Re: exclude DLEs
> On May 2, 2016, at 2:29 PM, Stefan G. Weichinger wrote: > > Am 2016-04-20 um 09:11 schrieb Stefan G. Weichinger: > >> It depends ;-) I think it would be more elegant to not have to use >> "amadmin force". Everything covered by the amanda config, no need to >> remember two things. But that's academic discussion in a way ;-) > > additional q here: > > customer wants two DLEs in the config only dumped on friday. > > I know how to only INCLUDE DLEs with "amdump config host1 host2" or so. > But I am unsure if there is the possibility to EXCLUDE some DLEs. > > reading manpage amanda-match now. > > I think of a bigger cronjob skipping these 2 DLEs from mon-thu and > including them on friday. > > Anyone with experience? > Is it possible? > > thanks, Stefan > >From the defeaning silence, I’m guessing you may have to specify which >nodes/DLEs to backup on Mon-Thu, in your cronjob amdump configname node1 node2 node4 or amdump confignamenode1 node2 node3 DLE2 DLE3 node4 and only on Friday can you do a simple amdump configname with no nodes or DLEs after it. If anybody has a better idea, than let this serve as “BUMP” for the question. Deb Baddorf
RE: Confusion about user accounts used by amanda
Jean-Louis, > -Original Message- > From: Jean-Louis Martineau [mailto:jmartin...@carbonite.com] > > What is the user amanda is configured to run as? > $ amadmin version version > check for --with-user this reports the user "backup". > Your dumpuser should be set to the same user > All files should be owned by that user. > All amanda command must be run by that user (except amrecover which > must > be run by root). thanks a lot. I've now changed all config settings to use the "backup" user and chown'ed all existing files to the same user. "amcheck" works, "amdump" seems to work (I will have to wait some days to be sure) and local "amrecover" works as expected. cheers, aa Please consider the environment before you print / Merci de penser à l'environnement avant d'imprimer / Bitte denken Sie an die Umwelt bevor Sie drucken Bombardier Transportation GmbH /Aufsichtsratsvorsitzender / Chairman of Supervisory Board: Wolfgang Toelsner Geschäftsführung / Management Board: Dieter John (Vorsitzender/Chairman), Dr. Susanne Kortendick, Dr. Daniel Perlzweig Sitz der Gesellschaft / Principal Office: Berlin Registergericht / Registration Court: Amtsgericht Charlottenburg, HRB 64838
Confusion about user accounts used by amanda
Hi all, I'm an amanda newbie, so please bear with me. I've installed amanda server 3.3.6 from the Ubuntu repo for 16.04 (i.e. patched by the packager). I backup some local directory hierarchies as well as remote directories via SSH, currently exclusively to vtape. This implies that the amanda user account is the "backup" system account (unfortunately). I've used "amserverconfig" to create a basic configuration; backups work well, but I have difficulties regarding user permissions when using "amrecover" locally. amserverconfig has created the config with "root" as the dumpuser. I don't know whether this is related but the backup data files as well as the tapelist file are created by owner "root". Changing ownership of these files to "backup" makes amrecover work as expected. I've already tried to change dumpuser to "backup" and run "amdump" as "backup" but this doesn't work because of insufficient priviledges for reading files. Could you please enlighten me how to configure things in a way that I can run "amrecover" locally without changing file ownership? I wouldn't mind to run most things as "root" as I've confined inetd to only serve the amanda server socket on localhost, and I'm using SSH for everything else. TIA, aa Please consider the environment before you print / Merci de penser à l'environnement avant d'imprimer / Bitte denken Sie an die Umwelt bevor Sie drucken Bombardier Transportation GmbH /Aufsichtsratsvorsitzender / Chairman of Supervisory Board: Wolfgang Toelsner Geschäftsführung / Management Board: Dieter John (Vorsitzender/Chairman), Dr. Susanne Kortendick, Dr. Daniel Perlzweig Sitz der Gesellschaft / Principal Office: Berlin Registergericht / Registration Court: Amtsgericht Charlottenburg, HRB 64838
