There are no problems (like corruption) if the server was power down during backup?
When I restore the backup at a different location how I validate the restored backup? With gfix? There is a formula to indentify that a Database NEED a backup/restore? I mean: If A is 50,000 bigger than B I need to backup/restore. (We use Delphi XE + DataSnap, I belive we have a good transaction control.) De: [email protected] [mailto:[email protected]] Em nome de Ann Harrison Enviada em: sábado, 19 de novembro de 2011 21:38 Para: [email protected] Assunto: Re: [firebird-support] When I need to do a full backup/restore? Fabiano wrote: > I read MUCH about avoid firebird problems/corruptions by backup/restore the > Firebird database eventually. The best approach appears to be every day - in > my case at night when there's no one connected to database. You should do a backup nightly, with the database accessible to customers. Once a week, restore a backup to a different location - preferably on a different machine, to validate that the backups are good and can be restored. I wouldn't bother replacing the working database by taking it down, backing it up, restoring it, and restarting it unless I knew there was a problem. The regular backups will force garbage collection. You might reset the selectivity of indexes weekly as well. > Good luck, Ann [Non-text portions of this message have been removed]
