Sei sulla pagina 1di 19

What is GWAN? Configuration of the backups over the LAN (not connected in the same network) is said to be GWAN.

Dos before configuring GWAN in Netbackup To check the Bandwidth limitations. Last Full backup medias of GWAN client Respective L3s approval / Validation

How do we configure the NBU GWAN in our infrastructure? For example: GWAN client need to configure in NBU server Request respective market to load the Medias which holds the last Full backup of GWAN client in to the destination NBU server. Start the Import process of the medias & Restore the GWAN client s data locally to the NBU server Force a Full backup of the restored data of the GWAN Client Once Backup completes. Install NBU client , Authorize & add it to the NBU server

Why we restoring the GWAN client images to local NBU server & Forcing Full backup? To use the de-duplication technology.

De-Duplications Concept: Deduplication is a method of retaining only one unique instance of backup data on storage media. Redundant data is replaced with a pointer to the unique data copy. Deduplication occurs on both a file level and a file segment level. When two or more files are identical, deduplication stores only one copy of the file. When two or more files share identical content, deduplication breaks the files into segments and stores only one copy of each unique file segment. Deduplication significantly reduces the amount of storage space that is required for the NetBackup backup images

Figure: File deduplication

The following list describes how NetBackup derives unique segments to store:

The deduplication engine breaks file 1 into segments A, B, C, D, and E. The deduplication engine breaks file 2 into segments A, B, Q, D, and L. The deduplication engine stores file segments A, B, C, D, and E from file 1 and file segments Q, and L from file 2. The deduplication engine does not store file segments A, B, and D from file 2. Instead, it points to the unique data copies of file segments A, B, and D that were already written from file 1.

In this scenario How De-duplication works: After Taking the Full backup of the GWAN client data locally( NBU MM). The backups information is gets stored in the Dedupe. This enables the deduplication for the GWAN client after the First Full backup.

How to Backup the GWAN image in NBU MM and add it to NBU:

Now the GWAN Image is in F drive on NBU MM

To Take Backup of this Folder (GWAN Client), Go to Policy -> Copy to New Policy

Give a Name as GWAN_Test_Policy & Press Ok

Configure the Policy storage to STU (Disk).

In the Client Tab , add NBU MM as client server

In the Selections Tab, select the path where you restored the GWAN client data.

Here the data is restored in F:\Restore1. Select it.

Once the configuration done, Check whether the policy is Active or De-active. If its in deactivated mode, make it active.

Cross check the exclusion list, sometimes Restore folders would be automatically added in exclusion list.

Now click on policy GWAN_Test_Policy and go to the client -> right click -> Host properties

Now go to Exclusion list -> and remove if the GWAN restore path is added.

Now Manually initiate the Full backup

Check the activity monitor for the backup status. Once the backup completes successfully.

Add the F:\Restore1 in exclusion list again, to avoid space utilization in tape.

As we done with GWAN client backup, we can delete the GWAN Test Policy.

Now the Backup image is added to EMM database & the de-duplications starts work

Now install the NBU client on the GWAN server & add it to the Policy Named

NZAUCM0001_NZAUCM0001_OASIS_GWAN_Default

AIR Backup Configuration: What is AIR Backup? Duplication to Remote Master is a NetBackup 7.1 feature where backups on a storage server in one NetBackup domain can be automatically duplicated (replicated) to a storage server on remote NetBackup domain. Once replicated, the images are automatically imported to NetBackup catalog on remote master.

What are the minimum requirements to implement Duplication to Remote Master? Duplication to Remote Master requires NetBackup 7.1 domains. The storage servers at the source and target domains must support OpenStorage version 11 and provide plugins to make use of Duplication to Remote Master. At the time of NetBackup 7.1 release, the Media Server Deduplication Pool (MSDP) supports duplications to remote master. The support for PureDisk Deduplication Pool (PDDO) and NetBackup appliances will be available at a later time. For third party OpenStorage devices, please contact the vendor for details on Duplication to Remote Master support.

NetBackup 7.1 Feature Briefing

Auto Image Replication

Figure 1 above shows the sequence of events in an Auto Image Replication backup and duplication operation broken down into 4 discrete steps: Step 1 The backup is written to disk storage in the source domain using a backup policy with an SLP configured for Auto Image Replication when the backup completes the catalog data it generates is appended to the end of the backup. Step 2 the backup is duplicated to the target domain

Step 3 the storage device in the target domain alerts the target master server to the fact that a backup has been duplicated to it. This triggers the receiving SLP to run a fast import operation in which the catalog data transferred from the source domain is added to the target domains catalog. Step 4 the receiving SLP in the target domain can now duplicate the received backup to any desired location for storage.

Test Drive Auto Image Replication is based on the interaction between storage lifecycle policies in the source and target domains. The SLP in the source domain duplicates the backup images to the target domain and the SLP in the target domain imports them into the target domains catalog. The first step to setting up Auto Image Replication is to configure at least one MSDP media server in both the source and target domains. Ensure that the media server in the target domain is reachable over LAN connections from the media server in the source domain. Once the storage servers have been created in both domains the storage server in the target domain must be granted replication credentials in the storage server in the source domain. This is set through the administration GUI on the source domain master server by adding the target domain storage server through the replication tab on the (source domain) storage server credentials as shown in Figure 2 below:

Figure 2 - Setting replication credentials on the source storage server.

The next step is to configure two storage lifecycle policies, one in each domain, with the same name. The SLP in the source domain must have at least one duplication storage destination that is configured as remote master as shown in Figure 3 below:

Figure 3 - Auto Image Replication remote duplication storage destination

The SLP in the target domain has no storage destination of type backup , instead the first storage destination has the type import and is configured to use the storage unit associated with the remote media server. At least one storage destination in this SLP must have the retention type set to remote retention . In Figure 4 below a single import storage destination is configured with the remote retention type selected.

Figure 4 - Auto Image Replication import storage destination

Once the SLPs have been set up configure backup policies in the source domain that uses the Auto Image Replication storage lifecycle policy. When these policies run the backups will be written to the backup storage destination and then duplicated to the storage server in the target domain. Figure 5 below shows the job monitor view from the source domain, showing the initial backup and subsequent duplication job.

Figure 5 Source domain, the backup is created and duplicated to the remote target domain

When the duplicated backup is detected in the target domain the target domain s SLP is trigged to import it and, if specified, duplicate it to other storage. Figure 6 below shows the job monitor view from the target domain showing the import of the image into the target domain and the subsequent duplication to alternative storage.

Figure 6 - Target domain, the backup from source domain is imported and duplicated to long term storage.

Once the backup has been imported into the target domain it is possible to browse the image and restore files from it in the target domain using the Backup, Archive and Restore (BAR) GUI as shown in Figure 7 below. (Remember to add the client from the source domain to the list of Source Clients for Restore in File -> Specify NetBackup Machines and Policy Types and select it):

Figure 7 - Target domain BAR GUI browsing Auto Image Replication backup.