• Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (9)

1 Charles Hart commented Permalink

One more question for this morning. We know the XIV can do snaps of Exchange2010, but we heard that it can not do snaps of the passive dags is that true?

 
Thank you for your time.

2 Delbert Hoobler commented Permalink

That is not true. IBM Tivoli Storage Manager for Mail - Data Protection for Exchange and IBM Tivoli Storage FlashCopy Manager supports backing up the active database AND the "Database Copies" (passive) in a Exchange 2010 DAG environment.

3 Charles Hart commented Permalink

Thank you Delbert, one last question. Do we have to use the DP for Mail Agent or can we just use the XIV snap capability along with Flashcopy services to perform VSS hdw based snaps. We currently manage a large TSM environment , but would like to move the Exchange backups out side of TSM.

 
Regards,
 
Charles

4 Delbert Hoobler commented Permalink

If you do not want to use a TSM Server, you can use IBM Tivoli Storage FlashCopy Manager by itself. You do not need to purchase IBM Tivoli Storage Manager for Mail - Data Protection for Exchange. FlashCopy Manager by itself will manage your persistent snapshots of your Exchange or SQL databases.

 
Here are a few thoughts to keep in mind... If you integrate with a TSM Server, you can still get the same functionality as standalone, but you also get the added value of the ability to store backups within the TSM Server storage pools (longer term storage), centralized scheduling, centralized policy management, centralized reporting, etc.

5 Charles Hart commented Permalink

Thank you again!

6 Matthias Feyerabend commented Permalink

hi,

 
thanks for the nice backup script - it works fine in our test environment.
 
We have a special question about backup and restore:
 
There are two nodes (Node1 and Node2) in the DAG.
Node1: MBX01 (active and mounted)
MBX02 (passive and healthy)
Node2: MBX01 (passive and healthy)
MBX02 (active and mounted)
 
The script backuped successfully on
Sunday full backup MBX02 (passive and healthy) on Node1 and
MBX01 (passive and healthy) on Node2
Monday to Saturday differential backup
MBX02 (passive and healthy) on Node1 and
MBX01 (passive and healthy) on Node2
 
 
 
We restored these databases MBX02 resp MBX01 to recovery databases on Node 1 esp. Node1 resp Node2.
 
 
 
What would have happened during restore if on Wednesday MBX02 had become "active and mounted" on Node1 and "passive and healthy" on Node2? The script would have backuped MBX02 on Node2.
So the restore on Friday could not work sucessfully because some backups are on Node1 and some are on Node1!
 
 
 
 
In the DSM.OPT in TDPExchange we configured different nodenames
Node 1 Nodename NOde1EX
Node 2 Nodename NOde2EX
 
 
 
Would the same nodename on both nodes solve the problem or what is the correct way get a successful restore is status of the databases changed?
 
Thanks for your help
Ruth

7 Delbert Hoobler commented Permalink

The current best practice is to back up databases from the same Exchange server if possible. If that cannot be done, you can use the same nodename for all nodes in a DAG. That will make all backups accessible from the the tree view on the left side of the GUI.

8 James MacDonald commented Permalink

So i have a question about your last post Delbert, you stated "The current best practice is to back up databases from the same Exchange server if possible. If that cannot be done, you can use the same nodename for all nodes in a DAG. That will make all backups accessible from the the tree view on the left side of the GUI"

 
So is that the TDPEXCHANGE nodename you are talking about, or the backup archive client nodename?
 
I have 3 Exchange 2010 servers, in a DAG setup with 9 DB's spread across the 3 nodes, and passive copies spread across too. So the Active and Passive Copies are never on the same node (unless a failure occurs i guess)
 
So what i have done is set up 3 separate BAclient nodes, and 1 TDPEXCHANGE node called EXCHANGE2010, i have looked at the backupdag.ps1 powershell script, and i am wondering what happens if one of the passive dbs on server is is unhealthy, it will not find the active DB on that node as it is on another....
 
I do have a call out to IBM support for some of these questions....
 
thanks

9 Delbert Hoobler commented Permalink

James,

 
>>So is that the TDPEXCHANGE nodename you are talking about, or the backup archive client nodename?
I am referring to the TDPEXCHANGE nodename.
 
>> So the Active and Passive Copies are never on the same node
If you want to back up from a passive copy, try to keep at least one of your servers consistently passive for any given database. You can then run the backups for that database from that consistently passive node. You can run backups from all three servers.
 
If a passive is not healthy, it will not back it up. If you are also running that same script from the active node, it will detect that situation and it will run the backup from there.
 
If you are still unsure, you have a great idea to pursue it through the PMR.

Add a Comment Add a Comment