Hi, i use proxmox and it's very useful and cool! 
i have two server (with proxmox) in a datacenter, but multicast is not supported
, for this reason i can't use a cluster...
but i configured one server such as a nfs server (directly proxmox, debian). then i add new nfs storage on second server (such as client) directly in proxmox web gui.
works ok, in fact i see "content" correctly.
on first server i add new storage ( directory) with the same path of the nfs "share", and i see the same "content".
when i tried to run a backup of one VM (kvm centos) with web gui on nfs destination, the backup has finished succesfully, but the VM crashed!
the i reboot it, centos asked me to run fcsk to repair some errors on hard disk. do it and reboot and now is all ok.
what could have happened?
depends to nfs destination? so far i have always done backup to local directory and works great.
my goal is schedule backup on other proxmox server, so that i restore more quickly on other server.
Thank you in advance
my pve version
output backup log
i have two server (with proxmox) in a datacenter, but multicast is not supported
, for this reason i can't use a cluster...but i configured one server such as a nfs server (directly proxmox, debian). then i add new nfs storage on second server (such as client) directly in proxmox web gui.
works ok, in fact i see "content" correctly.
on first server i add new storage ( directory) with the same path of the nfs "share", and i see the same "content".
when i tried to run a backup of one VM (kvm centos) with web gui on nfs destination, the backup has finished succesfully, but the VM crashed!
the i reboot it, centos asked me to run fcsk to repair some errors on hard disk. do it and reboot and now is all ok.
what could have happened?
depends to nfs destination? so far i have always done backup to local directory and works great.
my goal is schedule backup on other proxmox server, so that i restore more quickly on other server.
Thank you in advance
my pve version
Code:
proxmox-ve-2.6.32: 3.3-139 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-5 (running version: 3.3-5/bfebec03)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-34-pve: 2.6.32-140
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-1
pve-cluster: 3.0-15
qemu-server: 3.3-3
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-15
libpve-storage-perl: 3.0-25
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8 vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1output backup log
Code:
INFO: starting new backup job: vzdump 101 --remove 0 --mode snapshot --compress lzo --storage nfs-d3 --node d4
INFO: Starting Backup of VM 101 (qemu)
INFO: status = running
INFO: update VM 101: -lock backup
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating archive '/mnt/pve/nfs-d3/dump/vzdump-qemu-101-2015_03_31-12_20_10.vma.lzo'
INFO: started backup task '87c270d5-004a-4f16-8860-bc120aa1ad7b'
INFO: status: 1% (619642880/53687091200), sparse 0% (495964160), duration 3, 206/41 MB/s
.....
INFO: status: 100% (53687091200/53687091200), sparse 13% (7093821440), duration 1335, 1442/0 MB/s
INFO: transferred 53687 MB in 1335 seconds (40 MB/s)
INFO: archive file size: 25.26GB
INFO: Finished Backup of VM 101 (00:22:37)
INFO: Backup job finished successfully
TASK OK
Last edited: