[Users] openvz-diff-backups

mailinglist at tikklik.nl mailinglist at tikklik.nl
Wed Sep 23 17:26:43 MSK 2020


Yes that log i mailed you 

 

[2020-09-21 12:40:53] [   182]  Info2     | Mode: Virtuozzo 7
[2020-09-21 12:40:53] [   182]  Info2     | Task: backup 182 live -k 7
[2020-09-21 12:40:53] [   182]  Time      |       0.0s - Check container status ("VEID 182
exist mounted running")
[2020-09-21 12:40:53] [   182]  Time      |       0.0s - Adjust runtime configuration
[2020-09-21 12:40:53] [   182]  Info2     | Ploop layout detected - using "live_plop"
backup mode
[2020-09-21 12:40:55] [   182]  Time      |       0.0s - Execute hook "start"
[2020-09-21 12:40:55] [   182]  Time      |       0.0s - Lock container (path:
"/var/tmp/openvz-diff-backups_182.lock")
[2020-09-21 12:41:02] [   182]  Info2     | Master storage usage: 58% (path:
"/ext1/backup/182")
[2020-09-21 12:41:02] [   182]  Time      |       6.7s - Lock master storage (path:
"/ext1/backup/182/lock")
[2020-09-21 12:41:02] [   182]  Info      + <\|/> Create backup (ctid: 182 - mode:
live_plop - date: 2020-09-21_12-40-53 - keep: 2020-09-28_12-40-53)
[2020-09-21 12:41:02] [   182]  Info      + # --- Step  1/21: startup
[2020-09-21 12:41:03] [   182]  Time      |       1.1s - Update master task file (data:
"backup|running|live_plop|node1.tkservers.com|unknown|2020-09-28_12-40-53")
[2020-09-21 12:41:03] [   182]  Info      + # --- Step  2/21: check server usage
[2020-09-21 12:41:03] [   182]  Info2     | Virtuozzo 7 detected - using
"/vz/private/182/dump" as temp directory
[2020-09-21 12:41:03] [   182]  Info2     | Server memory usage:   41400 MB /   80329 MB
(52%) - free memory:   38929 MB (48%) - cache:   30233 MB (73%) - swap:     171 MB ( 1%)
[2020-09-21 12:41:03] [   182]  Info2     | OpenVZ memory usage:   18838 MB /   24576 MB
(77%) - free memory:    5738 MB (23%) - cache:   16118 MB (86%) - swap:       0 MB ( 0%)
[2020-09-21 12:41:03] [   182]  Info2     | OpenVZ disk usage:    187579 MB /  340046 MB
(55%) - free space:   152467 MB (45%)
[2020-09-21 12:41:03] [   182]  Info2     | OpenVZ disk inodes:     1240298 /   22118400 (
6%) - free inodes:   20878102 (94%)
[2020-09-21 12:41:03] [   182]  Info2     | Server tmpdir usage:  660471 MB / 1779509 MB
(37%) - free space:  1119038 MB (63%)
[2020-09-21 12:41:03] [   182]  Info2     | Server tmpfs size:     55146 MB /   55146 MB
(--%) - memory dump:    2239 MB ( 4%)
[2020-09-21 12:41:03] [   182]  Time      |       0.1s - Check server usage (ctid: 182 -
status: "VEID 182 exist mounted running")
[2020-09-21 12:41:03] [   182]  Info      + # --- Step  3/21: create server tmpfs
[2020-09-21 12:41:03] [   182]  Time      |       0.0s - Create server tmpfs (size: 55146
MB - path: "/vz/private/182/dump")
[2020-09-21 12:41:03] [   182]  Info      + # --- Step  4/21: save configuration files
[2020-09-21 12:41:03] [   182]  Info2     | Conf file: "conf_182_2020-09-21_12-40-53.conf"
[2020-09-21 12:41:04] [   182]  Time      |       1.1s - Save configuration files (path:
"/ext1/backup/182/conf/conf_182_2020-09-21_12-40-53.conf")
[2020-09-21 12:41:04] [   182]  Info      + # --- Step  5/21: suspend container
[2020-09-21 12:41:04] [   182]  Time      |       0.0s - Check container status ("VEID 182
exist mounted running")
[2020-09-21 12:41:04] [   182]  Info2     | Virtuozzo 7 detected - unable to suspend
container (operation not supported)
[2020-09-21 12:41:04] [   182]  Time      |       0.0s - Suspend container (ctid: 182)
[2020-09-21 12:41:04] [   182]  Info      + # --- Step  6/21: create ploop snapshot
(00.000043) Warn  (criu/log.c:203): The early log isn't empty
(00.019691) Warn  (compel/src/lib/infect.c:127): Unable to interrupt task: 999762
(Operation not permitted)
(00.019704) Warn  (compel/src/lib/infect.c:127): Unable to interrupt task: 999763
(Operation not permitted)

 

 

Van: users-bounces at openvz.org <users-bounces at openvz.org> Namens tranxene50
Verzonden: woensdag 23 september 2020 16:11
Aan: users at openvz.org
Onderwerp: Re: [Users] openvz-diff-backups

 

Understood.

In openvz-diff-backups.conf seek the line "CONTAINERS_FORCE_HOLD_BACKUP" and set it to :

CONTAINERS_FORCE_HOLD_BACKUP="182"

"hold" backup mode is similar to "live" mode but without extracting and saving CT memory.

However, if you have set a mail address in openvz-diff-backups.conf, you should have received reports containing error messages explaining why backups failed. 

Have a nice day!

 

Le 23/09/2020 à 08:25, mailinglist at tikklik.nl <mailto:mailinglist at tikklik.nl>  a écrit :

It is a mailserver centos 7 with a lot of mailboxes so im not happy with downtime when testing a backup.

Running postfix/ dovecot / mailman / rspamd and iscponfig as a controlpanel

So nothing special

 

I have several centos 7 servers on this node backing up without a problem.

 

It also happens randemly without me doing anything

1 - *Latest* backup - mode: live_plop - date: 2020-09-23_00-29-29 - task: backup - exit: success - keep: 2020-09-30_00-29-29 - host: 

 2 - *Sticky* backup - mode: live_plop - date: 2020-09-22_12-24-31 - task: backup - exit: success - keep: 2020-09-29_12-24-31 - host:

3 - *Sticky* backup - mode: live_plop - date: 2020-09-22_00-17-25 - task: backup - exit: success - keep: 2020-09-29_00-17-25 - host:

   | Invalid  backup - mode: live_plop - date: 2020-09-21_12-40-53 - task: backup - exit: failure - keep: until it is deleted - host:

   | Invalid  backup - mode: live_plop - date: 2020-09-21_00-20-15 - task: backup - exit: failure - keep: until it is deleted - host: 

 6 - *Sticky* backup - mode: live_plop - date: 2020-09-20_12-23-49 - task: backup - exit: success - keep: 2020-09-27_12-23-49 - host: 

 7 - *Sticky* backup - mode: live_plop - date: 2020-09-20_00-22-13 - task: backup - exit: success - keep: 2020-09-27_00-22-13 - host: 

 8 - *Sticky* backup - mode: live_plop - date: 2020-09-19_12-25-05 - task: backup - exit: success - keep: 2020-09-26_12-25-05 - host: 

   | Invalid  backup - mode: live_plop - date: 2020-09-19_00-22-45 - task: backup - exit: failure - keep: until it is deleted - host: node1.

10 - *Sticky* backup - mode: live_plop - date: 2020-09-18_12-22-38 - task: backup - exit: success - keep: 2020-09-25_12-22-38 - host: 

 

Van: users-bounces at openvz.org <mailto:users-bounces at openvz.org>   <mailto:users-bounces at openvz.org> <users-bounces at openvz.org> Namens tranxene50
Verzonden: dinsdag 22 september 2020 17:11
Aan: users at openvz.org <mailto:users at openvz.org> 
Onderwerp: Re: [Users] openvz-diff-backups

 

Hello Steffan.

Could you try "hold" backup mode ?

=> openvz-diff-backups backup 182 hold -l 9 -t

If it succeed then it seems that CRIU is unable to checkpoing the CT memory.

Last time you said that the problem was gone after restarting the container.

Could you tell us what apps are running inside?

Have a nice day! 





_______________________________________________
Users mailing list
Users at openvz.org <mailto:Users at openvz.org> 
https://lists.openvz.org/mailman/listinfo/users

-- 
tranxene50
tranxene50 at openvz-diff-backups.fr <mailto:tranxene50 at openvz-diff-backups.fr> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/users/attachments/20200923/8b6cef94/attachment-0001.html>


More information about the Users mailing list