Date: July 2007
Affected NV Version: 7.4.x
OS Version: ALL
Plugin version: ALL
Application version: ALL
Description:
A Full Sybase database backup completes successfully, but Incremental or differentals fail or hang.
Symptoms:
To test and receive the associated error message with the failure
perform an manual incremental dump within the Sybase ISQL interface :
Log in to ISQL and issue the following:
1> dump TRAN to " "
2> go
The command to enter would be for database named imdb that will create a backup file myfile.dat:
1> dump tran imdb to "imdb.dump"
2> go
If the following ouput/error message is received:
Msg 4205, Level 16, State 1:
Server 'SYBASE', Line 1:
Syslogs does not exist in its own segment in database 'imdb' with segmap '7' with logical start page
number of '0'. You cannot use DUMP TRANSACTION in this case, use DUMP DATABASE instead.
**The receipt of this message confirms that it is the location of the transaction logs that is causing the
incremental backup failure.
An incremental or differential backup of a Sybase database is only possible when the data and
logs are configured to reside on different devices. An error occurs if both data and logs reside
on the same device and an incremental or differential backup is attempted.
This happens because the NetVault incremental and differential backups are equivalent to the Dump
Transaction command of Sybase that backs up the transaction logs. Sybase uses the
transaction logs only in the event of disk failure in which case it is essential that this file
exist in a different device.
To enable the incremental backup to take place you must move the transaction log to a separate device.
This is achieved by using the Sybase procedure "Moving the Transaction Log to Another Device".
the utility used is sp_logdevice syntax as follows:
sp_logdevice database_name, devname
This is detailed within the Sybase SQL Server Administration Guide for the version of Sybase installed.
Please refer to the appropriate Sybase documentation.
BakBone SFDC Solution Number: 00000262
