Hello, Instead of using the MAXDB 7.5 tools (backup_start) for a full online database backup I would like to use the SNAP function on our SAN (hardware). So I freeze the MAXDB database by suspending the log writer to create a consistent backup (data and log files) with the commands:
dbmcli -D database -uUTL -u dbm,dbm util_execute suspend logwriter <then I create the SNAPSHOT from the LUN's with the DATA and LOG volumes (comparable with split mirror) in seconds with the SAN functionality> dbmcli -D database -uUTL -u dbm,dbm util_execute resume logwriter Since database startup, the autologging function is switched on (autolog_on), so all database actions are logged in number trailered logfiles. After the SAN backup (in this example a tar file with the LOG and DATA files) I generate some load up to the point where 6 logfiles have been written. So I have a full database backup (the tar file) and I have the logfiles to perform a point-in-time recovery (rollforward). The next files are available for recovery: -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:39 autoLOG_TESTDB.bak.002 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:39 autoLOG_TESTDB.bak.003 -rw-r--r-- 1 sdb sdba 999443456 Jan 28 09:40 SNAP_TESTDB.tar -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:40 autoLOG_TESTDB.bak.004 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:40 autoLOG_TESTDB.bak.006 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:40 autoLOG_TESTDB.bak.005 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:41 autoLOG_TESTDB.bak.007 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:41 autoLOG_TESTDB.bak.008 -rw-rw---- 1 sdb sdba 5701632 Jan 28 09:41 autoLOG_TESTDB.bak.009 Test recovery: I shutdown the database (db_stop), I remove the DATA an LOG volume files and put the SAN SNAPSHOT with the DATA and the LOG volumes back (the restore from the full database). 1. Restore SNAPSHOT from files as they are: When I (db_start) online the database, everything is normal, database is consistent. Everything works fine. 2. Restore SNAPSHOT from files and recover logs (rollforward): I open the database in db_admin mode, open a utility session and try to perform recovery (rollforward) on the database with the 6 logfiles that were created after the SAN snapshot (tar file). After the first recover_start the database is in the db_online state and I cannot proceed recovery (LOG 005). I used the next commands in a dbmcli session to recover: db_admin util_connect recover_start auto_logF LOG 004 recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak005 recover_start auto_logF LOG 005 recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak 006 recover_start auto_logF LOG 006 recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak 007 recover_start auto_logF LOG 007 recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak 008 recover_start auto_logF LOG 008 recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak 009 recover_start auto_logF LOG 009 recover_cancel util_release db_stop db_start The output I get is: >recover_start auto_logF LOG 004 OK Returncode 0 Date 20050128 Time 00094836 Server u25 Database TESTDB Kernel Version Kernel 7.5.0 Build 018-123-079-776 Pages Transferred 424 Pages Left 0 Volumes Medianame auto_logF Location /data/backup/autoLOG_TESTDB.bak.004 Errortext Label LOG_000000004 Is Consistent First LOG Page 2700 Last LOG Page 3517 DB Stamp 1 Date 20050128 DB Stamp 1 Time 00093911 DB Stamp 2 Date 20050128 DB Stamp 2 Time 00093928 Page Count 817 Devices Used 1 Database ID u25:TESTDB_20050128_093836 Max Used Data Page --- >recover_replace auto_logF /data/backup/autoLOG_TESTDB.bak 005 ERR -24988,ERR_SQL: sql error -8888,connection broken server state 10 PS: I cannot use autorecovery because the backup history is incomplete (SAN snapshots are not registered and there are no previous "backup_start" full backups). Can someone tell me what I am doing wrong and what dbmcli commands I shoud issue to get backup/recover (point-in-time) working using our SAN snapshot functionality? Regards, Jos Weijers -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
