home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 8 Other
/
08-Other.zip
/
thcdasd.zip
/
RESTDASD.TXT
< prev
next >
Wrap
Text File
|
1996-10-29
|
10KB
|
294 lines
RESTDASD UTILITY
----------------
Version 1.00
(c) Steve Sharrad, August 1996.
(c) The HENLEY College, August 1996.
It is suggested that you make this window full-screen,
if it is not already, by double-clicking on the above title bar.
All rights reserved.
This software is supplied without any warranty whatsoever and is used
entirely at the users own risk. No claims for damages as a result of using
this product will be accepted.
This product may be freely copied on the understanding of the above and on the
basis that it is not modified or sold for profit, and that it is supplied with
the readme text files (such as this document).
1. Introduction and Aim
2. Features
3. Syntax
4. Notes
5. Problems
6. Restoration
1. Introduction and Aim
----------------------------
386 HPFS provides the capability to limit the amount of disk space DASD resources take up.
This is especially useful where a large number of users share a limited amount of space.
However, as particular users demands change, you may find that you alter the limits associated
with these resources occassionally.
If, however, you needed to restore your system from tape (if, for example, you had suffered
a harddisk failure) then you would get all your data back, and probably all of your access control
lists (ACLs, if you were using an OS/2 backup program which restored directory information, such
as OS/2 Warp Server's Personally Safe'n'Sound, or Sytron's Sytos).
However, none of these programs, as yet, backup or restore the directory limit information.
In some cases this is not important, but if you have a large number of users or limited diskpace
(which may soon disappear before you can get all the limits back on at the right size) then this
could be a problem.
BACKDASD solves this problem by backing up directory limit information for DASD resources.
It backs up limit size, threshold value and delta, all into an editable text file. This
information can then be restored at a later time by the reverse process, RESTDASD.
Not only does this help you to get your system back up and running in an emergency (because
you won't have to worry about details such as DASD limits) but it also gives you the flexibility
to allow you to have different directories having different DASD limits without you having to
continually make a note of any changes.
It is assumed that you have read the BACKDASD help file before proceeding any further.
2. Features
----------------
RESTDASD has the following features:
a) Identify
You can ask RESTDASD to identify a backup file and report details about it (i.e. date/time of
backup, original backup path and server etc). You can make RESTDASD identify a file and then quit.
RESTDASD defaults to displaying details about a file and what it proposes to do before doing
anything; this however can be turned off.
b) Remote restore
RESTDASD can back up directories or disks on remote servers. You don't have to have an
administrator logged on (or to be logged on at all) to perform a local restore but you have
to be logged on for a remote server restore.
c) Error Log
RESTDASD maintains a comprehensive log. It defaults to using the same file as BACKDASD. RESTDASD
and BACKDASD error codes are similar and the same error codes from either mean the same or similar
problem.
RESTDASD performs many error checks and these errors are displayed to screen and copied to the
log file. You can, if you want, turn off error reporting (not recommended).
c) Speed Optimization
You can specify to bring bring the limits for an entire directory tree (default), or just the
root (non-recursive) or just down to one level.
If a backup file only contains upto one level down then RESTDASD will default to this and will
reject any switches stating /R:1.
BACKDASD contains three backup engines which are used by BACKDASD as and when appropiate.
For example, imaging your directory strutcure starts something like this:
d) Flexibility
You can tell RESTDASD not to restore a limit if an existing limit is already larger.
You can also tell RESTDASD not to restore a limit if the resource is already larger than the limit.
3. Syntax
--------------
Go into the directory containing the RESTDASD utility. This will be the place you asked for
during INSTALL.
Typing RESTDASD /? provides the following information:
RESTDASD Version 1.00beta Release 04/08/96 (c) Steve Sharrad
Internet e-mail: ssha@henleycol.ac.uk
Restores DASD directory limits on 386-HPFS DASD-enabled volumes
from backup files created using BACKDASD.
The syntax of this command is:
RESTDASD /F:[filename] /P:[pathname] [/R:[value]] [/L:[filename]] [/S:\\[servern
ame]] [[/E]] [[/A]] [[/V]] [[/L]] [[F]] [[/T]] [[/I]]
Required Parameters: /F:[filename] Specify a filename to restore from
Default extension is .DSD
Optional Parameters: /P:[pathname] Specify the pathname/tree to restore
to. Defaults to value in backup file
/R:[value] Specify 0 to turn off recursive restore
Defaults to value in backup file (which
may be 0, 1 or 2 (see help). You may
also specify 2 even if the file con-
tains all sub-directories
/L:[filename] Specify a different errorlog filename
Defaults to \DASD.LOG
/S:\\[server] Specify a valid server on domain. If
used, then pathname must be on server
/E Turns-off the error logging to file
/A Bypasses any stop for confirmation
and does not display information
/V Displays information during process
/L Do not restore a DASD limit if any
existing limit is larger
/F Do not restore a DASD limit if the
resource would already not fit in limit
/T Write the operation time and backup
count to error log upon completion
/I Identify the named backup file and
report details, then quit.
/F:[filename]
-------------
Use this parameter to specify a file to restore from. If you don't specify an extension, then
.DSD is assumed.
You should put a fully qualified pathname in front of the filename.
The following parameters are optional.
/P:[pathname]
-------------
This defaults to the pathname held in the backup file, but you can specify an alternative
destination. This could be a different drive or sub-directory.
If you want to restore to a tree which has a space character in the filename, then encapsulate the
pathname in quotes, e.g.
/P:"C:\USERS RULE"
/R:[value]
----------
Use this switch to change the recursive mode. The modes are as follows:
0 Restores the root or parent directory.
1 (default) Restores all sub-directories, if the backup file contains all directories.
2 Restores sub-directories but only down to one level. Saves time on large disks.
/L:[filename]
-------------
Use this switch to specify an alternative location and name for the log file.
/S:\\[servername]
-----------------
Defaults to local workstation.
Use this switch to specify the servername to restore to. This can be any running server on the same
domain (specifying the local workstation name does not fool RESTDASD and makes no difference).
Note that if you use this switch then the pathname pointed to by /P: must be a real pathname
on the specified server. You cannot restore re-directed resources directly; you must use the /S:\\
switch.
/E
--
Stops any entries being written to the error log.
/A
--
Stops RESTDASD displaying information on what it is about to do and asking for confirmation
before it actually does it.
/V
--
Make RESTDASD report verbosely during the restore.
/L
--
Won't restore a limit to a resource if any existing limit is already larger.
/F
--
Won't restore a limit to a resource if the resource is already too large for the limit.
/T
--
Make RESTDASD make entry into error log upon successfull completion of task.
/I
--
Identify the named backup file, report details and then quit.
4. Notes
-------------
Drives must be enabled for DASD limits before any limits can be applied.
This is dones by using NET DASD [drivename] /ENABLE.
You must enable a drive for DASD limits before attempting to restore limits otherwise RESTDASD
will report an error.
You must be logged on as an administrator to restore to a remote server.
5. Problems
----------------
There are no known problems with the software. However, if you do come across a problem, please
make a note of the following after trying again:
- The version of RESTDASD you are using
- The version of BACKDASD you used to create the file
- The command line options you gave to RESTDASD
- The configuration of your computer
- Any error numbers or exitcodes
- RESTDASD contains an in-built freak error handler. This will provide a few lines of debug
information which you should also record
Send details via e-mail to ssha@henleycol.ac.uk. If possible, send also a copy of the DASD
error log and the backup file and a listing of your directory structure.
No fixes garunteed!
6. Restoration
-------------------
If you regularly back up your system, make sure that it backs up the DASD backup files, and if
possible, the BACKDASD/RESTDASD files (they are stored in the OS/2 sub-directory of your system)
and also the file LSRXUT.DLL in the \IBMLAN\NETLIB directory. Otherwise, you will have to re-run
INSTALL and LSRXINST and your backup DSD files will be lost.