Hi there.
I recently noticed issues using NFS NAS share being used as backup storage. Probably due some network issues (or nas/power failure etc) scheduled vzdump process got frozen after reaching 100%. "Lucky" for me backed up VM still worked. Anyway I had to force killing vzdump proces and temporary force unmounting NFS share aswell. During forcing those PM GUI was half-unresponsive; most of management tabs (console etc) went blank. Luckily after finishing killing vzdump/unmounting share using SSH gui went back to normal.
I actually noticed that issues with mounted storage might even affect to properly boot PM even if share's aren't mandatory to boot PM or VM's.PM that cannot access all shares during boot seem to go to 'debug' mode instead of normal boot...
Any ideas to 'tweak' share mounting to make PM a bit more "share-fail-PROOF"?
I'm usually building/maintaining servers with dedicated internal drive (or external usb-drive at least) plus mounted NFS NAS share (if available) for PM backup purposes.
I recently noticed issues using NFS NAS share being used as backup storage. Probably due some network issues (or nas/power failure etc) scheduled vzdump process got frozen after reaching 100%. "Lucky" for me backed up VM still worked. Anyway I had to force killing vzdump proces and temporary force unmounting NFS share aswell. During forcing those PM GUI was half-unresponsive; most of management tabs (console etc) went blank. Luckily after finishing killing vzdump/unmounting share using SSH gui went back to normal.
I actually noticed that issues with mounted storage might even affect to properly boot PM even if share's aren't mandatory to boot PM or VM's.PM that cannot access all shares during boot seem to go to 'debug' mode instead of normal boot...
Any ideas to 'tweak' share mounting to make PM a bit more "share-fail-PROOF"?
I'm usually building/maintaining servers with dedicated internal drive (or external usb-drive at least) plus mounted NFS NAS share (if available) for PM backup purposes.