Backup set options | |
Use buffer | If checked, files will be copied to the DS-Client Buffer (i.e. as fast as possible for the given server and LAN speed). This will free up the backup source as fast as possible. Then the DS-Client will send the files from the DS-Client buffer to the DS-System. Note: This option cannot be used if Continuous Data Protection (CDP) is selected. This option is not applicable for VMware VADP backup sets. |
Detailed log | Records all files that are backed up (you may view them in the Activity Log). |
Stop on errors | Specifies that a backup stops if this number of errors are encountered. The default is 0 (no limit). • range 0-9999 |
Initial Backup | If checked, the backup set is flagged for Initial Backup. Click the [>>] button to select the Initial Backup Path. |
Continuous Data Protection | Check to access the "Continuous Data Protection Settings" screen. From there, you can instruct DS-Client how to monitor this backup set’s source to immediately detect and back up changes. • Note: This option cannot be used if the “Use buffer” option is selected. |
Disable Common Files | This box appears if the feature is activated by your service provider. If checked, the backup set’s files will be excluded from Common File storage reduction. This means duplicate files will be encrypted and backed up individually, thereby potentially increasing the stored size. • You can only set this feature in the New Backup Set Wizard. It cannot be changed afterwards. |
Use Local Storage • These options appear if you have the Local Storage Tool Enabled from your service provider, and you have specified a Local Storage Path in the "DS-Client Configuration Parameters Tab screen". | |
Save | Check this box to indicate this backup set will also be saved to a Local Storage location (at the DS-Client site). • Backup data will be sent to the location specified in the Local Storage Path field. |
Cache | Check this box to indicate this backup set will use the Local Storage as a cache, in case a backup session loses connection with DS-System. • Cached backup data will be sent to DS-System at the next connection opportunity (after synchronization). • Backup data will be sent to the location specified in the Local Storage Path field. |
Local Storage Path | Click [>>] to choose a specific local storage path for this backup set. • Opens the "Enter Local Storage Path". • If you do not make a selection, the path from the "DS-Client Configuration Parameters Tab screen" is used. |
PreScan | If checked, the backup set is flagged to scan all files in the backup set prior to backup to display an estimated completion time for the backup. |
BLM (Infinite Generations) (Backup Lifecycle Management module must be enabled) | Backup sets are configured to save a specific number of generations. Once a backup item reaches this number of generations, the oldest will be overwritten with each new generation backed up. Check to configure this backup set for BLM. When applicable, the DS-Client will instruct DS-System to send a copy of the oldest generation (that is about to be overwritten) to the BLM Archiver. |
Compression Type | You can select the compression type: • LZOP: A faster compression than ZLIB, that comes at the expense of less compression. • ZLIB: This compression method will normally produce better compression than LZOP, but will take more time to compress. Four different ZLIB strengths are available (Global, High, Medium, and Low). “ZLIB Global” is the default value set in the DS-Client Advanced Configurations ‘Compression Type’ parameter; “ZLIB High” corresponds to a value of 9; “ZLIB Medium” = 6; and “ZLIB Low” = 3. • None: Disables compression for this backup set. (This will only apply to backups performed after this section is made. Any backups currently online will retain the compression type used at the time of backup.) |
Additional Backup Set Options The options that appear in this section are specific to the type of backup set: | |
Pre/Post | Click Pre/Post to access the Pre & Post Execution screen. For more information, see "Pre & Post Execution screen". |
Exclude old files | Click to access the Exclude Old Files screen. For more information, see "Exclude Old Files screen". |
Additional Backup Set Options | NAS, UNIX-SSH, NFS, Local File System backup sets. |
Do not follow the Mount Point (UNIX-SSH only) | Check to backup only the Mount Point itself (not the data under any Mount Point). |
Force backup even if the modified time or size did not change | If selected, DS-Client will force a re-backup of a file, even if its “last modified” time and size have not changed since the last backup. |
Continue backup on snapshot failure (NAS only) | NAS backup sets automatically try to backup using a snapshot of the NAS volume, using the NAS device’s native snapshot feature. This option determines the DS-Client’s behavior if the NAS snapshot fails (for any reason). • ON: (Default) DS-Client will continue the backup by trying to backup the selected volume’s data directly from the NAS storage. • OFF: DS-Client will stop the backup and report errors. |
Use Snapdiff API (NAS only) | NetApp has a “Snapdiff API” feature that can compare the current snapshot with the previous snapshot of a NAS volume to generate the list of new and changed files. If enabled, this can generate significant backup process speed improvements on large volumes with many files. • If selected, DS-Client will attempt to use the Snapdiff API. A previous snapshot must also exist for comparison. • If Snapdiff fails for any reason, DS-Client will proceed to scan the full NAS volume. |
Backup Hard Links | Hard Links are created in Unix-based file systems with the ‘ln’ function. • By default, this option is selected for any new backup sets. This means the backup will handle backup of the file and hard link information for the hard links to be restored. • If this option is not selected, this means any backed up hard link will be restored as a separate (individual) file. • Even with this option selected, you must create a backup set that includes all the hard linked files. Otherwise a warning will appear in the Event Log for the backup activity and if you restore from that backup, your existing hard links will be broken. The same applies if you perform a partial restore of hard linked files. |
Additional Backup Set Options | System i backup sets. |
Backup Private Authorities | • Saves any private authorities for objects with the Private Authority (PVTAUT) parameter (This parameter was introduced since IBM i 6.1). • When PVTAUT is set to *YES on the System i server, DS-Client is able to save the private authorities attached to any saved objects. • This feature allows backup / restore of Public Authorities, Owner and object authorities, Primary group and primary group authorities, and the names of authorizations lists linked to the saved object. • NOTE: IBM cautions against using this option for ‘individual objects only’ because PVTAUT increases the amount of time needed to save an object. It is not recommended that you select this option for large scale backup and recovery of user data. |
Previous Target Release | (TGTRLS): Specifies the release of the operating system on which you intend to restore and use the object. • *CURRENT: The object is to be restored to, and used on, the release of the operating system currently running on your system. The object can also be restored to a system with any subsequent release of the operating system installed. • *PRV: The object is to be restored to the previous release with modification level 0 of the operating system. The object can also be restored to a system with any subsequent release of the operating system installed. NOTES: • For system Libraries, Q* Libraries and/or *IBM Libraries, only the current release can be the target release. • Not all objects can be targeted to another release. To find out which objects are supported check your IBM System i documentation. • If DS-Client cannot backup the object to a previous release, it will retry the command without the TGTRLS parameter; this operation will be show on the log with the message "System i returned previous release target error; trying to rerun the same command without TGTRLS(*PRV) flag." • This parameter can only be specified when the backup set is created. |
Additional Backup Set Options | MySQL backup sets. |
Add locks around insert statements | Lock tables before inserting data on restore. (See the MySQL manual page for ‘mysqldump’ for more information.) |
Add MySQL specific table create options | Add MySQL specific extensions to the backed up database dump. (See the MySQL manual page for ‘mysqldump’ for more information.) |
Insert statement type | Specify how table rows are inserted into the database dump (i.e. the style of the ‘INSERT’ statement). (See the MySQL manual page for ‘mysqldump’ for more information.) • Extended - Fast insert. May not be useful for manual loading into non-MySQL databases. • Delayed - Uses ‘INSERT DELAYED’ when inserting rows. • Normal - Standard insert. Slower, but may be more portable to other databases. • Complete - Uses complete ‘INSERT’ statements that include column names when inserting rows. |
Table dumping option | Specify how tables are dumped. (See the MySQL manual page for ‘mysqldump’ for more information.) • Lock all tables - Prevent changes to data while backup is in progress (sets the tables to read-only mode for duration of backup). [This option is like using the --lock-tables dump option from the command line.] • Single transaction - [only works with transactional tables] This dump approach also prevents changes to the backup data, but does not set tables to read-only mode. • Do not lock tables - If selected, the tables can be changed during the creation of the dump file. Note the consistency impact this may have on the backup. [This option is like using the --skip-lock-tables dump option from the command line.] • None - Dump will be performed using the ‘mysqldump’ function with no special conditions. |
Additional Backup Set Options | PgSQL backup sets. |
Backup only the schema, not the data | Dump only the schema (data definitions). |
Do not backup privileges (Grant / Revoke) | Will backup only the data, not including the privileges of the database. |
Backup data as INSERT, rather than COPY | Dumps data as INSERT commands (instead of COPY). This will make restores very slow, but it will make those backups more portable to other SQL database packages. |
Vacuum database before Backup | Optimizes the PostgreSQL database before performing the backup (analyzes the database and performs ‘garbage collection’). |
Backup ownership of database objects | Check to backup ownership of any objects within the database (e.g. tables). • Note: By default, this option is off. However, the ownership of the entire database is always backed up by DS-Client (independent of this option). |
Additional Backup Set Options | Oracle backup sets. |
Logical Corruption Check | (Default is on) Will perform a corruption check on the database prior to backup. |
Backup only current archived logs | Check to backup only those logs that are necessary for the Oracle database. This saves backup space, by avoiding backup of any older logs. Leave this box unchecked if you want to backup all log files |
Truncate archived logs | Clear the Oracle Database logs associated with this item after backup. |
Use RMAN Compression | DS-Client will backup the Oracle database using the RMAN compression option “backup as compressed backupset”. This requires more CPU during backup, but results in a smaller output file (i.e. it can reduce the size and time of the DB dump). Using this compression will limit the Master / Deltas block-level incremental reduction, since the DS-Client will not find any repeated blocks in subsequent Delta generations. • None: No RMAN compression. • Archive Logs: RMAN compression applied only to Archive Logs. • Archive Logs and Tablespaces: RMAN compression applied to both Archive Logs and Tablespaces. |
Force pipe library path | If you are using DS-PIPE, this field appears. • RMAN requires the Media Management Library “libobk.so” to backup / restore using a PIPE. • The exact library name will be slightly different, depending on the platform. For more information, refer to the “Oracle Server Requirements” section of the Knowledge Base article in “Backup / Restore of Oracle Database Servers”. • You can specify the exact path (including filename) to the corresponding “libobk.so” for the Oracle server’s platform. These library files can be found in the DS-Client installation directory. • If you do not specify a path, the default path will be used: “$ORACLE_HOME/lib/libobk.so” • Make sure Oracle has full rights to read and execute in the library path. • Note: DS-Client does not validate this path. It simply forwards it to RMAN. |
Max. backup channels | (Multi-channel backups are only used for Dump. It does not apply when backing up through DS-PIPE.) The maximum number of channels DS-Client will allocate when backing up the database. • DS-Client can support up to 32 channels. The actual number that will be used depends on the datafile count for a tablespace. |
Additional Backup Set Options | DB2 Server backup sets. |
Prune History / Logfile | Delete entries from the history file or log files from the active log path. |
Online Backup | • If unchecked, perform Offline DB2 backup. During an offline backup, applications cannot connect to the database. • If checked, perform Online DB2 backup. An online backup allows applications to connect to the database and read and write to tables during database backup. Log retain or userexit must be enabled for an online backup. |
Additional Backup Set Options | XenServer backup sets. |
Use Snapshot | This options appears if the XenServer supports a ‘snapshot’ feature. • If checked, the virtual machine will be backed up using XenServer's native Snapshot capability. This means the virtual machine can be backed up even if the virtual machine is running. • If unchecked, the virtual machine must be stopped to perform a backup. Notes: • 1) If editing an existing XenServer backup set, and DS-Client cannot connect to the XenServer, the message “Unable to determine availability” will appear. • 2) If “Use Snapshot” is selected, any backed up generation can only be restored as a Template. |
Additional Backup Set Options | Sybase backup sets. |
Use file-based pipes to backup the data | If selected, instead of dump files, the DS-Client will create Pipes (FIFO files) in the dump directory and instruct Sybase to dump there. |
Additional Backup Set Options | VMware VADP backup sets. |
Attempt to quiesce I/O before taking snapshot | Pause the applications to guarantee a consistent and usable backup. • This option requires that the VMware tools are properly installed and configured on the guest operating system of the virtual machine. |
Attempt to use Change Block Tracking for backing up Virtual Machines | This option applies to vCenter Server version 4.0 (or higher) with virtual machines version 7 (or above). When this option is selected, DS-Client will attempt to reconfigure virtual machines to use Changed Block Tracking (CBT). CBT monitors whether the disks have been changed between backup sessions and, when a disk has not been changed, improves backup performance. |
Snapshot all VMs in the backup set at the same time | If selected: • If there are multiple virtual machines in the same backup set, DS-Client will perform snapshots of all the virtual machines at the same time. If not selected: • If there are multiple virtual machines in the same backup set, DS-Client will perform sequential snapshots of each virtual machine, waiting until the previous snapshot completes before starting with the next snapshot. |
Use Local DS-VDR | Select this option to use the Local DS-VDR Tool. For more information and applicable requirements, see “VMware VADP backup sets (Windows or Linux)”. • Note: This option is only available in the New Backup Set Wizard and cannot be changed after the backup set has been created. |
Backup Virtual Machine memory | • ON: Saves the virtual machine state (running programs loaded in memory). • OFF: Backs up the virtual machine as if it were not running. |
Use FLR | Configures the VMware VADP backup set to be able to perform File Level Restore (FLR). |
VMware Library Version (Not applicable to Local DS-VDR) | Select the version of VDDK library that supports the version of vSphere that you are using and the version of ESXi from which you want to back up virtual machines. Refer to the VMware documentation on VDDK libraries to determine the appropriate library version. |
Verify disks signature on next backup (Not applicable to Local DS-VDR) | If this option is selected, a VMware VADP backup set that has Changed Block Tracking (CBT) enabled will verify the disk signature after a disk is backed up in the next immediate backup session. This setting is not permanent but enforces a one-time signature verification. After the next backup session has been completed, this check box will be automatically cleared. |
Backup Virtual Machine’s snapshots (Local DS-VDR backup set) | • ON: Backup will ‘export’ the actual running virtual machine and all its snapshots. • OFF: Backup will ‘export’ the actual running virtual machine only (no snapshots). |
Export to host (Local DS-VDR backup set) | This list contains the available ESXi hosts where you can export the selected virtual machines. You must assign one as the target. • Click [>>] to open the “Specify Credentials” screen. |
Export to datastore (Local DS-VDR backup set) | This is a list of available Datastores on the destination host where you can export the individual virtual machine disk. • You must assign one as the target. |
Additional Backup Set Options | Physical to Virtual backup sets. (whose destination is to a VMware VADP vCenter Server) |
Enter vCenter IP | Enter the IP address of the vCenter Server where you want to ‘virtualize’ the selected physical computer. You must supply the credentials to the vCenter Server for a user with sufficient permissions to create a virtual machine. • Click [>>] to open the “Specify Credentials” screen. • Note: You cannot use Chinese characters for these credentials (username and password) because the VMware vCenter Converter does not support them. |
Export to datacenter | Once DS-Client / Local DS-VDR Tool connects to the vCenter Server, this dropdown list displays the available datacenters. • You can select a different one (if more than one are available). |
Export to host | Once you select the datacenter, you will be able to select a specific host’s IP address where the ‘virtualized’ machine will be created. You must supply the credentials to this host. • Click [>>] to open the “Specify Credentials” screen. |
Export to datastore | After selecting the destination host, you must select one of the defined vCenter Server datastores to which the new virtual machine will belong. |
Physical machine’s OS | You must specify the operating system of the target physical machine for DS-Client to handle the conversion properly. • Windows • Linux |
IP for conversion helper VM | [This field appears for target physical machines running on Linux.] When you convert a powered-on Linux machine, VMware Converter Standalone creates a ‘Helper Virtual Machine’ on the destination. This ‘Helper VM’ needs network access to the source machine to clone the source files. • You must have your network administrator assign a dedicated IP address for this backup set. If you create another Physical-to-Virtual backup set, you must obtain another, unique, dedicated IP address. |
Netmask for conversion helper VM | [This field appears for target physical machines running on Linux.] • Ask your network administrator what should be used. Typically, this is “255.255.255.0”. |
Gateway for conversion helper VM | [This field appears for target physical machines running on Linux.] • Ask your network administrator what address should be used. Typically, this will be some unique IP address on the same subnet as the “IP for conversion helper VM”. • The gateway address is the IP address that the local host uses to forward IP datagrams to other IP networks. This is either the IP address of a local network adapter or the IP address of an IP router (such as a default gateway router). |
Use Local DS-VDR | This option is selected by default when creating the backup set. It cannot be changed. |
Perform incremental conversions after the first session. | This option configures how a converted virtual machine is handled on the destination vCenter Server. • OFF: (Default) Each conversion creates a new virtual machine in the vCenter Server. (Note the space considerations, since you must perform manual deletes from the vCenter Server.) • ON: Each subsequent conversion goes to the same virtual machine. |