Backup Exec 21.1 Best Practices
- Backup Exec Best Practices
Best practices for Backup Exec backups
Best practices include tips and recommendations to help you use Veritas Backup Exec backup jobs effectively. For more information, see the Backup Exec Administrator's Guide.
The following best practices help ensure effective backup jobs:
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. If a credentials test fails, you can enter new credentials for the content so that Backup Exec can access it.
You should run a backup job to your storage device before you run a test run job. Backup Exec does not recognize the capacity of a storage device until an actual backup job sends data to the device. 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. After at least one backup job has send data to a device, Backup Exec can determine the capacity.
You should always run a full backup job before and after upgrading Backup Exec, the operating system, or any applications.
Be sure to run full backup jobs periodically, in addition to any incremental backup jobs that you run. 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. However, if one of the incremental backups is corrupt or missing, it can cause the restore to fail. Running full backups periodically can help ensure that all of the data is accessible when you need to restore it.
You should avoid using hardware compression with software encryption. Hardware compression is performed after encryption. Data becomes randomized during the encryption process. Compression does not work effectively on data that is randomized.
You should not use software compression or encryption for GRT-enabled backu pjobs. The compression and encryption process are resource-intensive. Enabling either software compression or encryption can result in degraded performance for GRT-enabled backup jobs.
You should run a verify operation after all backup jobs. Running a verify operation can help you to determine if you will be able to restore the backup sets created by a backup job. If a verify operation fails, you can rerun the backup job to ensure that your data is protected. Otherwise, you may not realize that the media is inaccessible until you try to restore from it. By default, Backup Exec automatically verifies backed up data at the end of a backup job. However, you can also schedule the verify operation to take place at a later time or manually verify backup sets at any time.
If you need to keep data longer than four weeks, you should duplicate it. 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.