![]() ![]() I began looking around for another application that would allow me to keep my local files up to date and GoodSync appeared to be a promising candidate so I downloaded the trial version and installed it.īefore I could even notice that the user interface was far superior to what I had been using I was astonished by the speed of the application. I haven't confirmed that Allway Sync's problem was caused by Pogoplug but Pogoplug creates an enormous number of transcoded files to make photos, audio files, and video files available remotely and Allway Sync crashed constantly when trying to analyze or synchronize files. Until recently I used a file synchronization program from Allway Sync but when I added Pogoplug, Allway Sync was unable to keep up. The trick is keeping those local drives up to date. Files stored on my local disaster-recovery drives are available immediately. So large numbers of files or large files would take some time to retreieve. Files backed up to Carbonite are immediately available but I would have to download them. The files stored at the office will be at least several days old and I'll have to go get the backup drives and restore the data. That's what's on those local drives that sit beside the computer. The notebook computer has most of the applications that are on the desktop so I can continue working as long as I have access to my data. The service interruption lasted about 5 minutes because I was able to start up a laptop computer and attach it to a couple of local backup drives. That eliminates most of the potential disasters but what if the computer stops working and I need my files right now? This is not a hypothetical situation. For that reason I use external backup drives that I store at the office and Carbonite (whose servers are hundreds of miles away). You could get some of the files back but most of them, if lost, are simply lost. How many files are on your computer that, if they suddenly disappeared, you would be at least mildly distressed? Financial records. ![]() Either that or MySQL evolved way before the Microsoft VSS mechanism became mainstream, which also may have bee the case.There's more to backup than just backup. that's why I think this mechanism doesn't exist in MySQL. I believe MySQL was primarily designed, originally, for Linux then ported over to Windows. This demand/response warning system works very well with databases designed primarily for use under Windows. It takes that warning and flushes its memory-based caches to disk, then tells Windows it's OK to put the LOCK on, which Windows will do as soon as it hears back from all who have asked for this service. Most professional database servers that are designed to run under Windows are designed to ask Windows for a WARNING when it intends to LOCK the file system for backup purposes. These types of problems lie in the database servers themselves. Once the now consistent database has been backed up, all should be normal once again. The pre command that would be run would be a FLUSH of that database, insuring the on-disk consistency of all data involved. I believe BVCKUP2 has this pre/post command capability. this guarantees the consistency of the database being backup up. Some folks have used other system/file VSS backup tools that have the capability of running a pre backup/lock command followed by the backup with lock then running a post backup/unlock command. This is pretty difficult if you want set-and-forget backups to occur in the background. ![]() ![]() One of the only ways to insure the consistency of a MySQL database is to stop the server prior to the Microsoft VSS system lock then restart it. Click to expand.Han, a quick look at the net shows that MySQL is not very Microsoft VSS friendly. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |