Hi Zlatko
The small problem/task of backing up the DOS partition is easily solved... just
mak a CRON routine on the NetWare server, and use the TOOLBOX.NLM utility to
copy the DOS partion into a folder on a NetWare volume - after this u can make
a backup of these files... in a case of restore u just do it backwards -
restore to the NetWare volume, then use TOOLBOX.NLM etc. etc.
Regards
Flemming Hougaard
-----Oprindelig meddelelse-----
Fra: Zlatko Krastev/ACIT [mailto:acit AT ATTGLOBAL DOT NET]
Sendt: 22. november 2002 12:55
Til: ADSM-L AT VM.MARIST DOT EDU
Emne: Re: Novell bare-metal restore
Daniel,
I agree with you.
Following this list discussions we can see problems with NDS tree and less
with files. Latter are usualy resolvable. You are correct, my second
argument is mostly theoretical. TSM client ought to be able to restore NDS
tree. If demand is high enough Tivoli may/should ensure it really works.
If it does not we have to find another way.
But in Netware we have other replicas. Here comes my first (and main)
argument against the statement from that "customer's Novell guy". We have a
connection between the sites thus it does not matter at which
site new box is to be installed. During installation the server will join
the tree and create all necessary replicas. Even if we assume (very
unlikely) source replicas are in the plant, NDS replication ought to move
much less data than TSM restore. So they can:
1. Install server (DOS partition + some SYS: files)
2. Join the tree (even across WAN but I suspect LAN)
3. Finish Netware installation and install TSM client
4. Restore rest of the server files (definitely over LAN)
Because step 4 ought to be majority of the files and step 2 ought to be
several megabytes the procedure IMO ought to be fine.
I would count that "all restores to new machines can be considered BMR
procedures". We are calling it Bare-metal not same-metal recovery :-) And DOS
partition is a weird Netware problem we have to cope somehow. Maybe to try
using ADSM client for DOS v2 :-)
Zlatko Krastev
IT Consultant
Daniel Sparrman <daniel.sparrman AT EXIST DOT SE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
22.11.2002 11:00
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Novell bare-metal restore
Cant help commenting this... :)
Yes Zlatko, in theory your arguments are correct. However, looking down
the ADSM list, everyone can quickly notice the problems with backing up,
and restoring, the NDS tree.
So, if you have your master replica alive, and are trying to restore a
Netware server that contained a NDS r/w or subordinate replica from the
master server, I would probably recommend restoring the filesystems on the
Netware server, but creating a new NDS replica from the master server.
We've also been doing backup/restore testing on the NDS software, and the
NDS restore functionality is very dependent on which version of TSAXXX and
SMDR nlm:s you are using.
Also, doing a complete bare-metal restore of a netware, requires you to
restore the DOS partition, on which the server.exe resides. As far as I
know, this partition is NOT backed up by TSM. Therefore, doing the
bare-metal restore requires you to first create the DOS partition, then
copying the files to the Netware server directory. Thereafter, you must
start the Netware server, install the required protocols and nlms(normally
TSA:s and TCP/IP). Then, you have to manually(or automated if possible)
install the TSM client software. At this point, you are able to restore
all files backed up with TSM, including NDS(which I woulnd't trust).
This scenario, is not would I would call a BMR procedure. If it is, all
restores to new machines can be considered BMR procedures. For me, BMR is
the capability to automate restore functionality, making it easier to
recover from total system loss.
Best Regards
Daniel Sparrman
-----------------------------------
Daniel Sparrman
Exist i Stockholm AB
Propellervägen 6B
183 62 HÄGERNÄS
Växel: 08 - 754 98 00
Mobil: 070 - 399 27 51
Zlatko Krastev <acit AT ATTGLOBAL DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
2002-11-21 21:55
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Re: Novell bare-metal restore
--> You can't restore the Novell server at the central site because it
won't
be part of the Novell tree
I would argue against this.
- The server needs a connection to other servers to join the tree
during instalation process. If you have a connection (intended for TSM
backup) between the plant and the central site then you definitely have a
connection for NDS tree. And I suspect Master Replicas reside in the
central site so you will use LAN instead of WAN for NDS.
- you have the posibility to restore the NDS replicas on the new
server. Thus it will contain what the old one had. If the old one was part
of the tree new one ought to as well.
- maybe that Novell guru had bad experience with some other product.
Ask him can he perform that same restore using Novell tools. Later try to
explain that TSM client is using same operating system interface.
Zlatko Krastev
IT Consultant
John Schneider <jdschn AT ATTGLOBAL DOT NET>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
20.11.2002 18:24
Please respond to jdschn
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Novell bare-metal restore
Greetings,
I have a customer with a unique challenge. Maybe it's not, but it
seems to be to me because I am not a Novell guy. They are considering
implementing TSM in their environment to back up a bunch of Novell
servers that are out in remote plants with real slow links, like 256KBs.
The servers have sometimes 300-600MB of changed data a night. With
decent compression, we may be able to back them up overnight, since they
would permit 5pm to 8am as the acceptable backup window.
The challenge is when one server is replaced, either because it dies
or is replaced with new hardware. The Novell servers have about 40GB of
disk space, so there is no way they could restore across the slow link.
Our thinking is to restore the server to a server at the central
location where the TSM server is, so the restore could be accomplished
more quickly, then ship the restored server down to the remote site. My
customer's Novell guy says this won't work, because of the way Novell
trees work. You can't restore the Novell server at the central site
because it won't be part of the Novell tree(?!), and all the file
permissions and ownerships will be wrong.
Can somebody tell me what resources I should read to understand how
to do this, or can share with me your methodology to do a bare-metal
restore of a Novell server? I figure that surely by now a method has
been derived.
Thanks in advance,
John Schneider
***********************************************************************
* John D. Schneider Email: jdschn AT attglobal DOT net * Phone: 636-492-0247
* Lowery Systems, Inc.
* 1329 Horan Disclaimer: Opinions expressed here are
* Fenton, MO 63026 mine and mine alone.
***********************************************************************
|
