Recovery From Errors During Restore; Using Symbolic Links (Unix Only) - Sybase Adaptive Server IQ 12.4.2 Administration And Performance Manual

Restoring your databases

Recovery from errors during restore

Using Symbolic Links (UNIX Only)

-rw-r--r-- 1 dkusner
-rw-r--r-- 1 dkusner
-rw-r--r-- 1 dkusner
-rw-r--r-- 1 dkusner
-rw-r--r-- 1 dkusner
-rw-r--r-- 1 dkusner
lrwxrwxrwx 1 dkusner
LINKS/asiqdemo.iq1
lrwxrwxrwx 1 dkusner
LINKS/asiqdemo.iq2
lrwxrwxrwx 1 dkusner
/dev/rdsk/c2t6d0s0
408
For an example of the information you see in a header file, see any
line in the sample backup log in "Content of the backup log". A
with produces the information in the same format as the
CATALOG ONLY
backup log entry for an actual
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
the failure occurred, you may need to go back to the previous
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:
sybase 122880000 Feb 26 18:27 asiqdemo.db
sybase 122880000 Feb 26 18:27 asiqdemo.iq1
sybase 122880000 Feb 26 18:27 asiqdemo.iq2
sybase 122880000 Feb 26 18:27 asiqdemo.iq3
sybase 122880000 Feb 26 18:27 asiqdemo.iqtmp
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:
sybase 14 Feb 26 17:48 asiqdemo.iq1 ->
sybase 14 Feb 26 17:48 asiqdemo.iq2 ->
sybase 18 Feb 26 17:48 asiqdemo.iq3 ->
.
RESTORE
. If you were performing a
RESTORE
RESTORE
when
FULL RESTORE
.
FULL BACKUP