Db backups and OS/filesystem backups are what you need to perform a
recovery. Trying to manage your arserver via the remedy api is a lost
cause. There are too many factors that method can not address.
DR entails many things other than recovery from a server failure
though. You have to look past a server failure. What if a building
is lost, what if a site is lost, where are your bakcups? What if the
personnell responsible for systems operations are all concentrated in
the same area, and some catastrophe happens? What if your entire team
is on the same plane, helicopter, boat, etc.
http://en.wikipedia.org/wiki/Risk_management
http://en.wikipedia.org/wiki/Business_Continuity_Planning
http://en.wikipedia.org/wiki/Disaster_recovery
Axton Grams
On 11/4/06, Mosco, John D. <[EMAIL PROTECTED]> wrote:
**
All,
I am trying to find the best way to make sure that I have a good
disaster revovery plan. I already set up SQL Backups full and diff etc.
From my class two weeks ago (admin 2) it seems the best way to be able to
bring your data back though is to do a data export and then import. Is there
anyway to automate this on a schedule or do I need to have my junior admins
just do this every day ?
Thanks,
John Mosco
W01/GS-11
IT Coordinator
Customer Support Manager
PNG JFHQ J6
Com: 717-861-8143
DSN: 312-491-8143
Fax: 717-861-8414
'We the people'
__20060125_______________________This posting was
submitted with HTML in it___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
