Best practices for using Backup Exec 2012 Deduplication Option with the Central Admin Server Option
|Article:HOWTO74447|||||Created: 2012-03-07|||||Updated: 2014-01-28|||||Article URL http://www.symantec.com/docs/HOWTO74447|
Best practices include tips and recommendations to help you effectively use the Backup Exec Deduplication Option with the Central Admin Server Option (CASO). For more information about the Deduplication Option or CASO, see the Backup Exec 2012 Administrator's Guide.
The following best practices apply to using the Deduplication Option with the Central Admin Server Option:
Do not run jobs that use a deduplication disk storage device on a central administration server. Instead, assign backup jobs to managed Backup Exec servers and select a Backup Exec server pool as a setting for the destination device.
Share the deduplication disk storage devices that are on multiple managed Backup Exec servers with the Backup Exec server that is the replication target. This provides the best use of optimized duplication. For example, the main office site that has a managed Backup Exec server deployment shares the deduplication disk storage device with the central administration server at a remote site for disaster recovery purposes.
Subdivide the remote computers that are enabled for direct access sharing among the servers that host the deduplication disk storage folders to best optimize several managed Backup Exec servers at a single site. For example, a large site with two managed Backup Exec servers and 10 remote computers should split the remote computers evenly between the managed Backup Exec servers.
Limit the sharing of remote computers that are enabled for direct access sharing with other Backup Exec servers that use deduplication disk storage. This prevents duplicate data from being hosted on multiple backup servers.
- To perform optimized duplication between a central administration server and a managed Backup Exec server, the following WAN requirements must be met:
- Less than one percent packet loss during transmissions
- Less than 250 milliseconds network latency (round trip)
- Symantec recommends the following as minimum disk speeds per individual read, write, or verify operation:
- Up to 32 TBs of storage:
- 130 MB per second
- 200 MB per second for enterprise-level performance
- 32 to 48 TBs of storage: 200 MB per second
- 48 to 64 TBs of storage: 250 MB per second
- Up to 32 TBs of storage:
- Computers with disk speeds greater than 200 MB per second have optimal read and write performance deduplication.
- Computers with disk speeds between 150-200 MB per second have sufficient read and write speed for deduplication.
- Computers with disk speeds between 100-150 MB per second have some operations with degraded performance.
- Computers with disk speeds less than 100 MB per second experience poor performance. You should improve disk reads and writes before you install and run deduplication.
- For deduplication disk storage connection, the following are supported:
- Storage area network (Fibre Channel or iSCSI)
- Direct-attached storage (DAS)
- IInternal disks
- For deduplication disk storage connection, the following are not supported:
- Removable disks including USB
- FireWire devices
- The Backup Exec server should have redundant connectivity to the storage.
- The storage network must be a dedicated, low latency network with a maximum of 1-millisecond latency per round trip.
- The storage network must have enough bandwidth to meet your throughput objectives. Symantec supports the following storage network bandwidths:
- iSCSI SANs with a bandwidth of at least 10 Gb per second.
- Fibre Channel SANs with a bandwidth of at least 4 Gb per second.
Article URL http://www.symantec.com/docs/HOWTO74447