theTreeSpyder
TreeHouser
- Joined
- Feb 12, 2016
- Messages
- 691
Quotes:
"There is no part# for your data"
"Backing up means never having to say your sorry"
"Data is made of unubtanium and can only be cloned not created"
.
Backing up can be a drudgery, but also can be automated; and can really save your butt, tax records, kids pix etc.
Can backup as a disk image clonezilla.org/
or using DOS 'verbs' for file copies; really best 1 of each type, but i just use fileCopy verbs.
A backup image could be bootable/but not indiv. files, a fileCopy cannot boot/but has individual files.
If backing up a Punctured RAID array, the file image will pickup the puncture
and could put it back on another set of disks like it was a VIRUS(Vital Information Resources Under Siege).
A fileCopy will report punctured array file, but not copy it, so won't carry bad file to another set of disks!
.
Most all have heard of MS Copy and beefier xCopy.
They are CLI (Command Line Interface as opposed to GUI Graphic User Interface); single threading, no network tools etc.
Later MS added RoboCopy (robustCopy) that is MULTI-THREADING/fast, more options etc. but still CLI.
.
i've been using RichCopy almost 10yrs., it is a front end GUI for RoboCopy to my SD slot for stuff i want to backup(Desktop and Documents).
i leave card in slot, and have 1 in drawer that i swap around every so often in case of theft/fire etc.
For daily financials would network backup, tool can write to USB etc.
.
RichCopy.pdf very nicely shows how to use GUI to set backup and run,
and then also have it give command to copy to file and have Windows Task Manager run on whatever schedule
.
https://technet.microsoft.com/en-us/magazine/2009.04.utilityspotlight.aspx
"There is no part# for your data"
"Backing up means never having to say your sorry"
"Data is made of unubtanium and can only be cloned not created"
.
Backing up can be a drudgery, but also can be automated; and can really save your butt, tax records, kids pix etc.
Can backup as a disk image clonezilla.org/
or using DOS 'verbs' for file copies; really best 1 of each type, but i just use fileCopy verbs.
A backup image could be bootable/but not indiv. files, a fileCopy cannot boot/but has individual files.
If backing up a Punctured RAID array, the file image will pickup the puncture
and could put it back on another set of disks like it was a VIRUS(Vital Information Resources Under Siege).
A fileCopy will report punctured array file, but not copy it, so won't carry bad file to another set of disks!
.
Most all have heard of MS Copy and beefier xCopy.
They are CLI (Command Line Interface as opposed to GUI Graphic User Interface); single threading, no network tools etc.
Later MS added RoboCopy (robustCopy) that is MULTI-THREADING/fast, more options etc. but still CLI.
.
i've been using RichCopy almost 10yrs., it is a front end GUI for RoboCopy to my SD slot for stuff i want to backup(Desktop and Documents).
i leave card in slot, and have 1 in drawer that i swap around every so often in case of theft/fire etc.
For daily financials would network backup, tool can write to USB etc.
.
RichCopy.pdf very nicely shows how to use GUI to set backup and run,
and then also have it give command to copy to file and have Windows Task Manager run on whatever schedule
.
https://technet.microsoft.com/en-us/magazine/2009.04.utilityspotlight.aspx