SnapShot – not what I really thought it was for

Well, I just wasted several hours dealing with SnapShot only to discover that it doesn’t really serve a useful purpose if your website is completely trashed or if you’re trying to use it to move from one hosting provider to another. If you have been working on a WordPress website and have several SnapShots already backed up, I guess it can save you some grief because it gives you some type of “restore point” – similar to the Windows restore points.

But, if your WordPress website has been compromised so bad that you just want to delete it, reinstall a clean version of WordPress and then hit the restore function, fuuuuggggeeettt about it. it just will not do that. If it can, I haven’t been able to figure it out.

Actually, I was moving a client’s website from my hosting to their new hosting. They have FatCow – which I hate for other reasons, the main is because I can’t access the MySQL database using Navicat and they will not make any changes so I can (FatCow’s rules). I had the client put a fresh install of WordPress on the new hosting, changed their name servers, and copied the SnapShot files to the new hosting in the same folder as they were on the old server. SnapShot doesn’t see these files even though the backup folder is set to this location. I’m assuming that something is placed in the MySQL database when a snapshot is made telling SnapShot that a specific backup is in the folder. Remember, I can’t access the database.

This would be so much more functional as a backup/restore/transfer tool if it simply checked the /snapshots folder to see if snapshots existed and then put them in the list of “All SnapShots”. Then, you could copy over a SnapShot back and restore it easily.

My question? Can this functionality be implemented? If not, then I’m not sure I see much value in SnapShot. If I’m wrong on how this works, please offer up the solution because I’ve already wasted too much time on a FREEBIE client. Thanks.