Backup Central

David Masover writes:

Christopher L. Everett wrote:
| David,
|
| The backup log still grows at the rate of 50+ bytes per second, with a
| rescheduling message every second. Fix that before doing anything else.

I'm trying to configure BackupPC to just run the nightly cleanup,
without scheduling any backups at all. I want to run the backups
manually from cron. What should I have things set to? (WakeupSchedule,
etc)

- Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am).

- Set $Conf{FullPeriod} to -1.

- Use cron to run BackupPC_serverMesg to schedule all the full and
incremental backups.

The clients will still all be scheduled at 1am, but the setting
$Conf{FullPeriod} = -1 prevents any backups.

An alternative is to just use cron to schedule the full, and allow
BackupPC to run the incrementals:

- Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am),
or several times.

- Set $Conf{FullPeriod} to a large number (longer than the
cron full period).

- Use cron to run BackupPC_serverMesg to schedule all the full
backups.

- BackupPC will run the incrementals according to the setting of
$Conf{IncrPeriod}, relative to when cron requested the full.

Craig


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Craig Barratt wrote:
| David Masover writes:
|
|
|>Christopher L. Everett wrote:
|>| David,
|>|
|>| The backup log still grows at the rate of 50+ bytes per second, with a
|>| rescheduling message every second. Fix that before doing anything else.
|>
|>I'm trying to configure BackupPC to just run the nightly cleanup,
|>without scheduling any backups at all. I want to run the backups
|>manually from cron. What should I have things set to? (WakeupSchedule,
|>etc)
|
|
| - Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am).

Just curious, what happens when $Conf{WakeupSchedule} = []? I think
that was what broke it.
|
| - Set $Conf{FullPeriod} to -1.
|
| - Use cron to run BackupPC_serverMesg to schedule all the full and
| incremental backups.

How? And I'd rather run them manually from BackupPC_dump anyway,
thanks. I want to be able to run a nightly job which I can guarentee
only happens when no backups are running, which is easiest to do if I
just have a cron script which goes through all the backups, then runs
this job.

| The clients will still all be scheduled at 1am, but the setting
| $Conf{FullPeriod} = -1 prevents any backups.

I had this, also for incrementals.
|
| An alternative is to just use cron to schedule the full, and allow
| BackupPC to run the incrementals:
|
| - Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am),
| or several times.
|
| - Set $Conf{FullPeriod} to a large number (longer than the
| cron full period).

Cron has no similar concept -- it simply runs every night at the exact
same time.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQOtto3gHNmZLgCUhAQJieg//fDn+y3SpHBXol5HXAzbs2OO13uBZv+VD
O7F3CJavBP5GTKpESy4QlQkuwaRkenbFbelowKJdK6sM8z5A5G9kNI27SwYM5rxd
eTAX6ywmF9+rUl++kKisx67w0DA82Ho+ICpqn9QAPfSX0a+H6xh+EeOWEv5ufO1R
llq34KEJzDkiZ9HFvrYJMrIIAqdGpfIx1aWLSxL3kxpdQS2Tj807A/Yeq0xHuV5x
9Z0qvbz93pbnyYYDXE9F1ZMDEJjQ8AHmu0hn/FAF9hty04Z768oHtZGTDN4MpRqx
Q4Yd1zFUo/zGlsKz9QesNTvBdi0N6k7tjSJ7Wsdu0QLO7zdjd1H4AC6b47Lcs3tH
Gx4cNA0+3H7wFdBFxn+buAmpywKvHXYczBc3CffXlThJy9J3ifdqphI3B9fA7DeF
/hSYjXXXlIBoesrMDwxrSpS5dD3acGDr5UTdJGuB9i15ybDDEXy+X2Pj0HDygH12
4Ezdn3v+TEO7Q8f0nhxB4Kb4XDOi0HVbj6MezMgPgNMCAR8q/CgGtsds12FR0UDH
OtfuJVwIffRH4OvZgwWFcVRopRxJ58aa9Y6KbOQ9fgyWTJaFJXZKzUHEY1wsV8hJ
sKZSC/mwD9r9YuVtQPrS0waB9FmDBkrtn8zvLgTJ/AfeGG8m5uheGChMXJpFkwXe
/e2RWtENNrE=
=oK8o
-----END PGP SIGNATURE-----

David Masover writes:

Craig Barratt wrote:
| David Masover writes:
|
|
|>Christopher L. Everett wrote:
|>| David,
|>|
|>| The backup log still grows at the rate of 50+ bytes per second, with a
|>| rescheduling message every second. Fix that before doing anything else.
|>
|>I'm trying to configure BackupPC to just run the nightly cleanup,
|>without scheduling any backups at all. I want to run the backups
|>manually from cron. What should I have things set to? (WakeupSchedule,
|>etc)
|
|
| - Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am).

Just curious, what happens when $Conf{WakeupSchedule} = []? I think
that was what broke it.

I'm not sure what happens when $Conf{WakeupSchedule} = [].
Things will probably break.

| - Set $Conf{FullPeriod} to -1.
|
| - Use cron to run BackupPC_serverMesg to schedule all the full and
| incremental backups.

How? And I'd rather run them manually from BackupPC_dump anyway,
thanks. I want to be able to run a nightly job which I can guarentee
only happens when no backups are running, which is easiest to do if I
just have a cron script which goes through all the backups, then runs
this job.

If you run BackupPC_dump manually then BackupPC won't know about it.
That's bad for several reasons: BackupPC might run BackupPC_nightly
while you are running BackupPC_dump, which risks various race
conditions, BackupPC also runs BackupPC_link when each backup is done,
otherwise no files will be placed in the pool. It's important that
two BackupPC_links don't run at the same time. BackupPC keeps track
of all of these things for you.

To start a backup using BackupPC_serverMesg:

/usr/local/BackupPC/bin/BackupPC_serverMesg HOST HOSTIP USER INCR

where

- HOST is the client name to backup

- HOSTIP is the IP address if DHCP, or otherwise just the host name

- USER is the user name requesting the backup

- INCR = 1 for incremental and 0 for full.

This just emulates what the CGI script does.

| The clients will still all be scheduled at 1am, but the setting
| $Conf{FullPeriod} = -1 prevents any backups.

I had this, also for incrementals.

| An alternative is to just use cron to schedule the full, and allow
| BackupPC to run the incrementals:
|
| - Set $Conf{WakeupSchedule} to a single time (eg: 1, for 1am),
| or several times.
|
| - Set $Conf{FullPeriod} to a large number (longer than the
| cron full period).

Cron has no similar concept -- it simply runs every night at the exact
same time.

Cron does more than that. You can readily runs things once per week,
so use cron to run a weekly full, and BackupPC does the incrementals.

Craig


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
BackupPC-users mailing list
BackupPC-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/