VDSPACE fixup utility for Kbytes Limit Space Attribute
======================================================
The program called VDSPACE.EXE on Disk #1 of your Rescue NLM installation
disk set is a utility to find and fix problems with DSPACE settings on your
NetWare volumes. Read this prior to performing your first backup using
Rescue NLM!

If you have directory space limits setup on your disk, you might encounter
problems restoring directories using Rescue NLM if the space limit is more
than 65,535 4K blocks (262,140 KB or 268,431,360 bytes). This is because the
current versions of TSA31x and TSA400 seem to truncate the DSPACE limit in
subdirectories to 16 bits. The result is that you can't store files in any of
these subdirectories, or subdirs below them, because the DSPACE limit is now
smaller that it was when the data was backed up (even though the correct
DSPACE value was recorded on your NLM backup tape).

We have also found that some customer sites did not establish their own
DSPACE limits, but nevertheless, their volumes have various subdirectories
with VERY LARGE DSPACE limits (0x0FFFFFFF hex, or 268,435,455 4K blocks, or
1,073,741,820 KB). These users didn't notice such large DSPACE limits,
because the limits are larger than their volume sizes, and thus don't
restrict space usage. However, when these large numbers are backed up, then
restored, the TSA's will perform the same truncation, and one can end up with
a directory limit of about 260+ MB. If you have gigabyte disks, this CAN
result in "Insufficient disk space" error messages).

To assist our customers in dealing with this situation, we have provided the
VDSPACE (Verify DSPACE) utility. You can use it to see if any directory has a
DSPACE limit set larger than the volume size by typing:

     VDSPACE servername\volumename:

at the workstation's DOS command prompt. If VDSPACE finds any negative DSPACE
values, or ones that are bigger than the volume size, it will print out the
directory path and the DSPACE setting.

If you want to see the DSPACE settings for ALL directories that have a
setting, you can use the 'all' option:

     VDSPACE all servername\volumename:

You will get a complete listing of every directory that has a DSPACE setting.

If you find that you have invalid DSPACE values, you can have VDSPACE remove
the obviously erroneous ones (bigger than the volume size) by adding the
'fixup' option:

     VDSPACE fixup servername\volumename:

If you use the fixup option, and then run VDSPACE again without the fixup
option, it should NOT report any directories as having invalid values.

Finally, if you wish to remove ALL existing DSPACE settings, whether
"reasonable" or not, you can add the 'all' option along with the 'fixup'
option:

     VDSPACE fixup all servername\volumename:

Working with just part of a volume: if you want to perform any of the above
operations on just a subtree (a particular directory and all of its subdirs),
you can add a path to ANY of the above forms of the VDSPACE command to
restrict VDSPACE to just that part of your volume. For example:

     VDSPACE fixup all MYSERVER\SYS:SYSTEM\APPDIR

will cause VDSPACE to remove all DSPACE restrictions in the subdirectory
SYS:SYSTEM\APPDIR and all of the subdirectories of that directory.

Other options: If you type VDSPACE with no other parameters, VDSPACE will
explain its options for you. Please note that we have made two other options
available for VERY EXPERT USERS, and we DISCOURAGE THEIR USE! These two
options are 'dump' and 'torque'. The VDSPACE usage screen is self-
explanatory; if you use these options, you are responsible for the
consequences! Notice, though, that the effect of a 'torque' can be
subsequently undone with a 'fixup all'....
