Backup Win / Dos script

[gnappi]

Guess I'm on "thin ice" wonder what happens when I fall through?

Your drive crashes?

 

[gnappi]

I won’t get into the earlier fuss...whatever. 2,3,5TB drives would be more useful for “casual” data storage if you were implementing a real backup strategy with long-term full, incremental and differential backup schedules. To the majority of folks, they’d never go down this route, so yes, 5TB is a bit overkill. To more advanced users, 5TB isn’t excessive.

Yes the OP has a valid point that drives get bigger each year, it’s the way it is.

Ones data is whatever they want to keep. It’s nobody’s business what that data is, the size of it or what they do with it. You simply buy a drive for the capacity you need, and plan for the future.

I never said it was a "full" backup, it's for DATA. I can duplicate my Linux, and Windows drives in 5 minutes or less with a clone, or in an hour from DVD, but data I can keep on Waaayyyy less than a 256 gig drive.

At any rate, no skin off my nose who uses it.

Here's a recent user's comments:

I tried it today. I had to modify it a bit and have to run it as admin under windows 8. I ran it as a .bat file.

I am very great full to you for sharing this program! I have tried to use back-up software before but stopped using them due to the software not working properly.

I finally have a back-up copy!!! I love the simplicity of your program. You are very kind to share it with others!

I am ashamed to say I work in the tech industry and have not payed too much attention to back-ups at home. As you said these things fail when you least expect it.

Thank you again!!!

 

[AnglerRoy]

By nature, it is a full backup dude. You’re copying everything, that has changed based on your log file and skipping files that haven’t, but more or less a full backup if I recall your programming logic (i admit I did not go back and reread your post). A “full” backup doesn’t have to equate to backing up everything, it just means backing up everything you have specified as a source. I won’t dwell on the fundamentals of back-up terms any longer as the majority of the target audience most likely won’t understand.

In actuality, I guess your script could be considered an overwriting incremental backup if you want to get technical.

I think it’s great you shared it, but if “good” data gets corrupted and therefor modified, one would be trashing their good backup with bad data (because it’s been modified). Especially if the target drive is permanently connected like most folks probably would do, case in point, a crypto virus.

Hence, my mentioning of skipping the use of your application and using a real backup strategy if someone really wants to protect their info. But, as you are probably aware, even a backup drive with a complete backup schedule, permanently connected, would get corrupted by a crypto virus as well.

I’m not trying to trash your efforts, I just don’t really agree of leading people on that they’re fully protected by using your code. Yes, it’s a duplication and that never hurts, but once you overwrite that good data, there’s no going back...at least, with a simple script like the one you provided.

 

[gnappi]

By nature, it is a full backup dude.

I’m not trying to trash your efforts, I just don’t really agree of leading people on that they’re fully protected by using your code. Yes, it’s a duplication and that never hurts, but once you overwrite that good data, there’s no going back...at least, with a simple script like the one you provided.

If you bothered to read my original post, which it appears you did not...

"If anyone on this board feels they have an inadequate (or worse still non existent) backup plan, AND has some familiarity with DOS level scripting PM me and I will either email the file or attach it to a reply here, the text file is rather small."

I continued to say their DATA is backed up, THEY change it, how many iterations should THEY keep before backing up? YMMV, Rant on you seem to relish it."

 

[LDUBS]

I wasn't defensive I was pushing back on comments that were made that were inappropriate for the casual user like yourself, and even advanced users like me. I never said anyone was a porn collector, I suggested that porn and movies are reasons for huge drives.

Yeah, I think I used a poor choice of words.

 

[earl60446]

Thanks for the script Gary

 

[gnappi]

" there’s no going back...at least, with a simple script like the one you provided."

I rarely attack people but you make it tempting

My script is over 600 lines, no mean feat for a non compiled piece that has no compiler / build / make machine to catch errors and help debug.

What you and others with an agenda fail to see in my case is that I have people who have absolutely NO BACKUP plan at all for their kids pics, wedding movies, all stuff that will likely never change. Add stuff to as new fish are caught? Yes. Go back? To what? Tell me one single thing that having EVERYTHING a person accumulates on a machine over years, maybe even through two or more machine crashes is needing to "go back" to? An old unchanged file? An over written file? Handling stepping versions is no responsibility of backup software never was, never will be, that's the owner's responsibility.

Here's a note from a fellow who lost most EVERYTHING, because he had no backup plan... THEN had the temerity to blame the techs for not being able to restore what he lost after the crash.

Now the bad part ....most of you know my computer crashed ...finally got it back a few days ago ....they did a lousy job ....I lost lots of files , pictures ...name it ....

I bet he wished he had a "simple" backup plan in use well before the crash.