disaster recovery strategies

I have a ts 6.5 install and would like to have a ts6.5 box at my disaster recovery center win 2003 ee. My dilema is how to keep the dormant server current with the latest stuff in my live 6.5 box.

How are all of you doing it? I was thinking of deploying the backing store to the remote ts 6.5 box but someone said this is not the best idea due to domain naming issues? Someone else said to deploy editions to the remote box, but then then backing stores are out of synch right? or wrong? or doesn't matter? I'm lost.

How are the rest of you doing this?

Your thoughts r welcome, thanks,
Nico

Find more posts tagged with

Comments

DJ_At_Work

here is a simplified version of my current setup:

We have teamsite servers in 2 different states and all the data (backing-store) is stored in a 3rd state. the data store has 2 harddrives in the box; 1 drive for each teamsite server co-location. these 2 harddrives sync every 5 minutes.

to get a better idea, see attachment (and be amazed by my MS paint skills Smiley Happy

)

nico

so when your users are using teamsite they are really working off of a network in another state?

DJ_At_Work

sort of... the core teamsite application server lives in oregon (site A in the attachment), our backing-store lives in MI (site C in attachment), and our fail-over teamsite servers live in WI (site B in attachment). so when data is written to the backing-store, then it goes to a different state..

we just performed a DR test last weekend (thankfully, all went smooth).

nico

Are you using od to do all this data synching? Are the rest of you doing something similar?

jed

Do you do an iwfreeze before you sync to the other disks? In theory, if you do a sync to a backup disk/server, and an iwfreeze was not performed, the data on the backup can be in an inconsistent state.

--
Jed Michnowicz
jedm@sun.com
Content Management Engineering
Sun Microsystems