Required Parameters: /F:[filename] Specify a filename to backup to
Default extension is .DSD
/P:[pathname] Specify the pathname/tree to backup
Optional Parameters: /R:[value] Specify 0 to turn off recursive backup
Specify 1 (default) to backup all sub-
directories, or 2 to backup only sub-
directories upto 1 level down.
/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
/C Displays info and asks for confirmation
/V Displays information during process
/T Write the operation time and backup
count to error log upon completion
/F:[filename]
-------------
Use this parameter to specify a file to backup to. If you don't specify an extension, then
.DSD is assumed. If the file already exists a backup copy will be made.
You should put a fully qualified pathname in front of the filename.
/P:[pathname]
-------------
Specify the tree to backup. If you want to backup a whole drive, then specify the root, e.g.
/P:C:\.
If you want to backup a tree which has a space character in the filename, then encapsulate the
pathname in quotes, e.g.
/P:"C:\USERS RULE"
The following parameters are optional.
/R:[value]
----------
Use this switch to change the recursive mode. The modes are as follows:
0 Backs up the directory specified by the /P: switch but no sub-directories
1 (default) Backs up all sub-directories. Could take some time on large disks.
2 Backs up 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 the local workstation.
Use this switch to specify the servername to backup. This can be any running server on the same
domain (specifying the local workstation name does not fool BACKDASD 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 backup re-directed resources directly; you must use the /S:\\
switch.
/E
--
Stops any entries being written to the error log.
/C
--
Make BACKDASD display information on what it is about to do and ask for confirmation before it
actually does it.
/V
--
Make BACKDASD report verbosely during the backup.
/T
--
Make BACKDASD make entry into error log upon successfull completion of task.
4. Notes
-------------
Drives must be enabled for DASD limits before any limits can be applied.
This is dones by using NET DASD [drivename] /ENABLE and restarting the workstation.
You must be logged on as an administrator to backup a remote server.
If the /S:\\ switch is used, then the pathname must be on the remote server.
Creating an AT schedule:
OS/2 prompt
AT 20.00 /EVERY:M,T,W,TH,F,S BACKDASD /F:c:\backup\cdrive.dsd /p:c:\ /l:c:\ibmlan\logs\dasd.log /t
This creates an AT schedule which runs at 8.00pm every evening of the week
except Sunday. It calls BACKDASD and backs up all DASD limits on the C drive.
The file is stored in C:\BACKUP. Logging is to a file in C:\IBMLAN\LOGS. BACKDASD
also writes to the error log upon completion so that this file can be checked to
make sure the backup went OK.
Ideally, instead of calling BACKDASD, the AT scheduler should call a batch
file which calls BACKDASD, then BACKACC (if needed) and then your tape
backup software. Note that if you wish to use BACKDASD from another .CMD batch file, then the CALL command must be used
otherwise when BACKDASD finishes it will not return back to the calling .CMD file.
Note that BACKDASD can return error codes back to the calling process if the /V
switch is used. If you are using the AT command, then do not use the /V switch; you won't see any
information anyway but the /V switch causes the whole of the calling process indicated by
the AT command to be aborted (if BACKDASD encounters an error and returns an error code).
If you have a large number of DASD limits below a path (in excess of 1000) then it is possible
that BACKDASD will report error BACKDASD 0005: Insufficient stack space.
This can be cured by editing the BACKDASD program file and increasing the buffersize value at the
top of the file. I've never exhausted the buffer because I've set it quite high, but if you do
get this error then BACKDASD will report an estimate of what it thinks it should be set to.
Maximum Backup Size
In fully recursive mode, BACKDASD can back up upto about 1,600 DASD limits (depending on the length of the directory names).
You will find that BACKDASD fails if there are more limits to be backup up but BACKDASD runs out of memory, and returns error 14.
You have two options:
i) Use Recursive Mode 2. If all of your DASD limits are user home directories one-level down off a main tree, then use /R:2.
ii) Use normal mode but split the backup into several main trees.
iii) Increase the amount of memory BACKDASD is allowed to use. Make a backup copy of the BACKDASD.CMD file, and then open it using the E editor. On the first page you will notice a value called DASDInfo.Buffersize.
The value is in bytes. The default value is 6018000. Increase the value inside the inverted commas to allow BACKDASD to use more memory.
Default: DASDInfo.BufferSize='6018000'
Note that if you specify a value ludicrously high, then BACKDASD uses a smaller value and even less is backed up.
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 BACKDASD you are using
- The command line options you gave to BACKDASD
- The configuration of your computer
- Any error numbers or exitcodes
- BACKDASD 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 any partially created backup files and a listing of your directory structure.
No fixes guarunteed!
There are two limitations with the current release of BACKDASD:
- You cannot call BACKDASD from another intelligent REXX script unless ADDRESS is used. You can use the CALL command to invoke BACKDASD from a normal .CMD batch file, however.
- Maximum size of buffer; this can be increased if needed by user.
