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.
That should be the one you're after
Just make sure that the backup you're grabbing is a recent one, the backup you're listing here is from 11/11/2016 so yeah. If you want to pull all backups of that VM, do
Just keep in mind, you only need one to restore from. Just do a "ls -l /datapool/backups-compressed" and find the latest one that starts with "vzdump-qemu-100" then replace vzdump-qemu-100-2016_11_11-09_30_41.vma.lzo with whatever the latest one is.
Location: Montreal, Quebec and Dartmouth, Nova Scotia CANADA
Distribution: Arch, AntiX, ArtiX
Posts: 1,356
Rep:
My 2 cents ...
The output of the ls -l command definitely shows that even root does not have write permissions on that external hdd. Before telling you how to correct that, perhaps AB49K has comments on this ?
If not, the command to give root write permissions would be:
The output of the ls -l command definitely shows that even root does not have write permissions on that external hdd. Before telling you how to correct that, perhaps AB49K has comments on this ?
If not, the command to give root write permissions would be:
Code:
chmod -R 0775 /externalhdd
No need to chmod anything, root *always* has rw access you can't chmod rw access away from root.
I think the problem is most likely missing the trailing slash in the command I wrote out before. rsync can be funny sometimes.
Sometimes file systems like NTFS will report weird permissions because it doesn't properly support unix permissions (Don't be quoting me on that though). and I think it's a NTFS partition because it still has the default .exe's and .ini's on it.
Just keep in mind when copying to the new server you only want the latest backup, any more is kind of useless, as you will only want the latest to restore from.
Agreed, although by experience, I just prefer to have the whole set so if the latest fails or gets corrupted, I can cascade to the next one on the list. Will get back to you tomorrow.
Agreed, although by experience, I just prefer to have the whole set so if the latest fails or gets corrupted, I can cascade to the next one on the list. Will get back to you tomorrow.
That, and securing extra copies of your backups never hurt. It is always when you have one to FEW that it gets painful.
Got in this morning to find out that the files were not copied to the XHDD. Annoyed, I formatted the drive to exFAT. I launched a copy of the smallest file — SUCCESS! Screenshots are attached.
Now, I need to unmount the XHDD before doing anything else, right? So I ran "umount /dev/sd** /externalhdd/", and I get a message that neither /dev/sd** or /externalhdd/ are mounted?!?
When you umount you don't need to supply the directory. just "umount /dev/sdX"
Just a quick thing, in your command, at the end of /externalhdd/dump add a "/" at the end. "externalhdd/dump/" rsync will sometimes spit the dummy without it. Not really sure why.
That first image doesn't show any "success" -- only failures due to a read-only filesystem. I think you posted the wrong image.
The "umount" command wants one argument -- either the device or the mount point. When you give it more than one argument, it processes each in turn. In this case, it unmounted /dev/sde1, then tried to unmount /externalhdd/, which failed because it was already unmounted. Then you tried to unmount /dev/sde1 again, which failed for the same reason. It's umounted. You can disconnect the drive.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.