From: gregrwm <bac...@wh...> - 2013-10-13 01:01:33
|
i want a backup of my server as of now, so i start one with BackupPC_dump. before it finishes, the scheduler starts another one, which executes simultaneously. seems like trouble. |
From: Les M. <les...@gm...> - 2013-10-13 04:20:07
|
On Sat, Oct 12, 2013 at 7:37 PM, gregrwm <bac...@wh...> wrote: > i want a backup of my server as of now, so i start one with BackupPC_dump. > before it finishes, the scheduler starts another one, which executes > simultaneously. seems like trouble. > The server/scheduler doesn't know about programs you start from the command line. If you are doing a one-off manually, why not just use the web interface to start a backup? If you need to do it from cron or some other program you can use BackupPC_serverMesg to tell the server what you want it to do: http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=ServerMesg_commands -- Les Mikesell les...@gm... |
From: gregrwm <bac...@wh...> - 2013-10-13 13:42:53
|
> > i want a backup of my server as of now, so i start one with BackupPC_dump. > > before it finishes, the scheduler starts another one, which executes > > simultaneously. seems like trouble. > > The server/scheduler doesn't know about programs you start from the > command line. If you are doing a one-off manually, why not just use > the web interface to start a backup? If you need to do it from cron > or some other program you can use BackupPC_serverMesg to tell the > server what you want it to do: > > http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=ServerMesg_commands thank you les, i'll try that next time. as for BackupPC_dump, either it ought to feedback the same activity awareness as BackupPC_serverMesg, or its documentation ought to warn of the risk and advise against its use. |
From: Les M. <les...@gm...> - 2013-10-13 15:27:32
|
On Sun, Oct 13, 2013 at 8:42 AM, gregrwm <bac...@wh...> wrote: >> >> http://sourceforge.net/apps/mediawiki/backuppc/index.php?title=ServerMesg_commands > > thank you les, i'll try that next time. > > as for BackupPC_dump, either it ought to feedback the same activity > awareness as BackupPC_serverMesg, or its documentation ought to warn of the > risk and advise against its use. > Is there some reason you don't use the web interface? Most people would only use the command line to start a backup from some other program (like cron) or if the server isn't running. -- Les Mikesell les...@gm... |
From: <bac...@ko...> - 2013-10-13 18:09:29
|
gregrwm wrote at about 08:42:44 -0500 on Sunday, October 13, 2013: > as for BackupPC_dump, either it ought to feedback the same activity > awareness as BackupPC_serverMesg, or its documentation ought to warn of the > risk and advise against its use. Why? BackupPC_dump (along with several other supporting routines) were not designed to be run alone. As Les mentioned, when run manually, BackupPC is designed to be run from the web interface and if you do want to use the command line, then you use BackupPC_serverMesg. It is classic *nix philosophy for more complex routines to be built from a sequence of smaller building-block routines. It is not the responsibility of the building-block routine to remind you that it is just a building block. Since I don't believe the BackupPC documentation ever suggests running BackupPC_dump alone (at least without mentioning that it should be sent as a server message), why should it be the responsibility of the BackupPC_dump routine to warn people about things they were never advised to do in the first place... especially since there are an infinite number of such things potentially... |