Hi,
Legato's nsr_client or uasm page or one of those says that you can't use a "*"
in the saveset name, which makes this much more difficult. (It appears that it
works, but when you go to restore a saveset, you have to specify paths, and it
is unsupported, so it is possible that going forward it may simply not work).
This leaves you with the client-side script idea, and hard coding the subtree
paths.
Hard coding is much easier, both in implementation and in maintenance, than a
client-side script that replaces save.exe.
You could set your saveset as:
x:\projects\path1
x:\projects\path2
x:\projects\path3
This will get you three streams, working around both tape limitations
(depending on your specific config, of course), although this requires that
your projects be broken up intelligently. If the problems is that you have lots
of small files, this will also get around the kernel limitations on doing NTFS
file/directory lookups, although give your size, I'm suspecting your average
file size isn't the issue.
One theme that we've seen a lot of recently is that when you have a partition
that large, and backups become an issue, it gives you and opportunity to step
back and look at your policies for sizing of partitions. If you include backup
requirements as well as technical limitations of partition sizing, you may
decide to look at your internal best practices.
If you've ever done a chkdsk of a 1TB+ NTFS file system on Windows, you'll know
what I'm speaking of. (Unless you are using a different file system, like VxFx,
that is).
You may also want to consider using Windows mount points that are at a subtree
level--x:\projects is one partition, x:\projects2 is another, etc. Having large
partitions is inherently a risk, even with NTFS5's journaling--if you ever have
to do a boot time checkdsk on that drive, you are in for hours of delay in
booting. If you have several partitions under the x: drive, NetWorker will
inherently create multiple save streams for them.
BTW, we've done the client-side script, and it is more difficult than you would
think. Lots of details to understand, and unless you understand the subtle
NetWorker issues (automatic directive creation, automatic mount point
generation, root partition backups, etc), you may find that it is a maintenance
headache, and misses important data to boot.
So I guess I have one question--is your directory structure condusive to simply
hard-coding the saveset to something simple, or do you have a particularly wide
or deep directory structure that doesn't work with this?
Dave
-----Original Message-----
From: Maarten Boot (CWEU-USERS/CWNL)
[mailto:Maarten.Boot AT NL.COMPUWARE DOT COM]
Sent: Friday, May 27, 2005 10:45 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Batch file and script
Andrew,
If I understand correctly you want to create a script that lets you
backup a subtree in 3 parts separate from the normal backup of that
volume e.g.
master_volume = X:\
Subtree = X:\all_data\bigdata
and you want to split the Subtree into 3 parts e.g.
Subtree_1 = X:\all_data\bigdata\[a-k]*
Subtree_2 = X:\all_data\bigdata\[l-s]*
Subtree_3 = X:\all_data\bigdata\[[t-z]*
So now you have in total 4 subtrees on this volume
You allso expect to run Subtree_1 to 3 at the same time and so expect a
faster backup.
--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
