Backup Exec Best Practices
- Backup Exec Best Practices
Best practices for Backup Exec Storage Provisioning Option
Best practices include tips and recommendations to help you use the Storage Provisioning Option effectively. For more information about the Storage Provisioning Option, see the Backup Exec Administrator's Guide.
The following best practices apply before you install the Storage Provisioning Option:
Attach any storage arrays to the Backup Exec server.
Install the storage array vendor's Virtual Disk Service hardware provider on the Backup Exec server.
Ensure that you complete any steps that the storage array vendor requires. Refer to the documentation that the storage array vendor provides.
The following best practices apply when you install the Storage Provisioning Option:
Install the option on the Backup Exec server to which the storage array is attached if you install into a Central Admin Server Option (CASO) environment.
Ensure that a centralized database is used in the CASO configuration.
The following best practices apply when you configure the Storage Provisioning Option:
Use the Configure Storage Wizard to configure the storage array.
Specify at least one hot spare for the storage array. Refer to the documentation that the storage array vendor provides for any recommendations or requirements on the number of hot spares that you should specify. Also, consider the risk if more than one physical disk fails but only one hot spare is available.
Consider using the physical disks that are in the first slot in the enclosure as hot spares. Then, you can quickly identify which disk is a hot spare.
The following best practices apply to virtual disks:
Create a duplicate backup data job to move data from the virtual disk to another device. For example, you can move data to a tape, and then store the tape off-site. For array redundancy, you can move the data to a virtual disk on another storage array.
Use caution when you select an unconfigured virtual disk to configure for use with Backup Exec. An unconfigured virtual disk may be in use as a Microsoft SQL Server database, an Exchange database, or a boot disk.
Do not share the virtual disk with other applications because Backup Exec may use all of the capacity on the virtual disk.