At 24megs per file, and all files named the same - they add up quick. I could create 31 different directories and each date f the month overwrite the file from a previous month - but isn't that really the same thing as the way I'm doing it? If a file is currupt, it is currupt and having 2 or 31 or 365, eventually if a problem exists it will bite us in the rear.
At some point we just have to have faith. I don't think it matters how many loterry tickets you hold in your hand for the Mega-Lottery is going to change your chances of winning.
The only proble we had concerning a file was that (and I'm sure THIS is what happened) was that on my work computer, someone accessed our forum and deleted all the forums and then saved the backup file. That is what the server guy thinks and our work multi-user computer using Win2000 has a serious flaw in its data saving ability in multi-user.
When I go to Hotmail for example, I see the saved username and password ****** of the last person in my shop that used hotmail. I even have the same history file in Netscape AND Explorer as EVERYONE else. We all update each others history file - it is a FLAW and the NMCI people who are the owners and operators of the system know it exists.
I was FOOLISH enough to check the REMEMBER ME option in the forum in the work computer and someone went to my website, clicked on the forum, entered as me - saw they had admin powers and started deleteing every freakin thing they could THEN saved it. There was nothing left, but WHAT really crashed the saved file was the template was messed with.
MY PROBLEM was that I hadn't saved a backup on my home computer for about 10 days - and when I tried to upload it, the template part of the file info couldn't justify itself and the server guy needed to dump the old file and reinstall the only backup I had.
I don't think CURRUPTION is a problem - it is idiots whos NECK I would love to ring that caused the problem. I think 2 backups are fine - I could save more, probibly wouldn't hurt, but I think even one would fix the problem as long as the damaged file on the server can be removed by ME or the server guy.
It is having a current backup with all the messages and members that is important - and I'm backing it up every day. I learned a lesson that day, that was NEVER STAY LOGGED IN at work.
Besides that, we have NEVER had an issue of backup files.