Recovering Sybase
Once you have backups of the database, you need to know how to apply them so that you can recover the database in the case of problems. This section discusses how to recover using both cold backups and warm backups and presents a step-by-step recovery procedure. The procedure takes you from trying to start the data server through diagnosing why it did not start, to fixing the problems preventing it from starting. With these procedures and good backups, you should be able to recover from any Sybase problem.
Restoring from a Cold Backup
When restoring a system using a cold backup, nearly everything that was originally backed up needs to be restored. As in the cold backup, the data server must be shut down during the whole restore procedure. Depending upon the circumstances requiring the backup, one or more items might not need be restored. Run through these points to determine which items need to be restored:
Was one of the raw disks or filesystems replaced?
Even if only one of them was replaced, all of them will have to be restored because there is no way to restore only part of a cold backup of the datafiles or raw disks.
Hardcopies of five system tables in the master database (sysusages, syslogins, sysdatabases, sysdevices, sysloginroles) will be needed for the recovery to confirm the recovery was complete. These can be gotten by either bcp ing the tables into text files using the
-coption and then printing out the files or by using the T-SQL select command and ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access