Network - Troubleshoot

Topics | How To | Troubleshoot | Related Topics

When WAN Links Cannot Support the Full Backup Data Transfer

Overview
Use the following procedure when WAN links do not have the bandwidth to transfer full backups and therefore only incremental backups can be performed on a regular basis. Consider the following scenario: CommServe, MediaAgent and storage devices are located in a Data Center. Clients are located in remote sites across a WAN. The WAN can support transfer of incremental data but not full backups.
Requirements
A GridStore license is required to implement this solution. (See License Administration for comprehensive information on licensing.)
Procedure
1.	Install a temporary MediaAgent at the remote site. The MediaAgent can be installed in the Client computer or on a different computer in the remote site.	See MediaAgent Deployment for appropriate procedures for installing the MediaAgent.
2.	Attach a temporary storage device (tape or magnetic device) to this MediaAgent and configure the device. This storage device must be compatible with the storage device in the Data Center.	The following sections provide a discussion on the various types of libraries and how to configure them: Blind Libraries Centera Clusters Cloud Storage Direct-Attached Libraries Direct-Attached Shared Libraries HDS Data Retention Utility (DRU) IP Libraries (Like libraries attached to ACSLS Server) Magnetic Libraries NAS NDMP Libraries Optical Libraries PnP (Plug and Play) Disk Libraries Removable Magnetic Disk Drives SAN-Attached Libraries Stand-Alone Drives Virtual Tape Libraries
3.	Add a data path (using the temporary MediaAgent and Storage Device) to the Storage Policy Copy (which uses the MediaAgent and Storage Device in the Data Center as the default data path) that will eventually be used to backup the clients from the remote site on a regular basis. If you have configured the temporary MediaAgent on a different computer in the remote site, set this data path as a high priority data path in the subclient.	See the following procedures for step-by-step instructions: Add a Data Path to a Storage Policy Copy Configure Data Paths for Subclients
4.	Perform an initial full backup using the data path associated with the temporary MediaAgent and storage device.	See Full Backups - How To for step-by-step instructions.
5.	Ship the media containing the data associated with the full backup to the Data Center. In the Data Center import the media into the MediaAgent/library which will be used to backup the clients from the remote site on a regular basis. In the case of a disk device, the magnetic library can be migrated to the MediaAgent located in the Data Center.	See the following procedures for step-by-step instructions: Import Media Migrate a Magnetic Library
6.	Delete the remote data path from the storage policy copy. If necessary, the remote MediaAgent and storage device can also be deconfigured.	See the following procedures for step-by-step instructions: Delete a Data Path from a Storage Policy Copy De-Configure a MediaAgent Deconfigure Libraries
7.	Add a data path for the MediaAgent, Storage Device in the Data Center, to a Storage Policy if it is not already available.	See Add a Data Path to a Storage Policy Copy for step-by-step instructions.
8.	Schedule regular incremental backups to go across the WAN from the remote client to the Data Center.	See Incremental Backups - How To for step-by-step instructions.
9.	Schedule regular Synthetic Full backups to read the data from the full backup as well as the incremental backup located at the Data Center. Optionally an inline copy can be used to separate the full and incremental backup to a different Media type. (However note that using a inline copy is not mandatory.)	See the following procedures for step-by-step instructions: Synthetic Full Backups - How To Enable an Inline Copy