sybase增量备份和恢复的问题

zy407321952

sybase11.0.3   想用增量备份试一下，sybase增量备份要先做一下全备，备份过程没问题，但是恢复的时候有个问题：
load tran testdbs from '/day/test.bak'
go
提示错误信息：
Msg 4305, Level 16, State 1:
Line 1:
Specified file 'dump device' is out of sequence. Current time stamp is May  8
2013  9:11AM while dump was from May  8 2013  9:14AM.
我的全库备份是在9:11的时候做的，增量备份手动添加了几条记录，是在9:14做的备份，为什么恢复的时候提示我数据库的时间戳在9:11，是因为我恢复的时候时间戳也变成了9:11吗？可是增量恢复的时候貌似都是要先做一个全库恢复然后再使用增量备份恢复，求解，网上找不到解决办法，官方文档写的太无语，看了好几遍都没看到solution，有人做过sybase的增量备份吗？
Error 4305

Severity

16
Message text

Specified file '%.*s' is out of sequence. Current time stamp is %S_DATE while dump was from %S_DATE.
Explanation

During a load transaction, Adaptive Server checks the timestamp on the dumped database and each dumped transaction log to determine whether the sequence is correct. If the load sequence of the transaction logs is incorrect, error 4305 occurs and the load fails.

If you are missing a transaction log dump, you can only restore up to the transaction log dump before the missing dump.

In addition, you cannot load multiple transaction log dumps that have been created with the no_truncate option. The no_truncate option assumes that nothing further will be done with the transaction log after that point: it is only useful for up-to-the-minute recovery of a database after failure of the data device. If you have used the no_truncate option and your database is still okay, do a dump database as soon as possible.

This error is serious as the load processing stops and the load transaction fails.

Action

Load the log backups in the same sequence in which they were made. Check your transaction log dumps to determine whether one was loaded out of order. If you find the correct dump, load it and continue with the rest of the dumps, in order.

Additional information

For more information, refer to “load transaction” in the Reference Manual: Commands.

Versions in which this error is raised

All versions

zy407321952

找到哪做错了，O__O"…  现在可以了。

wang_xue_m

请把哪里出现的问题，怎么解决的。共享出来，谢谢

zy407321952

回复 3# wang_xue_m


    是因为我执行备份的时候使用了dump transaction testdbs with truncate_only来清除日志，查资料发现sybase增量备份是用日志来做的，所以导致增量备份无法恢复。

wang_xue_m

要是不截断日志的话，日志空间会满，看来你得经常做增量备份，备完，再截断

zy407321952

回复 5# wang_xue_m


    我又试了下，貌似跟dump transaction with truncate_only没多大关系，我在执行备份前后都执行了该命令，没问题，那天确实很奇怪，我也就多执行了下这条命令就出现了时间戳不匹配的错误，我现在做增量备份只会在全备的时候使用这条命令来清除日志，现在应该就没问题了。