Restoring your databases
408
For an example of the information you see in a header file, see any
RESTORE
line in the sample backup log in “Content of the backup log”. A
RESTORE
with
CATALOG ONLY
produces the information in the same format as the
backup log entry for an actual
RESTORE
.
Recovery from errors during restore
If an incremental restore fails early in the operation, the database is still usable
(assuming it existed and was not corrupt before the restore). If a full restore
fails, you will not have a usable database.
If a failure occurs after a certain point in the operation, the restore program
marks the database as corrupted. In this case recovery is only possible by
means of a
FULL RESTORE
. If you were performing a
FULL RESTORE
when
the failure occurred, you may need to go back to the previous
FULL BACKUP
.
Using Symbolic Links (UNIX Only)
If you use symbolic links, you may unknowingly cause dbspaces to be created
in a different directory from where you may want them to be. For example,
suppose you have created dbspaces in the following files:
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.db
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq1
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq2
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iq3
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iqtmp
-rw-r--r-- 1 dkusner sybase 122880000 Feb 26 18:27 asiqdemo.iqmsg
If you create the following links beforehand, then the dbspaces, when they are
created, are actually created in the directories (or on the raw partitions) pointed
to by the links:
lrwxrwxrwx 1 dkusner sybase 14 Feb 26 17:48 asiqdemo.iq1 ->
LINKS/asiqdemo.iq1
lrwxrwxrwx 1 dkusner sybase 14 Feb 26 17:48 asiqdemo.iq2 ->
LINKS/asiqdemo.iq2
lrwxrwxrwx 1 dkusner sybase 18 Feb 26 17:48 asiqdemo.iq3 ->
/dev/rdsk/c2t6d0s0
Summary of Contents for Adaptive Server IQ 12.4.2
Page 1: ...Administration and Performance Guide Adaptive Server IQ 12 4 2 ...
Page 16: ...xvi ...
Page 20: ...Related documents xx ...
Page 40: ...Compatibility with earlier versions 20 ...
Page 118: ...Troubleshooting startup shutdown and connections 98 ...
Page 248: ...Importing data by replication 228 ...
Page 306: ...Integrity rules in the system tables 286 ...
Page 334: ...Cursors in transactions 314 ...
Page 396: ...Users and permissions in the system tables 376 ...
Page 438: ...Determining your data backup and recovery strategy 418 ...
Page 484: ...Network performance 464 ...
Page 500: ...System utilities to monitor CPU use 480 ...
Page 514: ...Characteristics of Open Client and jConnect connections 494 ...
Page 536: ...Index 516 ...