Backup 5.8 - Updated 27/10/2010

[Owyn]

Is there a known maximum size for the zip?

800MB is too big.

Yeah. I saw your prior comments which was I am starting to get concerned.
The current dedicated tools support at least 2GB uncompressed files.

Hmmm. Do you happen to have any of your prior successful backup zip files around? That would give a better reading on maximum supported size.

[Lowlander]

Sorry, didn't start using the script until I reached that size.

[Owyn]

Guess I am on the bleeding edge.
If it happens I can do a full optimize on the database. I probably have a lot of slack due to deleted podcast episodes.

[sonofjon]

Just installed this script (never used it before on my current machine), version 5.4. I get the "unknown name" error when running the script. Reverted to version 5.3, get same error. I run MM as administrator.

[Mizery_Made]

Here is something I was thinking about last night as I was shutting down MediaMonkey prior to shutting down the PC. That is, there are times where I have pulled MM up and done nothing with it. Perhaps because I was looking up a piece of information in my library, don't remember. I have MM set to backup upon shutdown however, so even though there was really no changes to backup, I got one anyway. What I was thinking was, if it were possible to add an option for some kind of confirmation. Like when I shut down MM, it asks me, "Do you want to perform a backup?" and I could then either say yes or no. That way, I wouldn't have to perform an unnecessary backup in those situations. I guess it could be one of those situations where the "useful scenarios aren't likely in comparison to the other, and therefor not beneficial to account for them" or whatnot. Don't know... just my head coming up with a random thought and then me tossing it out there.

[MusicBringer]

I never even thought about the output path, because I always use "D:\Backup\MediaMonkey\" and then use the mask fields in the zip file. This is an oversight, I'll make sure folders are also deleted in the same way in the next version.

Dunno if I missed it, but did the Delete Folders feature get added, please.

Has it happened yet

[trixmoto]

@Mizery_Made - even though you've not made any changes, things may have happened in the background if you have file monitoring on, or any of the automatic features. I probably could look at adding this, although popups in the "OnShutdown" event can cause problems from my experience.

@MusicBringer - yes, I added this in version 5.4, released 10 days ago.

[Owyn]

@Mizery_Mode:
I considered backup at shutdown, however, I have seen so many problems at shutdown I decided against it. Also did not want to delay shutdown processing.

I use backup at startup instead with a 300 second delay to get past other startup processing, in particular, any podcast scans.

[MusicBringer]

@MusicBringer - yes, I added this in version 5.4, released 10 days ago.

Thank You Very Much

[MusicBringer]

I use backup at startup instead with a ...delay to get past other startup processing, in particular, any podcast scans.

Yeah me too. Shut off happens when I go to bed so I want no delays.

[Mizery_Made]

@ Trix - Fair enough. Hadn't really thought about background processes making changes and such. Like I mentioned, probably a case of "a scenario where this might be somewhat useful isn't often enough/beneficial enough to bother with it." Which is fine, not like it makes the script unusable or anything. Carry on.

However, I just ran across a strange occurrence (or just further proof that my memory is horrible). Last night when I closed out Monkey and the backup was performed, I don't recall any errors and pretty sure everything said "successfully" or whatnot on the Backup confirmation after shutdown. However, I close the Monkey tonight, and get an error about the process being canceled due to the Output folder already existing. I've gotten this error before after receiving the previously reported error (and forgetting to manually clean it), but I'm quite sure there shouldn't be a reason for it this time. *Scratches Head* Strangely enough, alphabetically, the Plugins folder is the first one listed. Though... I guess it's possible that I got the "Couldn't delete Plugins folder" error and just forgot. Still strange that it seems to always/typically hang on that folder.

@ Owyn, I might consider changing that around. Though, I figure it best to save a backup after the session ends (to preserve primarily my play history) than at the beginning as if something were to go wrong, then I would lose pretty much a day of listens. Though, I guess if there is issue (mostly mine for forgetting to clear the folder after error) on Shutdown, those plays aren't being backed up anyway. I'll have to think about that tomorrow... my eye libs feel like they weigh more than one of my legs right about now. Ha.

[MusicBringer]

The script will now start to delete the output path as well as the archives, but no output paths created with 5.3 will be deleted because they are not stored in the database to delete. Are you saying you'd prefer there to be two separate options, one to control deletion of output paths and one to control the deletion of archives?

Yes this is what I would prefer, that way I can keep deleting the archives while not deleting any output path backup files.

Am I misunderstanding things here
The script can create backup to Output path and/or Output archive.
The path is a Folder containing sub-folders such as Plugins, Scripts, and Skins.
The archive is a zip file.

I would like to see the script offer options of How many old backups to keep - for either/both path Folders and archive Zips

I have ticked the line Delete old backups - keep <number> files and folders.
Mine is set to 2 - but I fail to notice any path folders nor archive zips deleted.
I understood it was that new functionality that was being added (I am using Backup 5.4).

[trixmoto]

Version 5.5 will have separate options for the files and folders, instead of a single combined option. Only folders that were created in version 5.4 will be deleted, as the locations are stored in the database, so any folders created with previous versions will remain indefinitely.

[MusicBringer]

Thanks trixmoto, I'll await 5.5

[mrshameless]

Bear in mind I am clueless... And I have managed to create backups with Backup 5.4. Now I have upgraded to Win7 (clean install) and I do not know how to use the backup files I have to restore MM. I am using version 3.1.0.1256 and I cannot find an option for restoring. The files in my backup folder are: mediamonkey.ini - mm.db - mediamonkey.reg - restore.vbs and folders named: mediamonkey - plugins - scripts - skins. Thanks for any help.

CORRECTION: I am now using 5.4. Backup files were created with 5.2.

Thanks