Expedat full version12/29/2023 ![]() The Files Path Root specified in a request can either be appended to the Root Path specified in the Source/Destination configuration, or override the Root Path entirely if it is specified as an absolute path.ĭIVArchive can (optionally) interface with the Source/Destination named Data Expedition Expedat Source/Destination Server. See the DIVArchive Sources and Destinations Table in the Oracle DIVArchive Installation and Configuration Guide in the Oracle DIVArchive 7.6 Core documentation library for a comprehensive list of these options, paths, and how they interact with those specified at the request level. Whether a request can override these Source/Destination attributes depends on the source type. DIVArchive allows these parameters to be specified in a DIVArchive request to that source or destination (at the request level). If the Connect Options and Root Path parameters have been defined for a Source/Destination configuration, they may not be appropriate for every request submitted. The Root Path configuration also depends on the source type, and can be left blank in some cases (and will be ignored by DIVArchive).įor Local or Disk source types, the Root Path specifies the mount point of the device in the local file system. For example c:\Exported\MPEG2 for Windows based file systems, or /Movies/MPEG2 on Linux based file systems. This is always specified as an absolute directory path on the target device. The Root Path to the files to be archived on the source, or restored to on a destination. DIVArchive ignores this parameter if no options are specified. Examples of Connect Options are recursive subfolders, user names or passwords, or other options specific to the selected source type. This is the QOS used when Default is specified in a request's Quality of Service field.ĭefine Connect Options that must be provided (or that can also be optionally specified) for the specific protocol or access method of the target device. This may be used to throttle data transfers where the target device is shared with other production systems or third party applications. This identifies the limits on the number of simultaneous requests that DIVArchive will execute concurrently on the target device, or prioritizing write (restore) operations over read (archive) operations.ĭefine the maximum bandwidth allowable to DIVArchive for transfers to or from the device. The maximum number of read and write transfer sessions and the total maximum number of read/write sessions combined. The Source Type is the protocol or access method used when interacting with the target device. These are common to all requests that involve that Source/Destination Generally, each source and destination has the following parameters configured. Source and DestinationĭIVArchive will archive and restore files to and from the server or disk file system.Īlthough a detailed explanation of the configuration of a source or destination is beyond the scope of this guide, a brief overview of the configuration is included because they can influence how requests are issued to them, and influence how two or more simultaneous requests to them are managed in the Current Requests Queue. Destination OnlyĭIVArchive will only restore files to the server or disk file system. In DIVArchive's Source/Destination configuration, each server type or disk file system is given a unique name and are configured as follows: Source OnlyĭIVArchive will only archive files from the server or disk file system. The sources and destinations that are used in DIVArchive requests are predefined in the DIVArchive configuration and are accessible by the Sources Destinations button under the Home tab. UNC paths are supported for SMB Source/Destinations and managed disks if the UNC path is directly mounted on the Windows Actors. However, you can define a local path to a mounted SMB share. Examples of both are Broadcast Video servers, FTP servers, or Disk Storage.Īctors in the Linux operating system do not support UNC paths for CIFS sources and destinations. A destination is defined as any connected system that requires content to be transferred to it from DIVArchive. Oracle DIVArchive Sources and DestinationsĪ source is defined as any connected system that has content intended to be transferred to DIVArchive.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |