In regard to: [Networker] Setup Networker for DR test, grahambird80 said...:
Most of your questions are covered in the disaster recovery guide. You
should definitely read it.
With regards to
1) Bootstrap report listing bootstraps and tapes.
Can this be exported to a file rather than a Tape and then imported?
Don't confuse the bootstrap report with the bootstrap. The bootstrap
is a (special) backup done by NetWorker. It will go to a backup device,
which is often going to be a tape drive, perhaps virtual.
The bootstrap report is a report about the most recent bootstraps (backups).
NetWorker generates the report automatically after each bootstrap is done,
because it's extremely important information to have. Older versions of
NetWorker try to send the report to a printer, but that's configurable.
Most sites have the bootstrap report emailed "off site" or otherwise stored
in multiple locations.
If your production server is still online, you can generate the report
using the -B option to "mminfo".
To do a DR of NetWorker, you *must* have a bootstrap backup available to
recover from. If you don't also have the bootstrap report then you're
most likely faced with the situation where
- you have a pile of tapes
- you know one of those tapes has the most recent bootstrap backup
- you don't know which tape or where on the tape it is.
It's possible to *find* the most recent bootstrap backup in this situation
so in theory you can do a DR without the bootstrap report, but
realistically you've taken a straight-forward procedure that doesn't take
very long and turned it into an error-prone and lengthy procedure.
In other words, the bootstrap report is almost as critical as the
bootstrap itself.
Be advised that the bootstrap report assumes that your environment has
"match barcodes" set to yes (or true). If that's not true in your
environment, the bootstrap report doesn't tell you how to match the
NetWorker volume label (what's reported in the bootstrap report) to the
actual physical barcode. It's also possible to find that information
yourself, but it would slow you down in a disaster recovery situation if
you don't have it.
---------------------------------------------------------------------------------
When you say
2) Networker server version running at original site as well as server name
exactly as it appeared in production.
Does it have to be FQDN? or will the computer name suffice?
It should be exactly the same as the original server name. If that name
was FQDN, then that's what you use. If it wasn't the FQDN, then don't use
FQDN when you set up your DR system.
---------------------------------------------------------------------------------
What if you dont have
4) Same tape device as original. If LTOIII you can read on LTOIV.
Do you mean the exact same hardware or will a different manufacture be OK?
It has to be able to read the original tape(s). If a different
manufacturer's drive can read the tape, then you're fine.
---------------------------------------------------------------------------------
When you say
6) once done shutdown networker and save /nsr/res to /nsr/res.orig. Rename
/nsr/res.R to /nsr/res.
I take it these are the paths under c:\Program Files\Legato\Networker
That depends on your installation.
---------------------------------------------------------------------------------
Finaly
7) restart networker. Run nsrck -L6 on backup server. You will need to delete
the original library and rebuild for the one you are using. run nsrck -L7 to
recover all client file indexes. Hopefully they are either all on the same tape
or you have a tape library with all tape loaded
Does the command you have given delete the Library? or will I need to do that?
No the command given does not do that, it does database consistency
checks. You will *likely* want to delete the library and recreate it, either
before or after those checks have completed. If your DR server is using the
exact same model tape library with exactly the same configuration (# of
slots, # of drives) and all of the OS's device paths to communicate with
the library and the drives are the same, then you wouldn't need to delete
the library. For most people that's not the case, so after mmrecov has
loaded all the old server's config (including the tape library config that
will not work correctly with whatever you have connected to the new
system), then the next step is to remove the library config and replace it
with a fresh config that will work for the library that's in place.
Overall, when you're doing a DR of NetWorker, the more you can make your
DR environment exactly match the configuration of your production
environment, the easier your DR will be. Some things (like server host
name and where the software is installed) are more important to match than
others (like the exact version of the NetWorker software, as long as
they're in the same series).
Once you're very experienced with NetWorker, you can more easily get away
with things like using different versions of the NetWorker software (which
might imply a media database conversion) in your DR or installing the
software under different paths.
In a real DR situation, though, you're going to be really pressed for
time, under a lot of stress, and probably tired (or tired *and* hopped up
on caffeine). That's the exact situation where you want things to be as
simple and straight-forward as possible, so matching your DR environment
to your production environment is a good idea even for people that know
the software inside and out.
Tim
--
Tim Mooney Tim.Mooney AT ndsu DOT
edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
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 with 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
| 