Re: approaches to Amanda vaulting?
On Sat, 14 Oct 2017 17:19:57 +0100 Jose M Calharizwrote: > In my case is to duplicate the locals vtapes into a remote S3 > endpoint, for purposes of reliability in case of disaster. If I have > 50 locals vtapes, I want to have the same 50 vtapes on S3, on a > amvault. I wonder if rsync wouldn't do this also. I back up amanda metadata locally. Then from time to time I rsync my vtapes and metadata to a USB drive for offsite disaster recovery. I have scripts for all this & can share. -- The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized. -- U.S. Const. Amendment IV Key fingerprint = CE5C 6645 A45A 64E4 94C0 809C FFF6 4C48 4ECD DFDB
Re: approaches to Amanda vaulting?
Hi, I am too interested in examples of vaulting. In my case is to duplicate the locals vtapes into a remote S3 endpoint, for purposes of reliability in case of disaster. If I have 50 locals vtapes, I want to have the same 50 vtapes on S3, on a amvault. Kind regards Jose M Calhariz On Wed, Oct 04, 2017 at 10:17:22AM -0400, Nathan Stratton Treadway wrote: > We are in the process of adding vaulting to our existing Amanda > environment, and I am curious to hear/see how other sites have > approached this. > > In particular, I'm curious what policies you have adopted for what gets > vaulted, and how exactly you have scripted the vaulting so that you are > sure the correct dumps always get copied the correct number of times, > etc. > > In our situation, our nightly backups are to vtapes on a large internal > drive, and our plan is to then vault to separate vtapes on external USB > drives that are rotated physically each business day. So I think we > don't want to use "vault-storage", since we want to let the nightly > dumps proceeded without concern for whether the next USB drive is > available yet. But what isn't clear is the best way to code a cron job > to run later in the day, so that it keeps track of which of the nightly > dumps have already been vaulted v.s. the ones that still need to be. > > But more generally, I'm just curious to see how various sites have > implemented vaulting. > > Thanks. > > Nathan > > > Nathan Stratton Treadway - natha...@ontko.com - Mid-Atlantic region > Ray Ontko & Co. - Software consulting services - http://www.ontko.com/ > GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239 > Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239 > > -- -- Perguntar a um escritor o que acha dos criticos e como perguntar a um poste como ele se sente a respeito dos cachorros. -- John Osborne
Re: What are the correct permissions for lib binaries for amanda 3.5
On Sat, Oct 14, 2017 at 11:36:09AM -0400, Jean-Louis Martineau wrote: > On 14/10/17 11:14 AM, Jose M Calhariz wrote: > > -rwsr-xr-- 1 root backup 10232 Oct 13 17:23 ambind > > ambind must not be readable by all > > -rwsr-x--- 1 root backup 10232 Oct 13 17:23 ambind Thank you for the quick reply. May I ask why "ambind must not be readable by all" ? > > > Jean-Louis > This message is the property of CARBONITE, INC. and may contain confidential > or privileged information. > If this message has been delivered to you by mistake, then do not copy or > deliver this message to anyone. Instead, destroy it and notify me by reply > e-mail Kind regards Jose M Calhariz -- -- Perguntar a um escritor o que acha dos criticos e como perguntar a um poste como ele se sente a respeito dos cachorros. -- John Osborne
Re: What are the correct permissions for lib binaries for amanda 3.5
On 14/10/17 11:14 AM, Jose M Calhariz wrote: > -rwsr-xr-- 1 root backup 10232 Oct 13 17:23 ambind ambind must not be readable by all -rwsr-x--- 1 root backup 10232 Oct 13 17:23 ambind Jean-Louis This message is the property of CARBONITE, INC. and may contain confidential or privileged information. If this message has been delivered to you by mistake, then do not copy or deliver this message to anyone. Instead, destroy it and notify me by reply e-mail
What are the correct permissions for lib binaries for amanda 3.5
I am trying to package amanda 3.5 for Debian. Where the user for backups is "backup" and during the packaging I have to manually set the correct permissions of the binaries, specially group owner and setuid bits. For example my VM for testing amanda have: backup@debian-at:~$ ls -alF /usr/lib/amanda/ total 892 drwxr-xr-x 4 root root4096 Oct 14 15:13 ./ drwxr-xr-x 36 root root4096 Oct 14 14:36 ../ -rwxr-xr-x 1 root root6683 Oct 13 17:23 amadmin_perl* -rwxr-xr-x 1 root root 39160 Oct 13 17:23 amandad* -rw-r--r-- 1 root root 935 Oct 13 17:23 amanda-sh-lib.sh -rwxr-xr-x 1 root root 40835 Oct 13 17:23 ambackupd* -rwsr-xr-- 1 root backup 10232 Oct 13 17:23 ambind* -rw-r--r-- 1 root root 135 Oct 13 17:23 amcat.awk -rwxr-xr-x 1 root root 11613 Oct 13 17:23 amcheck-device* -rwxr-xr-x 1 root root 10243 Oct 13 17:23 amdumpd* -rwxr-xr-x 1 root root3804 Oct 13 17:23 amidxtaped* -rwxr-xr-x 1 root root 47184 Oct 13 17:23 amindexd* -rwxr-xr-x 1 root root2448 Oct 13 17:23 amlogroll* -rwxr-xr-x 1 root root 48136 Oct 13 17:23 amndmjob* -rw-r--r-- 1 root root 20523 Oct 13 17:23 amplot.awk -rw-r--r-- 1 root root3400 Oct 13 17:23 amplot.g -rw-r--r-- 1 root root3410 Oct 13 17:23 amplot.gp -rwxr-xr-x 1 root root 26616 Oct 13 17:23 amtrmidx* -rwxr-xr-x 1 root root 14328 Oct 13 17:23 amtrmlog* drwxr-xr-x 2 root root4096 Oct 14 15:13 application/ -rwsr-xr-- 1 root backup 18424 Oct 13 17:23 calcsize* -rwxr-xr-x 1 root root2672 Oct 13 17:23 chunker* -rwxr-xr-x 1 root root 96336 Oct 13 17:23 driver* -rwxr-xr-x 1 root backup 63672 Oct 13 17:23 dumper* -rwsr-xr-- 1 root backup 10232 Oct 13 17:23 killpgrp* -rwxr-xr-x 1 root root 52232 Oct 13 17:23 ndmjob* -rwxr-xr-x 1 root root 10232 Oct 13 17:23 noop* -rwxr-xr-x 1 root root5024 Oct 13 17:23 patch-system* -rwxr-xr-x 1 root backup 67712 Oct 13 17:23 planner* -rwxr-xr-x 1 root root1556 Oct 13 17:23 restore* drwxr-xr-x 8 root root4096 Oct 14 15:13 rest-server/ -rwsr-xr-- 1 root backup 10232 Oct 13 17:23 rundump* -rwsr-xr-- 1 root backup 14328 Oct 13 17:23 runtar* -rwxr-xr-x 1 root root 43080 Oct 13 17:23 selfcheck* -rwxr-xr-x 1 root root 60840 Oct 13 17:23 sendbackup* -rwxr-xr-x 1 root root 18432 Oct 13 17:23 senddiscover* -rwxr-xr-x 1 root root 55736 Oct 13 17:23 sendsize* -rwxr-xr-x 1 root root2918 Oct 13 17:23 taper* -rwxr-xr-x 1 root root 10232 Oct 13 17:23 teecount* But I got this warning from amcheck: backup@debian-at:~$ amcheck DailySet1 '/etc/amanda/DailySet1/amanda.conf', line 71: warning: Keyword usetimestamps is deprecated. Amanda Tape Server Host Check - ERROR: program /usr/lib/amanda/ambind: wrong permission NOTE: Holding disk '/hdisk/DailySet1': 2478080 KB disk space available, using 2375680 KB '/etc/amanda/DailySet1/amanda.conf', line 71: warning: Keyword usetimestamps is deprecated. slot 2: volume 'DailySet1-02' Will write to volume 'DailySet1-02' in slot 2. NOTE: skipping tape-writable test Server check took 0.282 seconds Amanda Backup Client Hosts Check Client check: 1 host checked in 0.153 seconds. 0 problems found. (brought to you by Amanda 3.5) Is the permissions of the binaries in /usr/lib/amanda correct? Kind regards Jose M Calhariz -- -- O tempo e a imagem movel da eternidade imovel. -- Platao 428 ± 348 a.C.; filosofo grego.