Re: [Amanda-users] Backup incremental files
Cuttler, Brian (HEALTH) schreef op 08-06-15 om 17:18: I see what you are saying, and while the filesystem may support a method of backing up the file change, gtar isn't the tool to use for recording that delta (zfs is not amenable to DUMP, nor would that meet the request). I am told that with the right ZFS-mounts you can generate a binary stream comprising a delta. You can dump that, with ... whatever. The other way around: ZFS can read that binary stream. Gerrit
Re: [Amanda-users] Backup incremental files
Op 08-06-15 om 16:20 schreef Taz_Tasmania: 2.) I have a big file (25GB) and each day becomes the file to end a piece longer. Can Amanda backup the difference from this file and not the complete file by incremental? AFIK Amanda does things on file system level, not file level. Gerrit
Re: [Amanda-users] Backup incremental files/ Barcode band-autoloader
Op 08-06-15 om 16:20 schreef Taz_Tasmania: 1.) Can Amanada work with a barcode band-autoloader? https://forums.zmanda.com/showthread.php?2224-How-amanda-interact-with-barcodes
Re: [Amanda-users] Backup incremental files
Op 08-06-15 om 17:01 schreef Cuttler, Brian (HEALTH): Amanda manages DLE (DiskList Entries) at the file system level, the tools used to back up the file systems are all native to the OS (of the amanda client) were the file system lives. The only tools I've seen used for backup are GTAR, STAR and Dump, which is not to say that you couldn't possibly roll-you-own, but it isn't something that I've seen discussed on the list before I think the only thing that would help is using ZFS or Btrfs or anything else which knows snapshots. Gerrit
Re: Package for Opensuse 11.3 ?
Op 09-12-14 om 17:16 schreef Stefan G. Weichinger: Is there an official package for amanda on opensuse 11.3 ? I don't have access to that server yet, so I ask in advance. amanda.org only shows packages for SLES ... And the customer prefers packages over installing from source, I assume ;-) Thanks, Stefan For OpenSuSE 13.1, Amanda sits in the standard repository, and for 12.2 too, but for 11.3 (old!!!) I don't know. I checked this on my own system and on software.opensuse.org -- Kind regards, AT COMPUTING Gerrit A. Smit Sysman AT Computing Telefoon: +31 24 352 72 22 Dé one-stop-Linux-shop Telefoon cursussecretariaat: +31 24 352 72 72 Fax: +31 24 352 72 92 Kerkenbos 12-38t...@atcomputing.nl 6546 BE Nijmegen www.atcomputing.nl
Re: Understanding disklist format
Charles Stroom schreef op 16-02-14 15:29: include ./* exclude ./Canon_800IS/* exclude ./Canon_G2/* Maybe you need to exclude first? Met vriendelijke groeten, AT COMPUTING Gerrit A. Smit Beheer Technische Infrastructuur -- AT Computing Telefoon: +31 24 352 72 22 Linux/UNIXperts, Telefoon cursussecretariaat: +31 24 352 72 72 opleiders oplossers Fax: +31 24 352 72 92 Kerkenbos 12-38 t...@atcomputing.nl 6546 BE Nijmegen www.atcomputing.nl Nieuw bij AT Computing: onze Linux Reference Card nu ook als gratis app!
Re: 'labelstr' param in amanda.conf
op 09-01-14 19:47, Michael Stauffer schreef: Does this mean that if I have multiple configurations in order to break up a large 30TB data set into managable chunks, each configuration will have to have a particular set of tapes assigned to it? That seems very awkward if so. Why would you make multiple configurations for that? Gerrit
Re: Splitting a DLE with regex
Op 31-07-13 18:56, Mike Neimoyer schreef: include ./[a-c].* Maybe you should first try an existing pathname (so no wildcard), just to be sure the ./ is correct here. -- Met vriendelijke groeten, AT COMPUTING Gerrit A. Smit Beheer Technische Infrastructuur AT Computing Telefoon: +31 24 352 72 22 Dé one-stop-Linux-shop Telefoon cursussecretariaat: +31 24 352 72 72 Fax: +31 24 352 72 92 Kerkenbos 12-38t...@atcomputing.nl 6546 BE Nijmegen www.atcomputing.nl Nieuw bij AT Computing: onze Linux Reference Card nu ook als gratis app!
Re: Splitting a DLE with regex
For compile time options: $ /usr/sbin/amadmin '' version Look for the values of DUMP en RESTORE Gerrit
Re: Splitting a DLE with regex
Op 31-07-13 19:58, Gerrit A. Smit TI schreef: For compile time options: $ /usr/sbin/amadmin '' version Look for the values of DUMP en RESTORE Sorry, look for GNUTAR. I think ... Gerrit
Re: Splitting a DLE with regex
Jean-Louis Martineau schreef op 31-07-13 23:02: On 07/31/2013 04:00 PM, Mike Neimoyer wrote: However, as the amandabackup user, when I cd /home and then ls -lah I get a permission denied. This could be the reason the glob directive is failing, since it cannot scan the contents of that directory to put together an accurate include list for tar. Unfortunately, each /home/username is owned by username:username as the UID:GID. It now looks like I need to figure out a way to get the amandabackup user access via a groupID. Try the amgtar application, it should do the glob expansion as root. With Amanda, plugins are rather new for me but AFIK root-permission is only needed for reading DLE's and is done by means of calling setuid-root executables. There are two of them involved in all Amanda-work: calcsize and dumper, both called by the daemon amandad which is called by xinetd. So in this case, root-permission should not be the problem. Unless of course callcsize and dumper to NOT have a s (from setuid) in front of them or are not owned by root. $ cd /usr/lib/amanda $ ls -l -rwsr-x--- 1 root amanda 19056 28 jan 2013 calcsize -rwsr-x--- 1 root amanda 52592 28 jan 2013 dumper $ All other executables including scripts inherit root permission form these two. Surely, amgtar adds some nice features on top of GNUTAR. Met vriendelijke groeten, AT COMPUTING Gerrit A. Smit Beheer Technische Infrastructuur -- AT Computing Telefoon: +31 24 352 72 22 Linux/UNIXperts, Telefoon cursussecretariaat: +31 24 352 72 72 opleiders oplossers Fax: +31 24 352 72 92 Kerkenbos 12-38 t...@atcomputing.nl 6546 BE Nijmegen www.atcomputing.nl Nieuw bij AT Computing: onze Linux Reference Card nu ook als gratis app!
Re: amgetconf: not found
Op di 17mrt09 om 18:33 schreef Dustin J. Mitchell: 2009/3/17 Zbigniew Szalbot z.szal...@lcwords.com: I am in the dark because it is a configuration that was previously done by someone else and I have not had a lot of expierience with amanda (it ran very well). Perhaps amgetconf was accidentally removed? You may need to restore from a backup (which could be fun if other parts of Amanda have been deleted) or reinstall. IIRC I have seen an amanda client rpm package which only included the amgetconf manpage, and nothing else with that name. Gerrit
Re: Is support for multiple, simultaneous tape drives on the roadmap?
Op vr 03okt08 om 17:38 schreef Terry Burton: And as an aside, would anybody please care to comment about their experience of running a split configuration on a single backup host using a single changer library. For example, does chg-zd-mtx play nicely with multiple accessors, or are there other, non-obvious problems that make this a bad idea. I have more than one configuration using 1 tape-changer, but not simultaneously. Makes thing simpler. chg-zd-mtx does not provide locking. I took care to share (by symlinks) some of the chg-zd-mtx config files by the amanda-configurations. I use the cleaning function of chg-zd-mtx, and the drive use is accumulated for all configurations. Gerrit
Re: Changer policy
I use tpchanger chg-disk# VTAPES the tape-changer glue script # This changer script is based on a directory structure like: # slot_root_dir -| # |- info # |- data - slot1 # |- slot1 # |- slot2 # |- ... # |- slotn # where 'slot_root_dir' is the tapedev 'file:xxx' parameter and # 'n' is the tapecycle parameter. # # To use this driver, just put the line 'tpchanger chg-disk' in # your amanda.conf. Gerrit
Re: 2.6 upgrade file locations
Op ma 11aug08 om 09:26 schreef stan:
Since I install each application in /opt/{APP_NAME}, I'd prefer not to
have the 2n'r amanda levels. In the past I used dirctives like:
--sbindir=/opt/amanda/sbin
Will doing this still work? If so, what all do I need to specif? In
the past it was:
--sbindir=/opt/amanda/sbin \
--libexecdir=/opt/amanda/libexec \
--libdir=/opt/amanda/lib \
--with-configdir=/opt/amanda/etc \
--with-gnutar-listdir=/opt/amanda/var/gnutar-lists \
--mandir=/opt/amanda/man \
IMHO, just
--prefix=/opt/amanda
should do your trick. Look at the output of ./configure --help
Kind regards,
AT COMPUTING
Gerrit A. Smit
Systems Manager
--
AT Computing
Linux/UNIXperts,
opleiders oplossers Telefoon: +31 24 352 72 22
Toernooiveld 104Telefoon cursussecretariaat: +31 24 352 72 72
6525 EC Nijmegen Fax: +31 24 352 72 92
Postbus 1428[EMAIL PROTECTED]
6501 BK Nijmegen www.atcomputing.nl
If you think education is expensive, then try ignorance.
Re: Out of space problem
Op di 06mei08 om 10:28 schreef Paul Bijnens:
Or better, use amtapetape -e 35g /dev/yourtapedrive to get
an estimate (takes about 3-5 hours normally).
I got/use:
define tapetype HP-DAT72 {
comment HP-DAT72x10 Autoloader (AE313A)
# data provided by Gerrit A. Smit [EMAIL PROTECTED]
length 35480 mbytes
filemark 0 kbytes
speed 2992 kbytes
}
Re: amrecover: Extractor child exited with status 2
Op vr 02mei08 om 05:59 schreef Yogesh Hasabnis: ... I observe the following error for every tape cartridge: tar: Error exit delayed from previous errors. amrecover: Extractor child exited with status 2 extract_list - child returned non-zero status: 1 I want to know about how serious this error is and would be grateful if I get some suggestion for resolving this error. I unwillingly came across this situation a few days ago. I was disturbed by the tar message, but quickly learned that it had to I do with previous tar errors I had seen. In my case I was very happy with this behaviour of tar, because it kept on doing what it was asked to do. So: I think you should try to get hold of those 'previous errors' (i.e. read between the lines of the verbose output of tar) to see how serious they are. Gerrit
Re: Does amanda only check free holdingdiskspace at startup?
Op ma 07jan08 om 07:45 schreef Marc Muehlfeld: last saturday my monthly off-site backup started. But at the starttime, the holding disk was full of scrap. Maybe you have to be careful with scrap, especially when made by Amanda: did you run amcleanup? Gerrit
Re: amanda non interactive or automated restore/recover
Op wo 02jan08 om 21:02 schreef fedora: Every end of month I have to recover databases to burn it into DVD. The command that I used is amrecover. For amrecover I have to give an input so that amanda can recover databases (interactive). It will be wasting my time to recover one by one for the clients and I have to wait until all finished. I have to setdate, sethost, setdisk and so on. Is there any specific amanda commands that will run restore or recover when we call the function in crontab automatically (non interactive)? Just my 2 cents. hostname.diskname.datestamp.dumplevel are the filenames made by the non-interactive form of the command amrestore to extract backup images from an Amanda tape (my 3rd and 4th cent) Gerrit
amdump doesn't listen to -o option
We have a tape-robot with tapes to dump on, but sometimes I don't want to dump to tape directly: the data of some small clients, which are available during the Monday morning meeting of their users, should be hold, to be flushed to tape as side-effect of the nightly dumps of the other clients. Until now I forced this behaviour by making a symbolic link to a changer.conf with effectively 0 slots available. Not the neatest way to do it, but it worked. To make things neater, I tried to use the config overwrite option to amdump. But, saying amdump ... -o tapedev='/dev/null' of amdump ... -o tapedev='null:' doesn't do the trick: Amanda uses the tapedev from the configfile, and I end up with a near to empty tape. Why doesn't amdump do as I tell her, like status in the manpage? (I didn't look at the sources yet, I only read the manpages) Gerrit
Re: Copying data to new tapes
Op ma 12nov07 om 15:29 schreef Marc Muehlfeld: we used a Tandberg Superloader DLT Autoloader for offsite backups. Now I ordered a Tandberg Storageloader LTO3. Does anybody of you see a way to get the data of the old DTL to the new LTO3 tapes? Doing a 1-to-1 copy is wasting many space and money. My only idea is restore everything on the old tapes to a huge place and backup it to LTO agin, isn't it? But this would be to much work. You could write serveral DLT's to one LT03, using the non-rewind device (which might be neede anyhow). Gerrit
How do I tell amanda a tape is not onsite?
Hello, I'm using amanda and all is OK. But, now I want to implement level null dumps to be made say every first monday of the month (piece of cake in crontab). From the Status Update for July 2007 I learned to simply say amanda config force to get a level null dump for all hosts and disks. After such a level null dump is made, I must figure out a way to know which tapes were used, I must set those tapes to no-reuse (both inside a script), and then physically move them away to some other place (off site). Although the tapes are still in the Amanda-database, and they cannot be re-used for dumping (both are desireable), I would like a way to tell amrecover that those tapes are off site without too much fiddling around with setdate. Any ideas? Gerrit
Re: How do I tell amanda a tape is not onsite?
Gerrit A. Smit wrote: I would like a way to tell amrecover that those tapes are off site without too much fiddling around with setdate. This question remains unsolved, I think. By telling Amanda not to re-use a tape, she will refrain from using that tape for dumping, but IMHO this doen't change anything for other operations. amrecover will still use the tape for reading when needed according to the set time, and I want to be able to prevent that for tapes which are off site. Thank you for your script, but it doesn't address the bottom line of my message. Gerrit Marc Muehlfield wrote: After your amdump you still can run amstatus. There you see the tapes amanda used. This you can use for and automatic setting to no-reuse.
Re: How do I tell amanda a tape is not onsite?
Marc Muehlfeld wrote: Gerrit A. Smit wrote: By telling Amanda not to re-use a tape, she will refrain from using that tape for dumping, but IMHO this doesn't change anything for other operations. amrecover will still use the tape for reading when needed according to the set time, and I want to be able to prevent that for tapes which are off site. The user should be able to decide whether to use a tape which is off site. Why? Because it would not be helpfull for people restoring files if they are told to mount a tape (with a level 0 dump) which is e.g. a one hour drive away. Sure they won't like that. They could be better off with an older level 0 dump which is on site. If you don't want to have the full dumps seen by amrecovery why don't you create a separate set for it? Having a separate set means having a separate configuration, right? Or can I have more than one set of tapes in the same configuration? I am looking for means to have 1 set of tapes for all purposes. Which also means that the number of tapes needed for a full dump is part of the total number of tapes in a set, and so it can get bigger or smaller as needed. Users don't have to bother about a different configuration. This might seem strange, but I still want to give it a try. They only remaining point is the use of amrecover with this setup. Gerrit
