Veritas backup exec 16 console not working

#Veritas backup exec 16 console not working full#

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.

#Veritas backup exec 16 console not working full#

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. 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: