Use sybrestore to restore an SAP ASE
database to the time of failure from the most current full database backup dump
files.
sybrestore can be used to restore a database:
- from the most current backup in the dump history.
- from the server integrated with Tivoli Storage Manager (TSM).
- to the same server or to a different target server.
- to different database name, or to a re-created new database on the same server.
- to a new database on a different target server.
- from cumulative dump.
- from a master database corruption.
sybrestore offers two modes—interactive and noninteractive—and is
supported on both Windows and UNIX platforms.
sybrestore also allows applying database attributes via
sp_dboption when a database is re-created and restored from the dump
file.
Noninteractive Mode
To use noninteractive mode:
- Use SAP ASE 15.7 ESD #2 and later.
- The target and source servers must be the same server and the target database to be
restored must be the same database as the source.
- You cannot use external dump files.
- Specify the server name, a user name, and the database name. If you do not provide a
password, you are prompted to do so when you invoke sybrestore.
- (Optional) Specify a dump directory and an interfaces file.
Interactive Mode
In interactive mode, you can specify:
- To restore a master database.
- A different target server than the source server. If the target database you specify
does not exist, a new database is automatically created.
- Whether the last transaction is dumped from the source server and loaded on to the
target server. If your data device fails and the database is inaccessible, the dump
transaction does not truncate the log.
- Whether to drop and re-create the database.
- Whether to use the current dump history files or external dump files.
- The location for the dump transaction.
- Whether to bring the database online immediately after the restore.
- A point in time, within the range of time during which the database is backed up in
the dump history files, from which to restore the database.
- To reinitialize and re-create the database devices of an offline database for which
the devices are offline. Then restore the re-created database.
- To log output to a file.