Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Sorry for my confusion between MB & GB (and KB and MB too).
But I stand by the "ignore read errors" is a crazy thing to do on a backup.
OK. I'll concede that one. I have written myself a memo saying, "Do not copy other peoples' commands until you understand them." If a disk clone is being created then the obvious requirement is that it should fail if an error occurs. I did not at first realize that this is the 'dd' default - but I do now. The best I can claim in my defence is that I am learning from my mistakes. I still find it paradoxical, however, that, if the conv=noerror parameter is used, it causes a fatal error in the cloning process.
Quote:
If you must clone all data, why not just copy the files, because everything (almost) is a file in Linux.
Well, maybe I'm just a lazy cloner at heart. If something goes really amiss I can simply exchange the main hard disk for a clone. If I just want a file or two I can connect the caddy, mount the clone and find the required item(s) in exactly the same place as on the main disk. If, as I earlier conceded, you measure your disk sizes in terabytes then you will probably see things differently but cloning an 80GB disk now only takes 45 minutes, yielding a 'push-button' recovery facility. Maybe I have too many memories of being confronted by the infamous BSOD (blue screen of death, as it was known) and then having to embark on a tedious differential recovery. I am also not too comfortable with that word 'almost' .
But you have to spot the problem before the next daily(?) backup.
With differential backups I can afford to be more lackadaisical.
I have three 80GB disks in caddies that I cycle, enabling me to be a bit lackadaisical, even if not so much as you.
Quote:
BTW If you have to replace your 80GB drive with another, you will not find it easy.
Well it shouldn't be difficult if it's one of the clones. I'll just replace that with another blank 80GB disk which I then introduce into the clone carrousel. If it's a bigger disk then I'll just copy my files - like you do! . Although, come to think of it, surely I will be able to clone one of my 80GB disks to a larger one? I can't imagine going back to a smaller one.
My PC has 2 x 1TB disks + 750GB NAS-attached offline storage(1) + 2TB USB-attachable offline storage(2).
Plus I run occasional backups using ssh & rsync to a netbook.
You might find products such as Spider Oak useful for storing a few bytes "in the cloud".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.