[BackupPC-users] Documentation error
Hi guys I've found what I believe to be a minor typo in the SSH FAQ entry. The sudoers line given by Martin Hansen: backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * Doesn't work as shown on CentOS 6; to make it work, remove the space before the asterisk so it becomes: backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender* Could we get a consensus on which works for different platforms? I'd like to see the FAQ updated if this is true for other OSes. All the best, Justin -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Documentation error
On Sun, Mar 18, 2012 at 12:00 PM, Justin Finkelstein < jus...@redwiredesign.com> wrote: > ** > Hi guys > > I've found what I believe to be a minor typo in the SSH FAQ entry. The > sudoers line given by Martin Hansen: > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * > > Doesn't work as shown on CentOS 6; to make it work, remove the space > before the asterisk so it becomes: > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender* > > Could we get a consensus on which works for different platforms? I'd like > to see the FAQ updated if this is true for other OSes. > > All the best, > > Justin > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * works without any flaws on Arch Linux (as client). but I guess the other command should work too since "*" matches " *" -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
[BackupPC-users] Encryption and long-term storage
Hi guys I've been reviewing a number of backup solutions to use for off-site backup of a number of machines in our office and I've a couple of questions regarding backuppc: 1. Is there a way to encrypt the data that's stored? 2. Is it practical to store a year's worth of data in BackupPC? i.e. one full annual backup + daily differentials? (i.e. how does this affect the time to restore a recent version of a file?) Any thoughts? Thanks, Justin -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Encryption and long-term storage
Hi, On Sunday 18 March 2012 16:44:30 Justin Finkelstein wrote: > I've been reviewing a number of backup solutions to use for off-site > backup of a number of machines in our office and I've a couple of > questions regarding backuppc: > > 1. Is there a way to encrypt the data that's stored? While we write encrypted "tapes" to kind-of-remote discs, storing the real data encrypted is probably not a good idea because of the pooling. But you can put the whole backuppc-filesystem on an encrypted disk. > 2. Is it practical to store a year's worth of data in BackupPC? i.e. > one full annual backup + daily differentials? > (i.e. how does this affect the time to restore a recent version > of a file?) Read the documentation about the number of full backups to keep. It can actually be an array where each number denotes double the interval of its previous number. So with [4, 0, 4] it means to keep 4 weekly, 0 bi-weekly and 4 almost-a-month full backups. [4, 0, 0, 4] means 4 weekly and 4 bi-monthly full backups to keep. That is when you full-interval actually is 7 days... Whether you keep full or incremental backups on disk is not important as backuppc already de-duplicates the stored files. Its only a matter of which files are transfered from the client to the server. Have fun, Arnold signature.asc Description: This is a digitally signed message part. -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
Re: [BackupPC-users] Documentation error
On Sun, Mar 18, 2012 at 04:25:48PM +0100, Till Hofmann wrote: > On Sun, Mar 18, 2012 at 12:00 PM, Justin Finkelstein < > jus...@redwiredesign.com> wrote: > > > ** > > Hi guys > > > > I've found what I believe to be a minor typo in the SSH FAQ entry. The > > sudoers line given by Martin Hansen: > > > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * > > > > Doesn't work as shown on CentOS 6; to make it work, remove the space > > before the asterisk so it becomes: > > > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender* > > > > Could we get a consensus on which works for different platforms? I'd like > > to see the FAQ updated if this is true for other OSes. > > > > All the best, > > > > Justin > > > > > backuppc ALL=NOPASSWD: /usr/bin/rsync --server --sender * > works without any flaws on Arch Linux (as client). > but I guess the other command should work too since "*" matches " *" It works on my Debian systems as well, with the space. -Rob -- This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure ___ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List:https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki:http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
