Google for "dag offline seed" Regards,
Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com -----Original Message----- From: Rick Berry [mailto:rbe...@elevativenetworks.com] Sent: Tuesday, January 18, 2011 3:56 PM To: MS-Exchange Admin Issues Subject: partial DAG restore, two of four dbs, sanity check Had a spate of drive failures across a three-server DAG last week (poweredge t710 firmware took out four drives across three machines inside of 24 hour period). I'm back up and running/healed ... but on one of the three, they'd like to take the opportunity to test their Backup Exec 2010 restore abilities. I had already reseeded two of four dbs before this came up, they'd like to drop the other two back in from restores and then re-enable replication. Does it work that way? If I drop two DBs back onto that file system (current replication suspended on those two to this particular target), will re-enabling replication at that point just fill in the delta between the two points in time magically? Or is that my own wishful thinking? Already know that I have a short bit of work to just do a simple reseed of these two and I'm good to go, but they'd like to try the restore as a test. Symantec is suggesting that we need to tear that machine out of the DAG completely, restore whole thing and then re-enable, but I think they're possibly wrong. Not sure what the diff would be between restoring two and re-replicating and restore four dbs/entire machine. I lack insight/skill in knowing that exchange 2010 replication will magically fill in that delta (of about a week's email data) on that restored DB file structure. I believed that it would 'just work', but am hesistant. --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
