|
Re: [Networker] saveset "all"
2006-04-21 10:54:54
On Apr 21, 2006, at 10:45 AM — 4/21/06, michael brooks wrote:
I should clarify my question for clarity...: does saveset "all" imply
(on a windows client) a restore of the registry, all libraries,
program
files etc so that if a client goes down, we could bring another
barebones client up (assuming identical hardware) with only a restore?
Or would we need to install the OS and rebuild program files and
restore
data from saveset "all?"
This depends on the Windows version, but yes, "Saveset all" does
carry that implication. This also assumes your server has no local
directives that skip any of the system components.
You should read the disaster recovery guide on EMC's server, as well
as the Windows NetWorker Administrator guide. Most of this stuff is
covered there.
Frankly though, for a typical Windows server, its easiest just to buy
two and then install your software on the second server and simply
have it available as a cheap hot standby for use in the event though
primary server fails. Ideally, your secondary server should be
located as far away as possible (in a different building) from the
primary server. This is what we do for a lot of our critical
applications and it works well. We also test the process of
recovering the previous night's backups to the secondary server every
three or four months.
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|
