2 Attachment(s)
Spent the whole week trying to get the VMs out of the server and onto the XHDD. 7 days ago, I mentioned that I formatted the drive to exFAT through Windows, and thought I was finally at it since I was able to "see" copied files on the XHDD using the "ls -l" command. When I plugged the XHDD in the new cloned server, I got an error message indicating that files (VMs) were corrupted. I then formatted the XHDD to ext3 using GParted. Started copying again the VMs from the current server to the XHDD's root, just to realize that transfers could not be completed because of lack of permissions. I then created a externalhdd/dump folder and FINALLY was able to get the latest snapshot of the VM out of there. FINALLY!
This morning, I started copying the VM from the XHDD to the cloned server using AB49K's procedure. Quote:
Quote:
|
Code:
1 LINUX CRASH COURSE |
Code:
GETTING INFO ABOUT THE SYSTEM: |
Hi Jay,
When you are running as root, you don't need to use sudo :) Just a quick thing, don't bring up the same VM on the old server and the new server while they are on the same network, you'll run into a similar problem at the VM level. |
Thanks for the info, linux4evr5581, and thanks for all your help, AB49K.
They are not on the same network. Our office server is running normally and I can access the PM interface through port 8006 on its proper IP. But the machine I am trying to clone is on my home network... Actually, I did not even plugged the Ethernet cable as you told me not to. I am stuck at the step of changing the current IP (which is the IP our office server uses) to a static IP. As I shown on the screenshot, my permission is denied even if logged using the root user credentials. What should I do? |
1 Attachment(s)
Thought I would edit the file using a Ubuntu live CD. No luck. See screenshot.
|
Quote:
Quote:
Boot into proxmox with the ethernet cable unplugged, then type "nano /etc/network interfaces" Make the changes to the ip and press "ctrl+x" It'll ask you to save, hit yes, then reboot. |
I'm pretty sure you cant change it cause in the screenshot it says "read only", and to be able to modify any type of file it should have "write" permissions assigned to it... Type ls -l to view a file's permissions (r=read, w=write, x=execute), and to change the permission type chmod u+w nameofile which will give the file's user write permission so you can modify the file. There's also permissions for groups and others, but to just to give you the user of the file (aka owner) write permissions u+w will suffice. Otherwise to give groups or other people write permission it be g+w, or o+w respectively... To take away write permission it be u-w OR to give full permissions it be u+rwx, etc... However, first in the terminal you must navigate to the directory where the file is contained in order to issue any type of command on it.
|
[QUOTE=linux4evr5581;5696903]I'm pretty sure you cant change it cause in the screenshot it says "read only"/QUOTE]
He was trying to modify the network in the live CD - not proxmox. if you boot into proxmox, log in as root you can change it. |
I like coming here to unwind after a long day. This is so exciting. I'm dying to see if he get this to work.
Proxmox was one of my favourite toys a few years ago. I loved spinning up VMs to try out things. Never realised it could be such a problem to backup. Damn, I'm getting old. I'd forgotten how confusing this must seem to people who don't leave, breathe and eat computers. It must all sound like the craziest shit. I mean, 'mount' works but 'unmount' doesn't. Isn't that just batshit crazy? I mean, wouldn't that be the first thing a normal person would fix? Why have we put up with that all these years? Why isn't the backup command called 'backup'? Why is it called 'rsync'? What non-marketing genius came up with that command? Sigh. And yet, this is how computers work. We must all be brain-dead. The aliens are gonna land, take one look at our operating systems, and say, "Shit dat! We're outta here!" and take off again. They ain't gonna want to interface to our systems. Just so you know, Proxmox is a German product. It is REALLY good stuff. Rock solid stuff. Now, you do need to setup RAID sometime or you got ZFS, which I can't remember using. But the good news is, once you got this tiny little problem sorted out, you can automate all this in the future. But dang, this must be a culture shock for you. Ah man, to get dropped in the deep end coz your friend died. Yeah, that shit happens. That's way I got everything backed up to every damn machine in the network. They're all backing up each other. No doubt, when I die, somebody's gonna have to deal with it all. I probably should start writing an "In the event of my death" document now. |
Quote:
NIT: rsync is a file replication tool. Technically it is not a backup program, though you can use anything that will copy a file to back up data. Bacula is backup tool, as is ADSM, amanda backup, backup box, etc. BURP is a very special network backup tool. There are also partition and volume clone and backup tools. Rsync is more like scp or cp seriously enhanced. It can be confusing, but it is this way because of the nature of our world. In FOSS the mantra "there is more than one way to do it" rules, and among the best each is better than the rest in one or more ways. You get to pick the one that best fits your need, once you take time to figure out what that MEANS! I am currently looking for gainful employment and have disconnected from many distracting threads, but not this one. I am hanging on here just waiting for the OP to report success. (Are we addicted?) |
Quote:
I haven't gotten up to date on the latest proxmox developments, but when I was learning to use it, documentation was a bit sparse and difficult to understand. I still remember having to blow a box away because a kernel update broke everything. :) |
Glad to hear this is considered an 'interesting' thread. :)
I was able to edit the IP address without any problems after realising there was a missing "/" in the code: "nano /etc/network/interfaces" Since this is my home network, I read on the net that I should use something like 192.168.0.XX to set up the machine's identity on the network. I used 192.168.0.99, accepted the changes in nano and rebooted proxmox. Problem is the PM interface is still asking that I logged into the GUI using our current IP address (the one I just modified in /etc/network/interfaces)... I pinged the IP address I assigned to the VM and I get the message that "destination host is unreachable" I double-checked and can confirm that the IP address was successfully updated. Any ideas what could be causing that? I was thinking about it and am wondering if it would not be simpler just to start with a blank HD and reinstall proxmox from scratch. Bad/good idea? |
Quote:
If you you will need to update the ip in /etc/network/interfaces to a valid IP on your home network. Reinstalling proxmox from scratch is certainly an option, all you would need to do is recopy the backup and follow the steps to restore the VM. |
4 Attachment(s)
Hi everyone,
I am reviving this thread. I spent the last few months trying different things and troubleshooting what was not working. Had various problems with copying the files (weird error messages, lack of storage space, unable to mount the device when installing PM on a 4Tb HDD, etc.). Now, I made it so far as to extract the files from our current server and copy them on two xHDD. Yesterday, I was finally able to transfer the .vma.lzo onto a 1Tb WD HDD after reinstalling PM from scratch. Then kept on going, following the steps AB49K pointed out: Quote:
I am attaching the screenshots. Could anyone please look at them and tell me why it is not working? Thanks so much! Jay |
All times are GMT -5. The time now is 06:34 PM. |