i'm running BackupPC 4.4.0 on linux.
local instance config includes
$Conf{FullPeriod} = 6.97;
$Conf{IncrPeriod} = 0.97;
$Conf{WakeupSchedule} = [3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 1, 2];
BackupPC_tarCreate can restore large files.
The error you are seeing happens when the metadata file size (stored in the
directory's attrib file) doesn't match the uncompressed file size. It
appears in this case, for some reason, the attribute file in that directory
says the file size for
I just restored a backup using the web interface and that worked well. I
would still like to know if there is a command line restore option that
will work with backups that contain large files.
The files that BackupPC_tarCreate restores are ok, it just skipped large
files.
On Sat, 10 Oct 2020 at
I'm just finishing up my 1st week of automated backups.
With this local config in place
$Conf{FullPeriod} = 6.97;
$Conf{IncrPeriod} = 0.97;
$Conf{WakeupSchedule} = [3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 1,
You could also use $Conf{BlackoutPeriods) to shift the backups to the early
morning. This would also prevent the backup time eventually shifting to
daytime again if the client is sometime not available at the 3am.
Best regards,
Guillermo
On Mon, Oct 12, 2020, 13:39 PGNet Dev wrote:
> On
Here are two ways:
- manually start a backup at the preferred time, then subsequent backups
will occur after that; however, 3am doesn't make this a convenient option
- in the web interface, assuming no backup is running, select
stop/dequeue backup and enter the number of hours until a
Thanks - that is a better answer than mine!
Craig
On Mon, Oct 12, 2020 at 10:18 AM Guillermo Rozas
wrote:
> You could also use $Conf{BlackoutPeriods) to shift the backups to the
> early morning. This would also prevent the backup time eventually shifting
> to daytime again if the client is
On 10/12/20 9:34 AM, Craig Barratt wrote:
> * in the web interface, assuming no backup is running, select stop/dequeue
> backup and enter the number of hours until a bit before 3am. That will delay
> the next backup until then.
aha, perfect!
thx!
On 10/12/20 10:16 AM, Guillermo Rozas wrote:
> You could also use $Conf{BlackoutPeriods) to shift the backups to the early
> morning. This would also prevent the backup time eventually shifting to
> daytime again if the client is sometime not available at the 3am.
thx. that certainly works as
Yes, that should keep ~6 incrementals. Is there anything in the LOG files
that show when those were deleted? Was there any point where you
set $Conf{IncrKeepCnt} to less than 6?
I guess you could wait and see if it keeps #4 for the next 3 days.
Craig
On Mon, Oct 12, 2020 at 9:49 AM PGNet Dev
BackupPC_attribPrint returns for basemap.vg
'basemap.vg' => {
'compress' => 3,
'digest' => '8f1cc9a413ed1ed97f5772df02e6515f',
'gid' => 100,
'inode' => 307011,
'mode' => 436,
'mtime' => 1387843913,
'name' => 'basemap.vg',
'nlinks' => 0,
'size' => 0,
'type'
This might be because BackupPC::XS (which is used by BackupPC_attribPrint
and BackupPC_tarCreate, but not rsync_bpc) is using a 4 byte int instead of
an 8 byte long.
What's the value of ivtype and ivsize in the output of perl -V? What's the
perl version, os, and BackupPC::XS version?
Craig
On
> and, iiuc, BlackoutPeriods prevent any/all backups during their range,
> correct?
>
Yes and no. Under normal operation no backup will occur during
BlackoutPeriods. But if a client fails to backup consistently in the
allowed time periods, it will be tried also during blackouts periods. What
it
Guillermo Rozas wrote at about 21:54:13 -0300 on Monday, October 12, 2020:
> > Rather than using cron, would it make sense to define a hash keyed by
> > the host that would allow one to specify a desire time or time range
> > for backups -- sort of like the inverse of blackouts but settable by
> Rather than using cron, would it make sense to define a hash keyed by
> the host that would allow one to specify a desire time or time range
> for backups -- sort of like the inverse of blackouts but settable by
> host.
>
> Also, I would make this more of a "soft" preference in that if a
>
Craig,
There seems to be a recurring question/desire to be able to launch
backups at a specified time.
Rather than using cron, would it make sense to define a hash keyed by
the host that would allow one to specify a desire time or time range
for backups -- sort of like the inverse of blackouts
16 matches
Mail list logo
