- Backup exec 16 delete expired backup sets full#
- Backup exec 16 delete expired backup sets software#
- Backup exec 16 delete expired backup sets plus#
All of the backup sets created by these backups eventually expire and are deleted by DLM.
Backup exec 16 delete expired backup sets full#
The second full backup runs, followed by the third incremental backup, and then the fourth incremental backup. The first full backup runs, followed by the first incremental backup, and then the second incremental backup. Even if the backup set is displayed as expired, the data is available until all dependent backup sets expire as well.įor example, you create a backup definition that contains a full backup and an incremental backup for the C: volume on a server. If backup sets are dependent on other backup sets, then Backup Exec does not delete the backup set until all expiration dates on the backup sets are reached. When the amount of time to keep the backup data expires, the data lifecycle management feature deletes the backup sets and reclaims the disk space unless there are dependent backup sets such as incrementals.īy default, Backup Exec keeps the most recent backup sets that are necessary to restore any backed-up component of a server, even if the backup sets expire. You specify how long to keep backup data when you create a backup job that is sent to a disk-based storage device. You can duplicate the backup data from the original storage device to tape, for example, which you can then send for long-term or off-site storage.How data lifecycle management (DLM) deletes expired backup sets on disk-based storageīackup Exec uses data lifecycle management (DLM) to automatically delete expired backup sets on disk storage, disk cartridge media, deduplication storage, storage arrays, virtual disks, and cloud storage. If you need to keep data longer than four weeks, you should duplicate it. However, you can also schedule the verify operation to take place at a later time or manually verify backup sets at any time. By default, Backup Exec automatically verifies backed up data at the end of a backup job. Otherwise, you may not realize that the media is inaccessible until you try to restore from it. If a verify operation fails, you can rerun the backup job to ensure that your data is protected. Running a verify operation can help you to determine if you will be able to restore the backup sets created by a backup job. You should run a verify operation after all backup jobs.
Backup exec 16 delete expired backup sets software#
Enabling either software compression or encryption can result in degraded performance for GRT-enabled backup jobs. The compression and encryption process are resource-intensive. You should not use software compression or encryption for GRT-enabled backu pjobs. Compression does not work effectively on data that is randomized. Data becomes randomized during the encryption process. Hardware compression is performed after encryption. You should avoid using hardware compression with software encryption. Running full backups periodically can help ensure that all of the data is accessible when you need to restore it. However, if one of the incremental backups is corrupt or missing, it can cause the restore to fail.
Backup exec 16 delete expired backup sets plus#
When you restore data that was backed up using incremental backups, Backup Exec restores the data from the initial full backup plus any data that was backed up in subsequent incremental backups. You should always run a full backup job before and after upgrading Backup Exec, the operating system, or any applications.īe sure to run full backup jobs periodically, in addition to any incremental backup jobs that you run. After at least one backup job has send data to a device, Backup Exec can determine the capacity. If you create a test run job before any other jobs, Backup Exec cannot check that the device has sufficient capacity to perform the backup job. Backup Exec does not recognize the capacity of a storage device until an actual backup job sends data to the device. You should run a backup job to your storage device before you run a test run job. If a credentials test fails, you can enter new credentials for the content so that Backup Exec can access it. Test to make sure that you have the appropriate credentials to access the content that you want to back up before you run a backup job. The following best practices help ensure effective backup jobs: