Side note: In doing full restores on netware machines I've seen tape
swaps like never before. This was back a few releases from the
current so I can't say it is still true BUT it went something like
this: mount tape for bindary info for a directory/tree path, dismount
tape, mount tape for restore of data in that directory/tree path,
dismount tape, mount tape for bindary info for another directory/tree
path, dismount tape, mount tape for restore of data, dismount tape,
mount tape for bindary, dismount tape, mount tape for data, dismount
tape, mount tape for bindary, ...
Many things contributed to this such as a lack of tape drives
(corrected now), small retention time on mounts (ie 0), lack of
collocation (corrected now), and on... I've attempted to isolate the
bindary & directory info as much as possible pointing it to its own
diskpool, not migrating it to tape daily (only when pool it fulllllll)
it has improved things.
later
Dwight
______________________________ Reply Separator _________________________________
Subject: Re: Netware Bindery question
Author: ADSM-L (ADSM-L AT VM.MARIST DOT EDU) at unix,mime
Date: 2/3/97 8:07 AM
From: Peter Thomas on 02/03/97 10:07 AM
When I initially installed the ADSM Netware client, it was at the 2.1.0.5
level on a 3.12 server. At this point, everything worked as expected with
the domain including
DOMAIN ALL-LOCAL BINDERY
I subsequently upgraed to the first version of the 2.1.0.6 code, and at
this point, incrementals backedup stopped including the Bindery; however,
selective backups still would process the bindery.
I have not yet reinstalled the new version of the 2.1.0.6 code on the
server, partially due to my having made the server into a Netware 4.10 in
the meantime.
Peter Thomas
From: tombart @ VNET.IBM.COM on 03/02/97 09:06 AM
Please respond to ADSM-L AT VM.MARIST DOT EDU
To: ADSM-L @ VM.MARIST.EDU
cc: (bcc: ADSM)
Subject: Netware Bindery question
Greetings,
I recently installed the ADSM for Netware client V2.1.0.6 on a Netware
4.10 server for the first time. When performing an incremental backup
I notice that the bindery info is not being included. My dsm.opt file
contains the following domain entry:
DOMAIN ALL-LOCAL DIRECTORY BINDERY
This seems to allow all of my local drives, and the NDS to be backed
up ok, but no bindery info. What would be the correct method to
include all local drives, NDS, and bindery info ?
Any help is appreciated,
--Tom Bartiromo
=========================================================================
|