Hello,
In BackupPC V3 each time a new backup begun the DumpPreUserCmd has been called
first. I use it to
disable hibernation in client and enable it again during DumpPostUserCmd.
In BackupPC V4, if a new backup is started (#5), we begin by renaming backup #4
to #5 and
DumpPreUserCmd will be called afterwards. This can have a duration from some
seconds till some
hours.
e.g.:
XferLOG file /var/lib/backuppc/pc/heide-pc/XferLOG.1249 created 2025-05-03
12:00:02
Executing /usr/share/backuppc/bin/BackupPC_backupDuplicate -m -h heide-pc
Xfer PIDs are now 3008956
Xfer PIDs are now 3008956,3016156
BackupPC_refCountUpdate: doing fsck on heide-pc #1249 since there are no
poolCnt files
BackupPC_refCountUpdate: host heide-pc got 0 errors (took 2208 secs)
Xfer PIDs are now 3008956
BackupPC_backupDuplicate: got 0 errors and 0 file open errors
Finished BackupPC_backupDuplicate (running time: 14777 sec)
Executing DumpPreUserCmd: /usr/share/onlineBackup/bin/obs-preBackup
heide-pc.mybackup full -s WINDOWS BACKUP4U C D E -b 1
means refCountUpdate need 37min and backupDuplicate need another 4h. Maybee
only once after the
migration from V3 to V4, maybee more or less regularly - I don't know.
If the client go to sleep during this time, the backup will fail.
1. Is it possible to recognize that BackupPC starts a backup for a client to
be able to disable
hibernation on this client?
2. If not - I could provide a patch for BackupPC_dump, to shift the
code-block "# Run an optional
pre-dump command" before the code-block "# See if this client needs an
fsck". Should I provide
such a patch
in
https://github.com/backuppc/backuppc/issueshttps://github.com/backuppc/backuppc/issues
?
Br
Matthias
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/
