home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 11 Util
/
11-Util.zip
/
BACKRE.ZIP
/
BACKREST.DOC
next >
Wrap
Text File
|
1990-09-12
|
4KB
|
73 lines
***********************************************************************
* WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING *
***********************************************************************
IBM HAS DEDICATED THIS PROGRAM TO THE PUBLIC AND CLAIMS NO RIGHTS
AND PROVIDES NO WARRANTIES WHATSOEVER. IBM PROVIDES THIS PROGRAM
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
***********************************************************************
* WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING *
***********************************************************************
The Backing Up and Restore of databases has grown into a larger task that
diskettes can not handle quickly.
This alternative should help a little.
The Database Manager creates a SQLUFI Directory on the diskette or fixed
disk and the OS/2 E.E. BACKUP.EXE creates either a BACKUP Directory with
BACKUP.001 and CONTROL.001 files or just the files on diskette.
When Database Manager Restore takes place, the SQLUFI directory/files and
the BACKUP Control files are used for validation.
In order to allow the Database Manager to work as design, this alternate
backup will still create BACKUP.001 and CONTROL.001 by backing up some
small set of database files. DBM will still create SQLUFI files and
validation the BACKUP control files, the only difference is that the
intercept backup.exe executes a command file that executes OS/2 BACKUP.EXE
call, so the user can change it to call a user provided program. This could
be a OS/2 Tape program for example. See the command file for instructions.
USER BEWARE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
BACKUP.EXE, RESTORE.EXE, SQLDBACK.CMD, and SQLDREST.CMD can be placed in
\SQLLIB directory.
The user will still need to provide a place for the SQLUFI files and BACKUP
Control files, but they can fix it one diskette or fixed disk other than
the drive where the database resides. Just use Backup/Restore as you would
today (i.e. use drive A:) the only diffence is that a user provided program
can be executed.
Remember that in order to move a database from machine to machine, the copy
protect flag in the database configuration must be off.
The following are files for the alternate backup/restore utilities:
-------------------------------------------------------------------
BACKUP C 12154 9-11-90 7:50p - alternate backup source
BACKUP DEF 128 7-23-90 11:47a - alternate backup definition
BACKUP EXE 14242 9-11-90 7:57p - alternate backup executable
BACKUP LNK 75 6-20-90 11:26a - alternate backup link
RESTORE C 11790 9-11-90 7:53p - alternate restore source
RESTORE DEF 128 7-23-90 11:47a - alternate restore definition
RESTORE EXE 14219 9-11-90 7:57p - alternate restore executable
RESTORE LNK 79 7-18-90 7:16p - alternate restore source
SQLDBACK CMD 4091 9-11-90 7:37p - Database Backup Command File
SQLDREST CMD 4221 9-11-90 7:37p - Database Restore Command File
BACKREST RME 2129 9-12-90 2:34p - Alternate Backup/Restore Read Me
***********************************************************************
* WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING *
***********************************************************************
IBM HAS DEDICATED THIS PROGRAM TO THE PUBLIC AND CLAIMS NO RIGHTS
AND PROVIDES NO WARRANTIES WHATSOEVER. IBM PROVIDES THIS PROGRAM
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
***********************************************************************
* WARNING * WARNING * WARNING * WARNING * WARNING * WARNING * WARNING *
***********************************************************************