Search results

It works for me on all our nodes.

On one of the nodes a backup (suspend) which should take max 2 hrs is taking 4 hours now. For the last couple of days the backup of this container just won't succeed (see my previous postings) so I tried 'suspend'. All other containers are backupped with no problems. When I look at /var/tmp...

it turns out all my nodes give kernel raid errors in the messages log. The logs of the cards itself shows no errors. The only thing the servers have in common is that they are Supermicro servers with PVE. Two have 3-ware cards (9xxx series) two have Areca cards. One have SAS disks the others...

this is a different server. I dont dare to do a fsck if I haven't got a proper backup of whats on the disk.

Hi Tom, We didn't dare to move the container so we moved everything inside into a new container on our backup server. This morning a backup should have been make of this new container on the backupserver but it seems as if the raid problems travelled with it: And I have a log of 49MB...

The poblem is that the backups of this one container all have errors because of this. They have many missing files: Other containers are fine. The container itself is running fine, nothing seems wrong with it. The files it says are not there really are there. What should I do? 1. try and...

I have a serious problem on one of my nodes. The raid (3ware raid-10) gives errors on the backup of one of the containers. Yesterday I needed to reboot the node to be able to get into the container again. While rebooting linux stopped the diskcheck telling fsck could'nt continue because of...

The restart of the node was the only thing to do for me too. It was a Openvz container.

Hi, I have a node with a load of 150. One of the containers is running but unreachable. I try to restart this container but it fails: node3:/var/lib/vz/backup# vzctl enter 120 enter into CT 120 failed node3:/var/lib/vz/backup# vzctl restart 120 Restarting container Stopping container ...

On a fresh installed 1.3 the backup of a 19GB container takes about five hours. Also there are no log files after the backup :confused: I used 'Suspend' en no compress through the control panel. Any ideas? Thanks

Sorry guys, I tend to panic in such situations :rolleyes: I have a large container that makes snapshots of backups of all nodes. The idea is that I can restore a crashed server quick that way, just login and vzdump --restore xxxx But ofcourse... if you login to a container there's no vzdump...

I need to restore a container and guess what, -bash: vzdump: command not found vzrestore? -bash: vzrestore: command not found I'm going crazy here, this is the last I need in an emergency :mad: Where is it? How do I get it? (and for later, why the hell isn't it here) Using PMVE 1.3

I want to run more then one container on this server, but a very good reason would be the easy migration to new hardware.

Hi Udo, Thanks a lot, I will try that!

Sorry to get this old thread up again but I just ran into the same problem. For a backupserver I need a node with 4TB space. I run eight 1TB disks in raid-10 leaving a partition of 3786GB. PVE won't install :mad: Can I still run proxmox and effectivly use ALL space for my container? If so...

Okay thats a relief, thanks!

Okay so in snapshot mode a free spave on root about the same size of the container is enough? Thanks, Erwin

is it correct that to backup a container you need twice the space on root partition? I have a container of 130GB, so I need a root partition of at least 260GB+?

Seems to work indeed. I will test some more and let you know if this works.

On our physical servers we used to set the /tmp partition to noexec, this saved us a lot of trouble. This is not possible with OpenVZ since there is no separate partition for /tmp. I searched for a way to protect them anyway since we have a lot of problems with rogue scripts that get uploaded...