Their data is stored offsite, in encrypted containers that are highly available and have lower TCO than local storage.Ī recent study commissioned by Veritas asked over 900 mid-market IT professionals about backup and recovery practices. Instead of complex processes that depend on human intervention (who forgot to put new tapes in on Friday night?), IT professionals can actively meet their business’ data storage policy and reduce costs. Inexpensive cloud targets can easily replace aging tape libraries and provide a higher degree of availability for long-term data retention. By embedding this capability directly into the backup workflow, Veritas improves user productivity and business agility. All the backup sets for the backup jobs that are sent to cloud, OpenStorage, and tape devices are stored in encrypted form.The recent release of Backup Exec 16 introduced direct cloud connectors that enable writing data directly to hot and cool Azure storage. Only the backup sets for the backup sources that do not support GRT are stored in encrypted form.
#CATREBUILDINDEX BACKUP EXEC 16 SOFTWARE#
Enabling either software compression or encryption can result in degraded performance for GRT-enabled backup jobs.īackup Exec does not store the granular backup sets on disk in encrypted form when you enable encryption for the GRT-enabled backup jobs that are sent to disk, deduplication, and disk cartridge devices. The compression and encryption processes are resource-intensive. Recovery and staging of GRT data may require more than the minimum system requirements, depending on the volume of data in the backup sets.ĭo not use software compression or encryption for GRT-enabled backup jobs. Monitor your processor, disk, and memory usage if you experience any performance issues. Duplicating the backup sets to disk storage eliminates the need to stage the data multiple times and improves the performance of the restore jobs. The staged data is not retained after the restore completes. GRT restores from backup sets on tape must be staged to disk first. If this storage amount increases too much, it can negatively affect your system resources.ĭuplicate GRT-enabled backup sets to disk storage first and then run the restore jobs from the disk-based backup sets, if you must run multiple restores from the same backup set on tape. Each incremental GRT-enabled job requires a small amount of internal storage.
#CATREBUILDINDEX BACKUP EXEC 16 FULL#
Run a full GRT-enabled backup job periodically if your backup strategy uses frequent incremental GRT-enabled jobs. The extra space that the file occupies can often lead to failed jobs because of low disk space. Since GRT information is stored in IMG media, the file does not hold backup data. If you enable the Preallocate disk space incrementally up to the maximum file size option in the storage details, Backup Exec creates a file that is as large as the maximum file size that you specified. You can change the default staging locations in the Backup Exec Settings.ĭo not allocate the maximum size for backup files. The volume on which the staging location resides should have at least as much available space as the size of your largest GRT-enabled backup job. Use a volume that is not your system volume for a staging location. You back up Active Directory data or Exchange data to a disk. When you restore granular data from a tape backup, you must specify a staging location to store all of the backup sets that are required for the restore job as well as a separate staging location of at least 1 GB for the GRT processing. Backup Exec extracts the granular data to the staging location while it is being cataloged. Tape backups require a staging location that is at least as large as the data that you back up. You back up to or restore from a volume with file size limitations. You must use a staging location for GRT-enabled jobs in the following scenarios:
0 kommentar(er)
