home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: SysTools
/
SysTools.zip
/
backres.zip
/
README.PSS
< prev
next >
Wrap
Text File
|
1999-03-15
|
12KB
|
272 lines
OS/2 Warp Server Backup/Restore V6.01.0 15 March 1999
------------------------------------------------------
This readme file contains the following information:
1) Installation notes
2) Code defects (APARs) fixed since the release of V6.00.
3) Uninstallation instructions
3.1) Uninstalling through the Graphical User Interface
3.2) Performing an Unattended Uninstall
4) A list of known restrictions and problems
5) Performance recommendations
6) Logging
7) Use of the Command Line Interface
8) Dynamic allocation of drive letters for partitioned
removable hard disk devices: How this effects PSnS
operation
**************************************************
1) Installation notes:
-------------------
Whenever you install a new version of OS/2 Warp Server Backup/Restore
you should recreate your disaster recovery diskettes. If you do not you may
find that you cannot perform a disaster recovery from backups that you have
taken with the new release. The current version allows the program files to
span on to multiple diskettes if necessary. This means that you may have to
provide more than three diskettes when creating disaster recovery diskettes.
Please refer to the Backup/Restore web site for up to date answers to common
questions and advice on how to implement your backup strategy.
http://www.software.ibm.com/os/warp/library/backfaq/index.html
2) Code defects (APARs) fixed since release of V6.00
------------------------------------------
This is a chronological list with the most recently fixed problems at the bottom.
IC20835 Client C program occasionally quits when calling PSnS API Server
IC20930 Files stored in ADSM lost if there is an identical path on a different drive
IC20884 SYS3175 or panic 005 entering user exit after backup or restore
IC21277 Apparent "out of memory" error in API client program when running
backup method with statistics call-back function.
IC21594 GO disaster recovery program fails with a SYS2070 - failure to load
the PSNSVM.DLL
IC22044 Failure to decompress a particular file
IC22556 Failure to return correct error code through the REXX API when no backup
volume present
3) Uninstallation instructions
---------------------------
Uninstalling device support will mean that you will not be able to restore data
backed up to that device.
Uninstalling both the C API component and the Graphical user interface will
mean that you cannot run OS/2 Warp Server Backup/Restore. It will also result
in all of your backup sets being deleted.
3.1 Uninstalling through the Graphical User Interface
------------------------------------------------------
Double click on the "Uninstall Backup/Restore" icon in the OS/2 Warp Server
Backup/Restore folder. This will take you through the uninstallation
program. You may uninstall one or more components of the program. If you
uninstall all the components OS/2 Warp Server Backup/Restore will be
completely removed from your system.
3.2 Performing an Unattended Uninstall
--------------------------------------
To uninstall OS/2 Warp Server Backup/Restore enter the following
single-line command at an OS/2 command prompt:
clifi /a:u /f:"<WP_INSTALLED>" /o:INV_PSNS /set:Selection=ALL
This will completely remove OS/2 Warp Server Backup/Restore from your
system.
4) Known Restrictions and problems
----------------------------------
- The OS/2 Warp Server Backup/Restore 'disaster recovery guide' gives
instructions for building disaster recovery diskettes which enable you to
boot your system and restore data in the event of a hard disk crash. The
instructions advise you to use the OS/2 MAKEDISK utility to modify the system
for use with HPFS386 partitions. You may find that MAKEDISK fails because
there is insufficient space on the diskette for all the required files.
If this is the case you should ignore the instruction to run MAKEDISK. You
will still be able to disaster recover data to a 386HPFS partition provided
you have reformatted the partition first. (If you do not reformat the
partition some files and directories may contain embedded access control
permissions that cannot be overwritten during the restore. The restore will
fail.)
Note: You will still be able to restore the access control permissions by
restoring the NET.ACC file in the normal way once you have rebooted your
machine.
- BACKACC, the utility invoked by Backup/Restore to backup the NET.ACC
file, scans all attached drives. If you have a removable media drives attached
which does not have a cartridge inserted, BACKACC will issue a warning that
the drive is not ready. The backup will be halted until you have pressed 'Return
error to program'. This can be avoided by leaving a cartridge in the drive when
the backup runs.
- If you may want to restore from a dual device backup set in disaster recovery
mode (having booted from diskette) you are advised to work in the following way:
Do NOT transfer out the backup set to the base device. During disaster recovery
you will typically want to restore from the base device only to restore a
bootable system. If you have transferred out the backup set to the base device
PSnS will try to restore both the base image and the increments. Although this
works fine it depends on you having BOTH the base and incremental devices
accessible and working while you are recovering. It is less risky to assume
that only one device (the base) will be operational in this situation. Having
recovered your system from the base device and rebooted the machine you can
restore the increments in the normal way through the graphical interface.
(Just transfer in the backup set from the incremental device and create a restore
method that restored all the files from it. When you run the restore method opt
to restore only files from the incremental device since you will have already
restored all the base files.)
- When transferring in a dual device backup set you will be asked to confirm the
names and settings for the two storage devices that you want to use for
the backup set. This is because you may be transferring in on a target machine
that does not have exactly the same set of devices attached as there were on
the original machine. For example, your ZIP drive may appear as a different
drive letter. Backup/Restore will prompt you to choose from the list of
possible devices attached to your system.
- C API backup methods do not function properly if the backup device on the
target Backup/Restore server requires a new volume to be inserted.
- If you backup files from a FAT partition and view them using the 'View backed
up data' option, you will notice that the file creation date is set to zero. This
is because the FAT file system does not store the creation date of a file.
- The date format on the "Prompt for Version" panel during restore is the
traditional English Day/Month/Year. The panel does not adapt to your
OS/2 date preferences.
5) Performance recommendations
-------------------------------
1) You are advised to install OS/2 Warp Server Backup/Restore on an HPFS or JFS
drive.
2) You are advised not to create backup sets on FAT drives.
6) Logging
----------
If you experience a problem when running this code, you can turn
problem logging on. Here is how you do this...
1) Open an OS/2 window, making sure that Backup/Restore is not running
2) Change directory into the directory where Backup/Restore is installed, e.g.:
cd PSNS
...if you installed Backup/Restore in a directory called 'PSNS'.
3) Type the following command:
SET PSNSDEBUG=4
4) Then type:
PSNS
...to run the program with problem-logging enabled.
This will produce a log file called 'psns.log', which is found in the
current directory. This file can be used by IBM to help
determine the cause of the problem.
Alternatively, include the statement 'PSNSDEBUG=4' in your config.sys file.
After doing this and re-booting, a log will be produced whenever you run Backup/Restore.
This means that you don't have to go through the steps detailed above.
This log file may become very large.
7) Use of the command line Interface (CLI)
------------------------------------------
To view on-line help for the CLI type:
psnscl help
This gives you a full list of the key words, such as 'backupmethod', that
can be used in your native language. To get detailed help on a given
key word, type the following:
psnscl help KEYWORD
(Replace KEYWORD with the key word for which you need help. To get help
on the backupmethod key word you would type: 'psnscl help backupmethod'.)
This will show you which verbs apply to the key word. You can then
request more detail on these by typing the following type of command in your
native language:
psnscl help KEYWORD VERB
(Replace VERB with the verb for which you need help. To get help on
creating backup methods you would type 'psnscl help backupmethod create'.)
Help for all keywords and verbs is available in this way.
Dynamic allocation of drive letters for Partitioned Removable Media (PRM):
-------------------------------------------------------------------------
How this effects PSnS operation
-------------------------------
Warp Server for e-business does not allocate a drive letter to PRM until
a cartridge is inserted. This has some consequences for PSnS of which you
should be aware.
a) How to create a new removable hard disk storage device:
PSnS normally creates default storage devices on each of the devices that you
have attached. This may not happen for Partitioned Removable Media because
the operating system only detects these devices and assigns a drive letter to
them if the device contains a cartridge. If PSnS has not created a storage
device on your removable hard disk you need to do the following:
1) Insert a cartridge in the removable hard disk device
2) Start PSnS and open the source drives container. Use the 'refresh' context
option to refresh the set of available source drives. You should see a removable
hard disk icon appear in the container.
3) Open the PSnS storage devices container. Use the 'refresh' context option to
refresh the set of available storage devices. You should see a removable hard
disk icon appear in this container also.
You should now find that PSnS has also created a default backup set on the new
storage device and you are ready to run backups to this.
(These same actions can be taken using the API.)
b) You should try to ensure that a removable hard disk device used by PSnS as
a backup device is always assigned the same drive letter whenever a cartridge
is inserted. You may use the Logical Volume Manager (LVM) to assign the same
preferred drive letter for each of the cartridges that you want to use, but
this does not guarantee that the device will always be allocated this letter.
In particular your CD-ROM drive may take the chosen drive letter if you boot
without a removable cartridge installed. One way that you can control this
situation is to include the following statement in your config.sys file:
ReserveDriveLetter=x
This will ensure that the CD-ROM drive will not take any drive letter lower or
equal to x (for example, x could be the drive letter you want your removable
media device to take.)
See the section 'Partitioned Removable Media Considerations' in the book 'Quick
Beginnings' (a3aa1mst.inf) for more information about the Logical Volume Manager
and Partitioned Removable Media.