cancel
Showing results for 
Search instead for 
Did you mean: 

netbackup 7.5.0.5 backing up exchange 2010 via vmware

Daryl_Gawn
Level 4

on page 201 of the admin guide for exchange it says

 

"Duplicating a VMware backup that protects Exchange You cannot duplicate a VMware backup that protects Exchange through theNetBackup Administration Console. Use following command to generate a full. Exchange catalog with granular information for the image:"

can someone please confirm my understanding of this: does this mean that data backed up to disk cannot be duplicated to tape through storage lifecycle policy?  

 

also is there a separate admin guide or whitepaper on backing up a DAG ? i have a good understanding of backing up a DAG via agent but not using the vmware policy 

1 ACCEPTED SOLUTION

Accepted Solutions

RLeon
Level 6
   VIP   

Backing up Exchange DAG nodes in a VMware environment using Nbu's VMware-policy-type, follows a set of different rules. Unfortunately, the information is not elaborated in greater detail in neither the Nbu's VMware guide nor the Exchange admin guide.

Basically, you have to use a dedicated VM DAG node, make sure it only holds passive mailbox DBs, then set its name instead of the DAG name as the policy Client.
More details in this post, and with links to the technote.

 

When you use the VMware-policy-type together with the ASC mode to capture Exchange GRT data, the image generated will be a special "composite" image, within which a second logical image also resides.
So, from a single vmdk snapshot backup, effectively 2 backup images will be created, but they exist as one.

The "base" image is the vmdk snapshot backup. It does contain the Exchange data, but you cannot do Exchange GRT restores from this image.
The logical image that is hiddenly created and is associated with the base image is the Exchange GRT data, and with it, you can do GRT restores.

The logical image cannot be seen from the Catalog window in the Nbu Admin Console. I.e., you will only see the base image. However, you can confirm that it exists and is in effect when you attempt to do Exchange GRT restores and find that you are able to.

 

During a backup, only the base image gets cataloged, but the logical image does not.
Normally, the logical image gets cataloged when SLP duplicates the base image from disk to tape. You can see in this case that the logical image effectively also gets duplicated, because it is associated to the base image.

The paragraph you quoted is really just saying that if you duplicate the base image manually by using the GUI, then the logical image would not get cataloged. Essentially, that means once this image is on tape, and with the original disk copy expired, you can no longer do Exchange GRT restores from this image; not directly from tape anyway.
It suggests that you use the "bpduplicate -bc_only" command option to kick start the cataloging of the logical image. This is only useful if you decide to use the GUI to duplicate the base image later. If you use SLP, it does the logical image catalog step for you anyway. (Unless you tell it not to.)

 

 

can someone please confirm my understanding of this: does this mean that data backed up to disk cannot be duplicated to tape through storage lifecycle policy?

To answer you question, you can let SLP duplicate your VMware backup images from disk to tape without losing the ability to do vmdk level restores, file level restores, or Exchange GRT restores from a single image. Caveat: Exchange GRT restores can only be done when the image is duplicated back from tape to disk. Caveat2: The previous caveat is just the tip of the iceberg.

 

View solution in original post

1 REPLY 1

RLeon
Level 6
   VIP   

Backing up Exchange DAG nodes in a VMware environment using Nbu's VMware-policy-type, follows a set of different rules. Unfortunately, the information is not elaborated in greater detail in neither the Nbu's VMware guide nor the Exchange admin guide.

Basically, you have to use a dedicated VM DAG node, make sure it only holds passive mailbox DBs, then set its name instead of the DAG name as the policy Client.
More details in this post, and with links to the technote.

 

When you use the VMware-policy-type together with the ASC mode to capture Exchange GRT data, the image generated will be a special "composite" image, within which a second logical image also resides.
So, from a single vmdk snapshot backup, effectively 2 backup images will be created, but they exist as one.

The "base" image is the vmdk snapshot backup. It does contain the Exchange data, but you cannot do Exchange GRT restores from this image.
The logical image that is hiddenly created and is associated with the base image is the Exchange GRT data, and with it, you can do GRT restores.

The logical image cannot be seen from the Catalog window in the Nbu Admin Console. I.e., you will only see the base image. However, you can confirm that it exists and is in effect when you attempt to do Exchange GRT restores and find that you are able to.

 

During a backup, only the base image gets cataloged, but the logical image does not.
Normally, the logical image gets cataloged when SLP duplicates the base image from disk to tape. You can see in this case that the logical image effectively also gets duplicated, because it is associated to the base image.

The paragraph you quoted is really just saying that if you duplicate the base image manually by using the GUI, then the logical image would not get cataloged. Essentially, that means once this image is on tape, and with the original disk copy expired, you can no longer do Exchange GRT restores from this image; not directly from tape anyway.
It suggests that you use the "bpduplicate -bc_only" command option to kick start the cataloging of the logical image. This is only useful if you decide to use the GUI to duplicate the base image later. If you use SLP, it does the logical image catalog step for you anyway. (Unless you tell it not to.)

 

 

can someone please confirm my understanding of this: does this mean that data backed up to disk cannot be duplicated to tape through storage lifecycle policy?

To answer you question, you can let SLP duplicate your VMware backup images from disk to tape without losing the ability to do vmdk level restores, file level restores, or Exchange GRT restores from a single image. Caveat: Exchange GRT restores can only be done when the image is duplicated back from tape to disk. Caveat2: The previous caveat is just the tip of the iceberg.