nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

disaster recovery of teamsite server .

srogers

Hi,
Is there any way we can link two teamsite server at two different location..& overcome the disaster situation like if one Teamsite server is down then other server picks up...i mean disaster recovery of teamiste server.

Find more posts tagged with

Comments

Adam Stoller

Hi,
Is there any way we can link two teamsite server at two different location..& overcome the disaster situation like if one Teamsite server is down then other server picks up...i mean disaster recovery of teamiste server.

There are ways of doing this - but it is dependent upon a number of factors - none of which you have provided and, frankly, this is the kind of thing that many of us get paid to implement - so I'm not sure you'll get much explicit response in a free forum.

If you have a reasonably detailed proposal - we are more likely to critique it for you, then to provide something from scratch.

cesarecastro

"Is there any way we can link two teamsite server at two different location?"

Yes

"overcome the disaster situation like if one Teamsite server is down then other server picks up"

As Ghotti stated there are many factors and different tools for this purpose. You could even use OD to maintain the servers in synch. It really depends on your SLA, requirements, budget,....

Share your ideas and we may be able to help you better.

cute_guy

Hi,
Is there any way we can link two teamsite server at two different location..& overcome the disaster situation like if one Teamsite server is down then other server picks up...i mean disaster recovery of teamiste server.

Try Microsoft clustering of two teamsite servers that share common store

nipper

Try Microsoft clustering of two teamsite servers that share common store

Boy that sounds so easy. Ever really tried it ?

Infrastructure, from installation to performance monitoring to disaster recovery, is a tricky game. While the fundamental goals are the same for most clients, differences in budget/hardware/software/etc. should determine the route you take.

For one of our "ideal" clients, we leveraged a SAN to store our data, and were able to reduce server downtime (freezes) from a few hours to a few seconds... it also goes without saying that a SAN is also a far more robust data storage solution, and an integral part of our DR strategy.

Then again, I have also worked on a project where the development server was the DR solution/server, and when production died (which it did), we had to use the weekly tape backups to restore the server -- it took 2 weeks. Fun, fun.

Fact is, DR strategies as rinky-**** as the latter example are considered "viable" by most clients... when you're in a boardroom, it's tough to sell a solution worth $X (and 'X' is usually a large sum) on something they may never have to use.

My only advice: use the right tools for the jobs, and don't allow your client to over simplify the DR process, or underestimate the potential dangers.

G'luck.