backup: strange warning in logfile

[mir]

Hi,

I was studying the logfiles for the weekly backup job and discovered the following for one of the VTs:
103: Aug 25 05:24:42 INFO: Starting Backup of VM 103 (openvz)
103: Aug 25 05:24:42 INFO: CTID 103 exist mounted running
103: Aug 25 05:24:42 INFO: status = running
103: Aug 25 05:24:42 INFO: mode failure - unable to detect lvm volume group
103: Aug 25 05:24:42 INFO: trying 'suspend' mode instead
103: Aug 25 05:24:42 INFO: backup mode: suspend

Any idea what this mean 'mode failure - unable to detect lvm volume group'?

A CT before and after did not show the above:
The one before:
102: Aug 25 05:15:25 INFO: Starting Backup of VM 102 (openvz)
102: Aug 25 05:15:25 INFO: CTID 102 exist mounted running
102: Aug 25 05:15:25 INFO: status = running
102: Aug 25 05:15:25 INFO: backup mode: snapshot
The one after:
105: Aug 25 05:27:42 INFO: Starting Backup of VM 105 (openvz)
105: Aug 25 05:27:42 INFO: CTID 105 exist mounted running
105: Aug 25 05:27:42 INFO: status = running
105: Aug 25 05:27:42 INFO: backup mode: snapshot

 

[dietmar]

What kind of storage is that CT on?

 

[mir]

What kind of storage is that CT on?

The specific CT is stored on a NFS server. The others are all on local storage.

 

[dietmar]

snapshots does not work on NFS (nfs has no such feature).

 

[mir]

Correct me if I am wrong:
1) HA needs shared storage
2) Only available shared storage for CT is NFS

How does backup of CT in HA then functioning?

 

[dietmar]

How does backup of CT in HA then functioning?

What is wrong with 'suspend' mode?

 

[mir]

What is wrong with 'suspend' mode?

For my CT in question the suspended time was 9 sec. I would hardly consider this amount of suspended time qualifying for HA.

 

[dietmar]

For my CT in question the suspended time was 9 sec. I would hardly consider this amount of suspended time qualifying for HA.

Then you have very strict HA requirements.

Note: 99,9% allows 9 hour offline per year, and most services can recover from the suspend without and service interruption. You just notice a small delay.

Anyways, you can use KVM instead, or you can use a commercial, full featured backup tool inside the VM.