Proxmox VE 3.2 Backup problem

K

Kerrigan

New Member
Jun 30, 2014
12
0
1
Hi
our customer is complaining about the following scenario:
During the backup (in the night), the VMs are not responsive and available.
Is this normal or do I have to change my configuration?

Here some infos:

Proxmox VE 3.2
No cluster, just a single node
Backup to an iSCSI volume
backup method: fast and snapshot

Thanks
 
What kind of network do you have setup? Even though backup is set to not use up all the network, if you're on an old 10/100 or something, I could see it having issues.
 
1nerdyguy said:
What kind of network do you have setup? Even though backup is set to not use up all the network, if you're on an old 10/100 or something, I could see it having issues.
Click to expand...

The connection is 1Gbit/s between the iSCSI network and my host.
And the traffic for the VMs goes through a separate cable and network.
Any other ideas?
 
try post pveperf result on that storage, and if possible vm .conf, /etc/network/interfaces, /etc/fstab, /etc/pve/storage.cfg and pveversion -v (all or some could give hint on what trouble to look for...)

Marco
 
m.ardito said:
try post pveperf result on that storage, and if possible vm .conf, /etc/network/interfaces, /etc/fstab, /etc/pve/storage.cfg and pveversion -v (all or some could give hint on what trouble to look for...)

Marco
Click to expand...
/etc/network/interfaces
Code: 
# network interface settingsauto lo
iface lo inet loopback


auto eth0
iface eth0 inet static
        address  10.50.68.20
        netmask  255.255.255.192
        gateway  10.50.68.1


iface eth1 inet manual


iface eth2 inet manual


auto eth3
iface eth3 inet static
        address  10.50.10.75
        netmask  255.255.254.0


auto bond0
iface bond0 inet manual
        slaves eth1 eth2
        bond_miimon 100
        bond_mode active-backup


auto vmbr0
iface vmbr0 inet manual
        bridge_ports bond0
        bridge_stp off
        bridge_fd 0
/etc/fstab
Code: 
root@vwerk-prod1:~# cat 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=ca9d4d30-1253-4905-8ad5-af74fcd49d0d /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/sdf1       /iSCSI_backup_volume1    ext4    rw      0       0
/dev/sdg1       /iSCSI_backup_volume2    ext4    rw      0       0

/etc/pve/storage.cfg
Code: 
lvm: lv_prep
        vgname vg_prep
        shared
        content images


dir: local
        path /var/lib/vz
        content images,iso,vztmpl,rootdir
        maxfiles 0


lvm: lv_prod
        vgname vg_prod
        shared
        content images


iscsi: backup
        target iqn.2003-10.com.lefthandnetworks:netrics-hosted-storage-mdl-2:8379:vorwerk.prod1.volume0.backup
        portal 10.50.10.62
        content none


nfs: systembackup_prep
        path /mnt/pve/systembackup_prep
        server vwerk-prod1
        export /iSCSI_backup_volume1/prep
        options vers=3
        content backup
        maxfiles 7


iscsi: backup_prod
        target iqn.2003-10.com.lefthandnetworks:netrics-hosted-storage-mdl-2:8382:vorwerk.prod1.volume1.backup
        portal 10.50.10.62
        content none


nfs: systembackup_prod
        path /mnt/pve/systembackup_prod
        server vwerk-prod1
        export /iSCSI_backup_volume2/prod
        options vers=3
        content backup
        maxfiles 7

pveversion -v
Code: 
root@vwerk-prod1:~# pveversion -v
proxmox-ve-2.6.32: 3.2-126 (running kernel: 2.6.32-29-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-29-pve: 2.6.32-126
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-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.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
 
ok, thanks, but please add also oveoerf test, since it's about system/storage performance:

like
#pveperf /mnt/pve/systembackup_prod

if /mnt/pve/systembackup_prod is the name of the storage where the problem occours.

and, if you can, also relevant lines of /etc/mtab (or #mount output) to see haw that storage is mounted, exactly.
and, if you can, try also performance chacking tools, like iperf, to be sure about real bandwidth (at backup starting-ending times)

that said, I'm not a big expert here, but I'm sure all those info will help me or others to help you.

Marco
 
m.ardito said:
ok, thanks, but please add also oveoerf test, since it's about system/storage performance:

like
#pveperf /mnt/pve/systembackup_prod

if /mnt/pve/systembackup_prod is the name of the storage where the problem occours.

and, if you can, also relevant lines of /etc/mtab (or #mount output) to see haw that storage is mounted, exactly.
and, if you can, try also performance chacking tools, like iperf, to be sure about real bandwidth (at backup starting-ending times)

that said, I'm not a big expert here, but I'm sure all those info will help me or others to help you.

Marco
Click to expand...
pveperf /mnt/pve/systembackup_prod
Code: 
CPU BOGOMIPS:      127685.12
REGEX/SECOND:      1120414
HD SIZE:           6095.59 GB (vwerk-prod1:/iSCSI_backup_volume2/prod)
FSYNCS/SECOND:     107.58
DNS EXT:           43.50 ms
DNS INT:           1.91 ms (netrics.ch)
pveperf /mnt/pve/systembackup_prep
Code: 
CPU BOGOMIPS:      127685.12
REGEX/SECOND:      876172
HD SIZE:           4031.73 GB (vwerk-prod1:/iSCSI_backup_volume1/prep)
FSYNCS/SECOND:     97.51
DNS EXT:           45.60 ms
DNS INT:           1.92 ms (netrics.ch)
mount
Code: 
/dev/sdf1 on /iSCSI_backup_volume1 type ext4 (rw,relatime,barrier=1,data=ordered)vwerk-prod1:/iSCSI_backup_volume1/prep on /mnt/pve/systembackup_prep type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.50.68.20,mountvers=3,mountport=47406,mountproto=udp,local_lock=none,addr=10.50.68.20)
/dev/sdg1 on /iSCSI_backup_volume2 type ext4 (rw,relatime,barrier=1,data=ordered)
vwerk-prod1:/iSCSI_backup_volume2/prod on /mnt/pve/systembackup_prod type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.50.68.20,mountvers=3,mountport=60239,mountproto=udp,local_lock=none,addr=10.50.68.20)
 
FSYNCS/SECOND: 107.58
Click to expand...

this is a really low value, afaik, and could be part of the source of the problem
my nfs backup (& other) share from qnap ts879 gives a value over 1800.00! (1GB/s network)

iirc, I saw a thread where pve devs suggested at least 1500.00 for the storage to work well...

Marco
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back