"I wrote a batch file back in June that basically copies 3 things to a different drive: the MySQL db, my localhost on C: where I integration test my code, and critical files from my development environment which includes the code I'm working on and relevant files linked to such as images, docs, etc. and a miscellaneous folder where I keep notes and saved versions of files I'm working on."
"I was so confident of the backup batch file process that I didn't bother to verify that the MySQL folder in the backup drive, backup generation folders contained valid content before I flushed my db (under Claude's guidance) because to clear the missing mysql.proc error I had to recreate my db. No problem: I have 3 generations of backup. The most I could lose would be a day or 2 of changes."
Resolving a missing mysql.proc error required recreating the MySQL database and caused deletion of the entire database. The database contained only a small lookup table pair but represented about two months of schema work. A June batch file copied three targets to another drive: the MySQL data folder, the localhost C: integration-test folder, and critical development files including code and linked resources. The batch file maintained three generations of backups and ran daily via Windows Task Scheduler. The MySQL folder in the backup generations did not contain valid content when the database was flushed, so the presumed backups could not restore the schema.
Read at SitePoint Forums | Web Development & Design Community
Unable to calculate read time
Collection
[
|
...
]