Data deduplication happens on the Arcserve Backup Server, so it works with all Arcserve Backup Agents running in your environment. However, you must upgrade any Arcserve Backup Windows and UNIX/Linux and Mac agents to r12.5.
To deduplicate data during a backup job, set up the job as usual and select a properly configured deduplication device as the backup destination, or as the staging location in a disk to disk to tape backup job. To configure deduplication devices, refer to the topic, Deduplication Device Management. To assist you as you determine where to add deduplication device groups, consider the following:
Consider deduplicating data that remains relatively stable between backups. The less data changes between backups, the greater the incidence of identifying duplicates.
Consider deduplicating data that must be retained for long time periods. Deduplication fits more backups onto the same physical media.
There is no limitation on data type.
Huge backup data streams are good candidates for deduplication.
Deduplication happens on the backup server, which means data is transported over the network and then deduplicated.
The answer to this question depends on how much data you need to back up, with approximately 110MB of data per backup stream required. The following are suggested guidelines:
For less than 500 GB, 1 CPU
For 500 GB to 2 TB, 2 CPUs
For greater than 2TB, 2 dual core CPUs
Example: How to Plan a Deduplication Installation
Suppose you backup 10 TB to a 25 TB disk, which means you can store a full backup for just one week. Using data deduplication, your first full backup might require only 8 TB of space. However, subsequent backups performed with data deduplication might require only as much as 800 GB (about 10% of its former space requirements). You would then be able to store about 20 full backups - about 5 months of backups - on the same disk.
Using this example, you can retain backup images:
|
Copyright © 2016
|
|