Link to home
Start Free TrialLog in
Avatar of jlongton
jlongton

asked on

Backup of Constantly Changing Music Collection

OK, I've been thinking about this.  I don't feel like anyone understands exactly what I desire, which is completely understandable since I didn't really understand either.  

It started out that I simply wanted a backup of my server (I will just focus on the music collection since that is what is troubling me most).  I want a 1-to-1 backup (to a 500GB external USB drive) of all my mp3s (~120 and growing) in case of:

-drive failure/corruption
-file structure damage (itunes wrecked that for me once)
-I want a non-compressed backup so I can also use the external drive and have instant access to my files wherever I take the drive.  
-etc.

This is a relatively easy task. I have looked at making a batch file using xcopy or xxcopy and a program called Second Copy.  Both options seem to have the same capabilities.  However, I realized a few problems:

1.  If my file structure was damaged or if files were accidentally deleted from my collection, and I didn't realize it before the backup was scheduled, my backup would be useless because it would be missing the files and have the same problems.  I could solve this by keeping a past backup or two (instead of overwriting every time), but with a collection of this size, that is impractical.  

2.  As I organize my music collection, directory names are often changed and files and directories are moved into other directories.  This seems to cause a lot of inefficiency when backed up.  The backup process involves deleting the directories that no longer exist in the source and copying the new directories and files to the destination.  The files don't really need to be deleted and copied.  They only need to be moved.  

I guess I am looking for suggestions for a backup plan that is not going to be unreasonably huge and is not going to take a long time.  I am always changing mp3 tags, directory names, adding files, removing files, moving files, etc.  I would like it backed up weekly.  

If my intent seems misguided or unreasonable please let me know.  Thanks
Avatar of JamesTX10
JamesTX10
Flag of United States of America image

That is going to be tuff for any backup program that I have seen. You are wanting the ease of only updating files that are changed but you are changing everything that allows a program to match it up with an older backup.

Since you have a 500 gig drive and 120 gig of music to back up I would set up your backup program to make full backups and then delete the older one your drive could hold 4 backups of your current collection. I would guess you only need to keep two backups though.

Check out this free backup software that can be set to make a copy of each file rather then storing them all in one file.

http://www.educ.umu.se/~cobian/cobianbackup.htm
Avatar of callrs
callrs

http://www.lwcomputing.com/tips/static/backup.asp      Backup Recommendations
Author is leew http:M_152751.html, who you should invite to participate in this topic.
Can also post a pointer at https://www.experts-exchange.com/Storage/ ; see http:help.jsp#hi262
Avatar of jlongton

ASKER

Is there a specific procedure for posting a pointer?  How do you invite someone to participate in a topic?
You can use Symantec Ghost to help you with this.  You will be able to do a full backup to start out with and then an incrumental(sp?) backup throughtout the week.  Also, my recommendation would be to keep all of the music files in a general Music folder (named whatever you would like it to be) and backup up that folder on a weekley process.
I have software that can do incremental and much more.  my plan is to backup on a weekly basis.  I have no trouble doing that.  I am afraid that if I backup weekly by simply copying new files and deleting obsolete files (files that no longer exist in the source), I might accidentally lose/delete files from my source and then back it up, causing my backup program to delete those files from my backup drive as well.  I am beginning to realize that I am crazy for thinking that way.  That is one of the main reasons for backing up in the first place.  I really just need a backup in case my hard drive becomes corrupt.  

Now to my second concern: If I change the name of a main directory in my source drive, when it is backed up, it will have to delete that entire directory from the destination drive and copy over all the files again.  That seems inefficient and slow, but I can't see any other way around it.  if its an album or two I don't care but 50-100GB seems unreasonable.  I will probably not worry about it.  If I change a main directory I will try to go into my backup drive and change it there before my backup is scheduled, to avoid that.  

I guess I am resolving this in my head right now.  I will just use Second Copy to backup my music collection on a weekly basis, copying new files and deleting obsolete files.  But I still welcome any suggestions that might seem more logical, faster, more efficient, etc.  and if this seems like this is  not a good idea, please let me know.  thanks.

To invite, get e-mail address from member's profile (and his is right at the end of his profile). For pointer, search for "pointer" in the EE help: http:help.jsp#hi262.


This is a good topic to keep PAQ'd, even without a current resolution.
The problem is well presented & solution is really worth looking into.

jlongton, you should re-post this question at https://www.experts-exchange.com/Storage/, and a couple pointer questions in other areas...
ASKER CERTIFIED SOLUTION
Avatar of CetusMOD
CetusMOD
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial