**

The comments people have supplied are consistent with the strategy we used.

However, one thing I felt was great was that we swapped our prod server to the backup every month. (even months - server a was prod, odd months - server b was prod) The first 5 times or so - we learned a lot (DNS caching issues and stuff like that) - but eventually we had it down quite nice.

Oh - we did this for years - eventually to the point where we did not swap the machines anymore. Then (guess what happened) - mgmt saw the backup as an idle box and gave people access to it - which then caused problems for future swaps. (So the lesson is - hold on tight to both machines)

-John



John David Sundberg
235 East 6th Street, Suite 400B
St. Paul, MN 55101
(651) 556-0930-work
(651) 247-6766-cell
(651) 695-8577-fax



On Sep 22, 2006, at 10:47 AM, Marino, Melanie A wrote:

**
Can anyone share with me what their company is using for Remedy Disaster Recovery?  We are looking to replicate our Remedy production environment to another site in real-time and switch back and forth between the servers as needed.  We are trying to determine the best solution.  We are running on a Solaris machine and an Oracle DB.
 
Your help would be greatly appreciated.
 
Thanks,
Melanie Marino
Project Manager
KPMG LLP

*****************************************************************************
The information in this email is confidential and may be legally privileged. It is intended solely for the addressee. Access to this email by anyone else is unauthorized.

If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. When addressed to our clients any opinions or advice contained in this email are subject to the terms and conditions expressed in the governing KPMG client engagement letter.
*****************************************************************************

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to