![]() ![]() Especially people who can't detect when they've made a mistake or when what they've setup isn't working. But I'm afraid it would be so complex and so many people would argue about the details that a lot of people wouldn't be able to hack it.īest to have good offline backups, and handy datastores of the apps and OSs you need.Īnd let go the people that seem to make way way too many mistakes. There should be a list of things that one should never ever do. is a horrifically easy way to do the wrong thing.īUT - if you're using full paths with tar without -C. Īlso use absolute paths so there's no accidentallyĪnd if you can help it, don't do for anything! If you must rsync into a remote with root perms, do as user: $ rsync -ax. So a multiple mistakes and now have 2 servers to rebuild and an audit of my backup scripts, unless anyone knows a slick way of recovering files from system memory. which is now copied over! Well, I have regular backups. No biggie, I have everything in /etc/ under a git repo. FFFFFFFFFFFFFFFFFFFFFFFUUUUUUUUUUUUUUUUUUUUUU-, I forgot a period! By the time I realized my mistake, /etc was already copied over. ![]() To ensure I had the freshest backups of the two main volumes of ns1, I quickly ran from the backup directory: # rsync -ax ns1:/home/ home/Īnd then for the / dir: # rsync -ax ns1:/ / The latter broke hard after a system update and I eventually decided to rebuild it. I have a virtualization server with 2 "production" VMs: a file server and another (ns1) for various network services and dev'ing environments. Over a decade administering linux servers and this is by far the worst mistake I've made. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |