The Backup utility
80
Connection parameters (–c) For a description of the connection
parameters, see "Connection parameters" on page 64 of the book ASA User’s
Guide. If the connection parameters are not specified, connection parameters
from the SQLCONNECT environment variable are used, if set. The user ID
must have DBA authority or REMOTE DBA authority.
For example, the following command backs up the asademo database
running on the server sample_server, connecting as user ID
DBA with
password
SQL, into the
asabackup
directory:
dbbackup -c "eng=sample_server;dbn=asademo;uid=DBA;pwd=SQL" asabackup
Backup main database only (–d) Back up the main database files only,
without backing up the transaction log file or a write file, if one exists.
Live backup (–l lower-case L) This option is provided to enable a
secondary system to be brought up rapidly in the event of a server crash. A
live backup does not terminate, but continues running while the server runs.
It runs until the primary server crashes. At that point, it is shut down, but the
backed up log file is intact and can be used to bring a secondary system up
quickly.
Change backup transaction log naming convention (–n) This option
is used in conjunction with
-r. It changes the naming convention of the
backup transaction log file to
yymmddnn.log
, where nn is a number from 00
to 99 and
yymmdd
represents the current year, month and day.
The backup copy of the transaction log file is stored in the directory specified
on the command line, and with the
yymmddnn.log
naming convention. This
allows backups of multiple versions of the transaction log file to be kep in
the same backup directory.
The two-digit year notation does not cause any year 2000 problems. The
names are used solely for identification, not for ordering.
Log output messages to file (–o) Write output messages to the named
file.
Operate quietly (–q) Do not display output messages. This option is
available only from the command-line utility.
Rename and start new transaction log (–r) This option forces a
checkpoint and the following three steps to occur:
♦
Step 1 The current working transaction log file is copied and saved to
the directory specified in the command line.
To Next Page
Loading...