Backup set options • Some options may not appear or may be grayed out, depending on your backup selection and DS-Client configuration. | |
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. |
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. • range 0-9999, 0 = no limit • Note: The global default that appears in the New Backup Set Wizard can be configured using the Windows DS-Client “MaxErrors” Advanced Parameter. |
Initial Backup | If checked, the backup set is flagged for Initial Backup. Click the [>>] button to select the Initial Backup Path. |
Continuous Data Protection (Mircosoft Exchange Server using DS-MLR only) | 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. |
BLM (Infinite Generations) (Backup Lifecycle Management module must be enabled) | [Properties Tab only] 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. |
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. |
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.) |
Use Local Storage • [Properties Tab only] • 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 | [Properties Tab only] 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 | [Properties Tab only] 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 | [Properties Tab only] 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. |
Additional Backup Set Options | |
Use FLR | Configures the VSS-aware backup set for standalone Microsoft Hyper-V or Hyper-V clusters to be able to perform File Level Restore (FLR) of files from the target virtual machine’s files. • Note: This feature will not work if this backup set is configured to use Local Storage. |
Nimble Storage Integration Settings | Select this check box to configure the Nimble Storage integration settings. This option is only displayed when you are creating a Microsoft Server (VSS-aware) backup set. |
Database Backup Policy / Hyper-V Backup Policy • Some options may not appear, depending on your backup selection and DS-Client configuration. | |
Full dump: Always | [Default] This is the default behavior for all Windows database backups. • Each backup of the target Server performs a full dump of each database. |
Full dump: Plus Differential | Performs a full dump of the database on first backup, followed by differential backups until another full backup is needed (*). • [Microsoft SQL Server backup sets] The database can be selected with or without the ‘backup transaction log’ option. |
Full dump: Plus Incremental | Performs a full dump of the database on first backup, followed by incremental backups until another full dump is needed (*). • [Microsoft SQL Server backup sets] The database should be selected without the ‘backup transaction log’ option. (Even if ‘backup transaction log’ is selected, that option will be ignored if this backup policy is selected.) • [Microsoft SQL Server backup sets] The database’s Recovery Model must be: ‘full’ or ‘bulk_logged’. |
Transaction Log Only | Performs backups of transaction logs for selected databases to be used in combination with full dumps taken by another VSS or Classic Microsoft SQL Server backup set that performs full database backups. This option is only displayed when you are creating a Microsoft SQL Server database backup set. |
(*) A full dump is needed (other than first time) when: • a database has been backed up by another backup set (or manually from the SQL tools); • a database has been restored (either from another database or an earlier generation); • the database properties have been modified (recovery model switched to ‘simple’); • local cache is used for the backup set (This can occur for ‘Online’ backup sets with the option ‘Transmission cache on local storage’, but only when a generation must actually ‘pass through’ the local cache. If the connection to DS-System is down, then a full dump occurs and is written to the local cache. After that dump, DS-Client continues with the selected database backup policy.) • the DS-Client requires a Master generation (configured in the “MasterGenerations” value of the DS-Client Advanced Parameters - Setup Menu > Configuration > Advanced Tab). | |
Database Backup Policy Schedule Over-ride Rules [OPTIONAL] • This entire section is optional. It provides more precise control over the full dump for large Microsoft databases in high performance environments. • These over-ride rules are applied in addition to the regular backup schedule for this backup set. This means the backup set must be scheduled to run on the first day of the month, if the over-ride rule “Full every month on 1st day...” will apply. | |
Do not start full dump on | Prevents a full dump from being performed during the time window on the selected day(s). • This skips performing a full dump of the database, for up to the maximum number of consecutive times specified in the ‘MaxNonFullDumps’ parameter of the DS-Client Advanced Parameters (Setup Menu > Configuration > Advanced Tab). • For database integrity reasons, a full dump should be performed before that amount is reached. DS-Client will automatically try to run one full dump (once a day) if this option is set. |
Full every | Forces a full backup to be performed at the specified interval. • hour(s), day(s), week(s), month(s), or year(s) |
Full every week on | Forces a full backup to be performed on a specific day of the week. • You must specify a time, after which the full backup can be performed. |
Full every month on | Forces a full backup to be performed on a specific day of the month. • You must specify a time, after which the full backup can be performed. |
E-Mail Scan Policy • The “E-Mail Scan Policy” section appears for Email message backup sets for Microsoft Exchange Server using MAPI. | |
Full scan: Always | [Default] This is the default behavior for Email message backups for Microsoft Exchange Server using MAPI. • Each backup of the target performs a full scan of all items in the target folder. |
Full scan: Plus Incremental | Performs a full scan of the target folder on first backup, followed by incremental backups. • During incremental backups, DS-Client / DS-MLR will only retrieve the new or modified items from each folder. • Speed is the benefit of this option. However, since it does not detect items that have been removed from a folder, periodic full backups that perform a full scan should be performed. |
E-Mail Scan Policy Schedule Over-ride Rules [OPTIONAL] • This section is disabled if Continuous data protection is selected. • This entire section is optional. It provides more precise control over the full scan. • These over-ride rules are applied in addition to the regular backup schedule for this backup set. This means the backup set must be scheduled to run on the first day of the month, if the over-ride rule “Full every month on 1st day...” will apply. | |
Do not start full scan on | Prevents a full scan from being performed during the time window on the selected day(s). • This skips performing a full scan of the backup set’s target folders, for up to the maximum number of consecutive times specified in the ‘MaxNonFullDumps’ parameter of the DS-Client Advanced Parameters (Setup Menu > Configuration > Advanced Tab). |
Full every | Forces a backup with a full scan to be performed at the specified interval. • hour(s), day(s), week(s), month(s), or year(s) |
Full every week on | Forces a full scan to be performed on a specific day of the week. • You must specify a time, after which the backup with a full scan can be performed. |
Full every month on | Forces a full scan to be performed on a specific day of the month. • You must specify a time, after which the backup with a full scan can be performed. |
Pre/Post Click to access the Pre & Post Execution screen. • For more information, see "Pre & Post Execution screen". | |