Database Backup Strategy

[#1]

I think I need to implement a better backup strategy. I'm thinking this:

Every day at 1am: validate db and if ok, full backup to another disk + copy to dat + copy to amazon s3 (encrypted). If validate fail, send me an email.

From 1am to 23:59: incremental backup to another disk + copy to amazon s3.

Keep each backup 6 days (i.e.: every monday I'll overwrite previous monday backup).

Incremental backup, what you think to put events in database to do this, every 15min or 10mb log file - recreating log file.

That is time, my db size is 80.1gb growing about 60mb/day.

Is this a good strategy? Should I change something? What can happen if inc backup is running and another inc backup starts?

Thank you and sorry this too long question. And again, sorry my poor english.

[VolkerBarth]

Just to add to Mark's response and the according comments:

When doing incremental backups, I would make sure to store the log to different files (possibly in a round-robin scheme using a few file names). I.e. you could store the backup log file from 1:00 and 1:15 to different files. This should make sure that a failing backup or file copy operation would not damage your "last good" file.

Note: Your question seems that you use different files names/directories for the daily full backups, but I was not clear about your differential backups.)

Furthermore you could check the validity of the backup logs by running DBTRAN against them, cf. the help.