Hello BackupPC-users,
I have a scenario in my head and am soliciting feedback as to its
feasibility. Forgive me if this has been discussed before; I searched
the mailing list and wider Internet but couldn't come up with much
information. What I'd like to do is:
1. Set a schedule on the Windows cl
Robert,
That is a perfectly normal design for enterprise backup systems. Bacula, for
instance, allows the execution of arbitrary commands before and after backups
run, so you can execute scripts to send wake-on-LAN and shutdown commands.
I don't think Backuppc has this provision, but it should
Hi Tyler,
On Tue, Oct 13, 2009 at 08:28:04AM +0100, Tyler J. Wagner wrote:
> That is a perfectly normal design for enterprise backup systems. Bacula, for
> instance, allows the execution of arbitrary commands before and after backups
> run, so you can execute scripts to send wake-on-LAN and sh
On Tuesday 13 October 2009 09:43:43 Tino Schwarze wrote:
> Hi Tyler,
>
> On Tue, Oct 13, 2009 at 08:28:04AM +0100, Tyler J. Wagner wrote:
> > That is a perfectly normal design for enterprise backup systems. Bacula,
> > for instance, allows the execution of arbitrary commands before and after
> >
Hi Robert,
On Mon, Oct 12, 2009 at 09:11:24PM -0400, Robert Kosinski wrote:
> I have a scenario in my head and am soliciting feedback as to its
> feasibility. Forgive me if this has been discussed before; I searched
> the mailing list and wider Internet but couldn't come up with much
> informatio
Tyler J. Wagner wrote:
> Robert,
>
> That is a perfectly normal design for enterprise backup systems. Bacula, for
> instance, allows the execution of arbitrary commands before and after backups
> run, so you can execute scripts to send wake-on-LAN and shutdown commands.
>
> I don't think Backu
Thanks for the feedback thus far, guys. Maybe some background will
clarify my motivations. I intend to use BackupPC as a medium-duty
backup service for an entertainment media collection: a relatively
small number of infrequently modified large files contained on a small
number of clients. Though I
Wake-by-BIOS is interesting. Nice tip. I forgot the functionality even
> existed. This makes the setup simpler. So what about:
>
> 1. BIOS wakes up machine.
>
> 2. Wake machine around midnight so BackupPC_nightly can do its thing
> or just trigger manually upon bootup.
>
> 3. Now we'll reverse the
> 2)let backuppc process all backups. should automatically happen due to the
> wakeup schedule though I would shorten that period.
I was thinking every 15 min or so.
> 3)run a script to determine if backuppc is doing a backup, if so then sleep
> for your wakeup schedule + 1 minute, if not then e
Tino Schwarze wrote at about 10:43:43 +0200 on Tuesday, October 13, 2009:
> Hi Tyler,
>
> On Tue, Oct 13, 2009 at 08:28:04AM +0100, Tyler J. Wagner wrote:
>
> > That is a perfectly normal design for enterprise backup systems. Bacula,
> > for
> > instance, allows the execution of arbitra
On Tue, Oct 13, 2009 at 12:28 PM, dan wrote:
> 1)boot on bios power-on schedule
> 2)let backuppc process all backups. should automatically happen due to the
> wakeup schedule though I would shorten that period.
> 3)run a script to determine if backuppc is doing a backup, if so then sleep
> for y
On Thu, Oct 15, 2009 at 11:20:10AM -0400, Robert Kosinski wrote:
> > 1)boot on bios power-on schedule
> > 2)let backuppc process all backups. should automatically happen due to the
> > wakeup schedule though I would shorten that period.
> > 3)run a script to determine if backuppc is doing a backu
On Thu, Oct 15, 2009 at 12:15 PM, Tino Schwarze wrote:
> Maybe you could better use "status jobs" instead?
Thanks. That's definitely a superior idea. I used this logic to
determine if a job is running:
BackupPC_serverMesg status jobs|awk -F } '{print $2}'
If only trashClean is running, the abo
13 matches
Mail list logo
