Exchange 07 SCR Failback Procedure Help
I have a couple of questions regarding SCR.
1)Presuming that I have had a Database in a storage group go south on me and I have successfully activated the target computers storage group and it is in use by users, how do I then revert the database back to the use of the original computer, I think this is called FailBack, as compared to FailOver..?? Does anyone know any good links on this topic specifically, or have a detailed answer for me?
2)What happens to the log shipping on the Target SCR computer when a nightly Full back up is done. Currently we user a log reply lag of 1 minute and a truncate log time of 5 minutes. If the Source logs are applied and flushed(after the back up), how does the target update after that happens? Can someone explain this to me and fill me in on what I as missing in my understanding (limited) of SCR
Thanks in advance experts!
1)Presuming that I have had a Database in a storage group go south on me and I have successfully activated the target computers storage group and it is in use by users, how do I then revert the database back to the use of the original computer, I think this is called FailBack, as compared to FailOver..?? Does anyone know any good links on this topic specifically, or have a detailed answer for me?
2)What happens to the log shipping on the Target SCR computer when a nightly Full back up is done. Currently we user a log reply lag of 1 minute and a truncate log time of 5 minutes. If the Source logs are applied and flushed(after the back up), how does the target update after that happens? Can someone explain this to me and fill me in on what I as missing in my understanding (limited) of SCR
Thanks in advance experts!
ASKER
Thanks for all the links, However I have read all those and more allready. What I really want to know is, what is the procedure for going back to the original source server after successfully moving a storage group and the mail boxes in it over to a target machine. Is it the same as activating the target machine but in the other direction?
I need to know how to put the original server and or databases contained therein back in to production after using the SCR machine as a production server.
Also please address my question regarding what happensd to the log files on the SCR target when a back up job occurs on the source.
thanks!
I need to know how to put the original server and or databases contained therein back in to production after using the SCR machine as a production server.
Also please address my question regarding what happensd to the log files on the SCR target when a back up job occurs on the source.
thanks!
Also please address my question regarding what happensd to the log files on the SCR target when a back up job occurs on the source.
"Because you cannot make backups of an SCR target database, SCR log truncation is not based on backup times. Instead, log truncation is determined by the checkpoint at the SCR source and the value for TruncationLagTime.If the SCR source is a clustered mailbox server (CMS) in a CCR environment, the log truncation logic includes successfully copying and inspecting the log files by all SCR targets. This means that if an SCR target is not available, log truncation does not occur on the SCR source even if backups are taken."
"Because you cannot make backups of an SCR target database, SCR log truncation is not based on backup times. Instead, log truncation is determined by the checkpoint at the SCR source and the value for TruncationLagTime.If the SCR source is a clustered mailbox server (CMS) in a CCR environment, the log truncation logic includes successfully copying and inspecting the log files by all SCR targets. This means that if an SCR target is not available, log truncation does not occur on the SCR source even if backups are taken."
ASKER
Ok, thanks , that helps... But what happens when there is a Target available and a full back up is taken of the source, what happens to the sources log files... what my fear is, they trunkated by the backup process and not copied by the target before hand... I have my lag times set to 0.0:1:0 for both truncating and replay. So asuming that the source is available and the target is online as well, I would like to know if there is any fall out or what exactly happens to the log files after a back up is made to a source and how it effects the target. Also if there are any "special" considerations to consider in setting up a backup job?
ASKER
Another question i just came up with is not related to the previous, but I would like an answer.
After falling back to the source server after a simulate disaster recovery where I made active the targets copy of a storeage group\database, I have turned off the information store service on the target machine, and now Im getting errors in the event logs about a transient log failure of the system attendant service:(see below)
So my question ins i suspect that thisis caused by the attendent now being able to access the storage groups that i used as a recovery storage group, Is it safe to delete the storage groups using the exchange management console and whould that make the error go away?
A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds. Diagnostic information:
Cannot open mailbox /o=PCM/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
Microsoft.Exchange.Data.St
After falling back to the source server after a simulate disaster recovery where I made active the targets copy of a storeage group\database, I have turned off the information store service on the target machine, and now Im getting errors in the event logs about a transient log failure of the system attendant service:(see below)
So my question ins i suspect that thisis caused by the attendent now being able to access the storage groups that i used as a recovery storage group, Is it safe to delete the storage groups using the exchange management console and whould that make the error go away?
A transient failure has occurred. The problem may resolve itself in awhile. The service will retry in 56 seconds. Diagnostic information:
Cannot open mailbox /o=PCM/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Confi
Microsoft.Exchange.Data.St
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
A very detailed explaiantion would not be possible.However, you could check these articles,they have enough information you are looking for.
http://technet.microsoft.com/en-us/library/bb676502.aspx
http://technet.microsoft.com/en-us/library/cc164368.aspx
http://technet.microsoft.com/en-us/library/bb676465.aspx
resuming
http://technet.microsoft.com/en-us/library/bb691431.aspx
thanks,
consultkhan