As an IT professional, I suggest you use transactional backups... that way you can return to the single point of failure for a restore as opposed to what you are doing now... a manual backup? Once a week? Only when there is a programming change?
As an IT professional, I suggest you use transactional backups... that way you can return to the single point of failure for a restore as opposed to what you are doing now... a manual backup? Once a week? Only when there is a programming change?
Actually, we have it setup to backup every hour. However, the backups stopped at 12-31 at 11:30 PM, I assume due to the year change over (a bug in the backup software in any case). It goes without saying that we'll be switching to a different backup solution. Actually, that's part of what I have been doing, in addition to considering and working on solutions that would best address the actual issue for all players...researching the best solution for database backup.
Antilles (01-02-2010)
Paragon, and BackupAssist are both good backup software solutions.
Neither of those cover MySQL databases. Not to worry. We have a triple redundant system in place now.