Hello<br /><br />I am currently running SQL 2000 Enterprise Ed. on Windows 2000 Advanced Server on a cluster, disk storage provided by a SAN.<br /><br />Yes, I'm v. lucky <img src='/community/emoticons/emotion-1.gif' alt='' /><br /><br />The only downside is that if we lose our site, we lose our data, so I have setup log shipping to a different server on a different site.<br /><br />I have successfully got my two databases across, but now I have two questions.<br /><br />1. Is there a best practise for getting all the jobs & DTS packages across?<br />I can script out both, but I would need to change all references from primary to the secondary.<br /><br />2. I need to test this, but is it an easy thing to flip between the Primary & Secondary, as it is on a Cluster? It is a more manual process, but I would like someone to confirm that switching the 'instance' back to the Cluster box is as simple as running the jobs that I need to run to make the Secondary the Primary, but on the other box.<br /><br />Gosh, that's hard to read. Let me list the steps I would make in an ideal world.<br /><br />* Setup log shipping - done<br />* Backup, backup, backup <img src='/community/emoticons/emotion-5.gif' alt=';-)' /><br />* Failover SQL 'instance' to Seconday Server<br />* Point clients at Secondary Server<br />* Test, including updates to DB<br />* Bring Primary back on line<br />* Log ship from Secondary to Primary to bring DB up to date? Or do I backup Secondary & restore to Primary ?<br />* Flip 'instance' back to Primary<br />* Point clients back to Primary Server<br />* Test, including looking for updated record(s)<br /><br />Has anyone gone through this cycle, in a test scenario or, god forbid, for real?<br />If so, how was it for you? Did things work as advertised, or did you find gotcha's that you had to work through.<br /><br />My biggest fear is flipping my instance to the secondary, but then being unable to flip it back.<br /><br />any thoughts welcome.