Deduplication PowerVault DL Backup to Disk Appliance
Executive Summary Introduction Customers of all sizes and needs are seeking new ways to tackle their data protection challenges. While the challenges of data growth are not new, the pace of growth has become more rapid, the location of data more dispersed, and linkages between data sets more complex.
example, a single media server licensed with the Deduplication Option can simultaneously use Client Deduplication for some jobs and Media Server deduplication for others.
exists where the customer’s VMware Server or Exchange Servers are the most powerful machines available in terms of processor speed or disk throughout.. Where appropriate, why not leverage some of this remote computing power to achieve faster backups? Both of these situations are examples where client deduplication can offer a comprehensive solution to the data protection challenges brought on by the environment. Generally, remote office backup strategies have two basic architectures.
Table 1 – Client Deduplication * Note – for Client deduplication with Backup Exec Agent for VMWare (AVVI) and Hyper-V, the Backup Exec Remote Agent must be installed in the Guest Operating System. In this circumstance, the Remote Agent is responsible for performing the backup, and not the Agent for VMWare or the Agent for Hyper-V. Symantec recommends that for optimal deduplication, a Remote Agent also be installed in Hyper-V guests.
• Remote Office Protection over a WAN: With Media Server Deduplication, the PowerVault DL Backup to Disk Appliance receives the entire data set before deduplication takes place. This is not a WAN-friendly method of deduplication. Generally, Remote Office protection without local storage should use Client Deduplication. Any PowerVault DL Backup to Disk Appliance that has the Deduplication Option licensed can utilize Media Server deduplication.
tracked and maintained. By default, the file storage location and the Postgres SQL database are installed to the same location. Right click on the Deduplication Storage Folder in the Backup Exec Device tab and select properties to access the default settings. The default settings specify 2 concurrent operations for the Deduplication Storage Folder. The Concurrent operations setting represent the number of backup or restore operations that the Deduplication Storage Folder will process simultaneously.
For Remote Agents that cannot use Client Deduplication (Remote Agent for Linux and Unix [RALUS], Remote Agent for Mac Server [RAMS], Remote Agent for NetWare [RANW], etc.) there is no change to the system requirements as outlined in the Backup Exec 2010 Administration Guide. This also holds true for Windows Remote Agents that do not choose to use Client Deduplication.
Table 3: Deduplication Methodology by Use Case Migrating Data to Tape for Long-Term Storage An environment with a disk-to-disk-to-tape architecture is fairly common among customers who are interested in deduplication. It’s important to note that all of the forms of deduplication mentioned here are disk-based. Deduplicated data is never stored on tape in its deduplicated form; however, the process of migrating deduplicated data to tape is a simple process.
Restoring Deduplicated Data Restoring deduplicated data follows the same process as setting up a regular restore job of backup data that has not been deduplicated. See Chapter 14 of the Backup Exec Administrator’s Guide for specific details on setting up restore jobs. Conclusion The PowerVault DL Backup to Disk Appliance powered by Symantec Backup Exec 2010 introduces new capabilities around storage management through Deduplication.
