Subject Re: DB modified date is over a month old, but Forced Writes are ON??
Author Raymond
> To be safe, do the backup without taking the database down,
> restore it to a different
> file and location, and validate that the month's data is
> there. But I think you're just
> seeing a Windows quirk.


Thanks Ann and Woody!!!!

I did a hot backup and that worked fine - log files were fine! (whew!! I can breathe again!)

On Linux I always stopped the Firebird daemon and that closed all the db's so that I could run gbak

but Windows does not quite behave the same ...

Does this sound correct? I need to shutdown the database (leave FB running) with gfix, gbak backup, gbak restore, move to using the newly restored db

gfix -sh -tr 300 scmaster
gfix -sh -f 300 scmaster

//backup db
gbak -b -v -user sysdba -password ***** -y “D:\SCMaster\temp\SCMaster20110608_backup.log”
scmaster “D:\SCMaster\temp\SCMaster20110608.fbk”

//restore db
gbak -c -v -user sysdba -password ***** -y “D:\SCMaster\temp\SCMaster20110608_restore.log”
“D:\SCMaster\temp\SCMaster20110608.fbk” “D:\SCMaster\temp\SCMasterNew.fdb”

copy, move, and delete old rotations of files as needed...

Does this make sense? - or should I consider a different approach?

Many thanks,
-Raymond