NFS or Bind mount in a container

[Dr.Dran]

Hi guys,

I've readed this thread, and that make me think a little....

My situation is this:

I have 2 vps(container) web server, both have to acces some shared data... the shared data is located in another vps(ftp) server... I've make some experiment, I'm start with share file with nfs, but I've see that the vzdump of the 2 web vps fail with this errorcode: exit code 16

I've disabled the NFS, ad the vzdump run without problem.

The question is: is possible to mont/bind a directory of the vps(ftp)? Because I will backup alla the data with the very precious vzdump.

Did someone have a solution?

Best regards

Franco

 

[dietmar]

I use vzdump and bind mounts without problems. vzdump simply skip bind-mounted directories. So how can I reproduce that error?

 

[Dr.Dran]

hi!

You can reproduce the problem with this configuration:

Enable the nfs module in the host, with "modprobe nfs"

- enable the nfs in two openvz container with:
- vzctl set 101 --features "nfsn" --save
- vzctl set 102 --features "nfsn" --save

On the server install unfs3 and export a directory, on the client install nfs.common and mount the export of the server.

That's all...

When the vzdump start with the option to make the snapshot backup, the script didnt'backup the client and give me in the log the error that I show you.

For me is particular importa make the backup with vzdump, for semplicity... I want to make backups with one or max two action

Best regards

Franco Tampieri

 

[dietmar]

What version do you use exactly?

# pveversion -v

 

[Dr.Dran]

This is the output:

███ root@ProxMox-00:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.24-9-pve
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-8
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
███ root@ProxMox-00:~#

 

[dietmar]

This is the output:

The 'proxmox-ve-2.6.24' package is missing, so you also have an old kernel. I will try to reproduce it here next week.

 

[Dr.Dran]

Thanx!

I'm waiting for your reply

Best Regards

Franco

 

[Dr.Dran]

@ dietmar

Did yuo have reproduced the problem? My trouble is to mantain the flexybility of vzdump, the nfs share is the best form to have a container for repository and the other container for clients...

Did you suggest some alternative?

Best Regards

Franco

 

[dietmar]

Did yuo have reproduced the problem?

Sorry, I am sidetracked by other issues, no time to debug that.

Did you suggest some alternative?

What is you use an external nfs server - does it show the same bug?

 

[dietmar]

or try to use veth instead of venet - does that help?