<a href="http://msdn.microsoft.com/en-us/library/bb677181.aspx">http://msdn.microsoft.com/en-us/library/bb677181.aspx</a>]]>Wed, 14 Jul 2010 06:06:42 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from chvgmsToday I had an situation, where the witness and secondary at DR site went offline due to FW maintenance). The DB on the primary was not accessible using web though I have disabled (Paused) mirroring on the primary before the Firewall went offline. How do i make sure that the secret server is accessible in such situations?

Thanks,Sridhar]]>Tue, 13 Jul 2010 08:24:25 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from TuckerIn the event the Witness Server goes offline and the primary gets in the fail-over state. You can disable mirroring and then continue to access the primary database.

1. Run this SQL command on the primary db to disabling the Mirroring:ALTER DATABASE SET PARTNER OFF;

2. To Disable the Database's Recovery State (Restoring) Run this command:RESTORE DATABASE WITH RECOVERY;

]]>Tue, 13 Apr 2010 06:25:40 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from TuckerIn the event the Witness Server goes offline and the primary gets in the fail-over state. You can disable mirroring and then continue to access the primary database.

1. Run this SQL command on the primary db to disabling the Mirroring:ALTER DATABASE SET PARTNER OFF;

2. To Disable the Database's Recovery State (Restoring) Run this command:RESTORE DATABASE WITH RECOVERY;

]]>Tue, 13 Apr 2010 06:25:29 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from chvgmsSince the DB mirror is very much controlled by witness server, in the event if it crashes, the DB on the primary cannot be accessed nor deleted. What would be the alternative to access the DB in this case, apart from creating a new DB, restoring the backup and configuring the new DB name in the configuration settings?

Thanks,Sridhar]]>Mon, 12 Apr 2010 02:33:46 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from TuckerTo reboot machines in a mirrored environment you will need to temporarily pause the mirroring. If you go to database properties and the Mirroring tab, there will be a Pause mirroring button. Once paused the machines can be rebooted and then when they are all back online the mirroring can be resumed. While the mirror is down the primary will queue a log of any changes and when the mirror is resumed these will be replicated to the mirrored database.

If the outage is going to be prolonged, you may need to remove and recreate the mirror rather then pausing because of the log size. See this link for more information: <a href="http://www.thycotic.com/products_secretserver_forums.html?postid=1776#1776">http://www.thycotic.com/products_secretserver_forums.html?postid=1776#1776</a>]]>Tue, 23 Mar 2010 11:51:37 GMThttp://my.thycotic.com/forums/messages.aspx?TopicID=261
Message from chvgmsI have configured DB mirroring for my existing secret server for the DB failover with witness server. My question is what is the order do i need to follow if i want to reboot the primary, secondary and witness servers?