I have collected these ways for setting up a DR Server from our ARSList and other sources. Hope this helps you
Database-wise, Our DBA should be mirroring the primary server, or perhaps dumping the logs from our primary and applying them to our backup every couple of hours. We can also use SQL Server log shipping as well. In short, we should not only replicate our database, and set up a procedure to keep it in sync (if possible) but we should also install the applications and configure them in the very same way, right down to the same installation directories.
Remedy licenses are specific to the host that they are on, so we cannot use the same server license on a different box. I beleive that Remedy does offer a licensing option, or plan, or something-er-other specifically for a backup server option. BMC would not charge us for DR licenses.
One other thing that just came to mind is we are using a VIP (Virtual IP) address for your server, rather than the actual hostname. Why?
Well, if our primary server goes down, and we have
used the hostname of the server to specify the connection, then we will be faced
with either
1.) walking around to every desktop and changing it out,
2.)pushing down a new config via your lan management tool of choice,
or
3.)putting together a document on how our users can change it out
themselves.
Either way If we go with the hostname, our users
feel the pain.
Not a good idea, especially in any current
environment.
If we use a VIP, then our users connections are
pointed to a virtual server name such as 'arsprod' or something generic. When
our primary server goes into melt down, switching everyone over simply becomes
a
matter of swapping out a DNS record.
Setting Up Database Mirroring
http://msdn2.microsoft.com/en-us/library/ms190941.aspx
Hope this Helps.
Regards,
Roney Samuel Varghese
**__20060125_______________________This posting was submitted with HTML in it___Classification: UNCLASSIFIED
Caveats: NONE
Hello all,
We are currently utilizing DSO to mirror two production servers. We use Like IDs to do this. We are getting performance hits because of this. I'd like to replace this with something else. I can think of several options, but I'm looking for other's ideas.
Is there a preferred method for producing mirror images of two productions servers?
The goal is to always have a fall back server in case the primary goes down.
Thanks up front,
Gordon Frank
Lockheed Martin
Classification: UNCLASSIFIED
Caveats: NONE
__20060125_______________________This posting was submitted with HTML in it___
