Re: amflush surprize auth=ssh.
On Tue, Aug 24, 2021 at 07:06:44PM +, Debra S Baddorf wrote: Wasn’t there, at some point, a parameter in addition to the chunksize param? I’m using chunking, but yes, the whole set of chunks is always re-taped. But I’m using real tapes so that’s what I want. Wasn’t there another parameter, besides chunking onto the holding disk, which actually allowed the chunks to make it to your (virtual) tape? To say splitting was allowed on ’tape’ (as well as on holding disk)? That sounds like the parameter you need, to make your re-taping not start at the beginning of the set. I can’t find such a param in my setup files right now. Of course, I’m not using it, so maybe I didn’t add it to my files. Deb Baddorf Fermilab My bad. Terminology is "chunks" on holding disk, "parts" on tape. I was refering to the 45 parts that would be on the tape(s). Yes there is a parameter "allow-split" which defaults to "yes". The parameter is absent from my config files so it is default. There are also parameters for specifying the part size. Jon On Aug 24, 2021, at 12:10 AM, Jon LaBadie wrote: On Mon, Aug 23, 2021 at 06:30:24PM +0100, Jose M Calhariz wrote: Hi, What you describe is what I see when I do not use chunks. The last backup to the last vtape will be transfered again to vtape on next amdump or amflush. Kind regards Jose M Calhariz Yes, that is the historically desired behavior when DLE dumps could not be split across physical or virtual tapes. The last DLE dumped when the tape "ran out" must be retaped in its entirety. But with chunks, no more than the last chunk should need to be retaped. Amanda has record of which chunks were successfully taped. Jon On Sun, Aug 22, 2021 at 02:40:52PM -0400, Jon LaBadie wrote: I have one large DLE that gets broken into about 45 chunks for taping. My vtapes hold 20 of these chunks and I allow up to 3 tapes to be used nightly. Two evening back another large DLE was in the same dump so only about 30 of the 45 chunks fit on the three tapes. Today I ran amflush thinking amanda would just tape the 15 untaped chunks onto 1 vtape. But no, it is doing the entire 45 which will take 3 vtapes. In a vtape environment, is this reasonable behavior? Was there a way to flush only the untaped chunks? Jon End of included message <<< -- Jon H. LaBadie j...@labadie.us 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: amflush surprize auth=ssh.
Wasn’t there, at some point, a parameter in addition to the chunksize param? I’m using chunking, but yes, the whole set of chunks is always re-taped. But I’m using real tapes so that’s what I want. Wasn’t there another parameter, besides chunking onto the holding disk, which actually allowed the chunks to make it to your (virtual) tape? To say splitting was allowed on ’tape’ (as well as on holding disk)? That sounds like the parameter you need, to make your re-taping not start at the beginning of the set. I can’t find such a param in my setup files right now. Of course, I’m not using it, so maybe I didn’t add it to my files. Deb Baddorf Fermilab > On Aug 24, 2021, at 12:10 AM, Jon LaBadie wrote: > > On Mon, Aug 23, 2021 at 06:30:24PM +0100, Jose M Calhariz wrote: >> Hi, >> >> What you describe is what I see when I do not use chunks. The last >> backup to the last vtape will be transfered again to vtape on next >> amdump or amflush. >> >> Kind regards >> Jose M Calhariz > > Yes, that is the historically desired behavior when DLE dumps could > not be split across physical or virtual tapes. The last DLE dumped > when the tape "ran out" must be retaped in its entirety. But with > chunks, no more than the last chunk should need to be retaped. > Amanda has record of which chunks were successfully taped. > > Jon > >> >> On Sun, Aug 22, 2021 at 02:40:52PM -0400, Jon LaBadie wrote: >>> I have one large DLE that gets broken into about >>> 45 chunks for taping. My vtapes hold 20 of these >>> chunks and I allow up to 3 tapes to be used nightly. >>> >>> Two evening back another large DLE was in the same >>> dump so only about 30 of the 45 chunks fit on the >>> three tapes. >>> >>> Today I ran amflush thinking amanda would just tape >>> the 15 untaped chunks onto 1 vtape. But no, it is doing >>> the entire 45 which will take 3 vtapes. >>> >>> In a vtape environment, is this reasonable behavior? >>> >>> Was there a way to flush only the untaped chunks? >>> >>> Jon >>> >> > > End of included message <<< > > -- > Jon H. LaBadie j...@jgcomp.com > 11226 South Shore Rd. (703) 787-0688 (H) > Reston, VA 20190 (703) 935-6720 (C)
Question regarding a S3 cloud overhaul in progress....
I’m working to reduce the memory burden of the S3 device currently, as well as to (hopefully) clean up and speed up the upload streaming. Our ZMC product currently (because we don’t know what users tend to want) depends mostly on creating “cloud files” and splitting backups between them as needed, if they grow too large.(A limit exists because each of 10,000 uploaded parts to AWS requires a checksum-in-memory before it is uploaded… limiting its size by buffer memory). How many users depend on the non-multipart style of cloud storage?Show of hands? Who uses the cloud storage where Amanda creates blobs with “f1-b01234.data” to enumerate fixed size chunks in order. I’ve been working on making this mode able to upload without using full-size memory buffers every time, but it seems our ZMC product doesn’t use that mode nearly ever. Does anyone? n CH Confidentiality Notice | The information transmitted by this email is intended only for the person or entity to which it is addressed. This email may contain proprietary, business-confidential and/or privileged material. If you are not the intended recipient of this message, be aware that any use, review, re-transmission, distribution, reproduction or any action taken in reliance upon this message is strictly prohibited. If you received this in error, please contact the sender and delete the material from all computers.
RE: amsamba breaks with samba-4.14?
@Tobias: We have a new version of the amsamba app that you can try. We need to get it out to get reviewed but it's nearly all changed. We were hoping to get a community build out ... but that keeps getting delayed. It's been refined and corrected in several ways. We have seen various versions of samba behave differently. I cannot say I saw this below, though. -- CH > -Original Message- > From: owner-amanda-us...@amanda.org us...@amanda.org> On Behalf Of Tobias Koeck > Sent: Friday, August 20, 2021 7:54 AM > To: li...@xunil.at; amanda-users@amanda.org > Subject: Re: amsamba breaks with samba-4.14? > > WARNING: This email originated from outside of BETSOL. Do not click links or > open attachments unless you recognize the sender and know the content is safe. > > > And in the log.error logs I have errors like > > > sendbackup: info BACKUP=APPLICATION > sendbackup: info APPLICATION=amsamba > sendbackup: info RECOVER_CMD=/usr/lib/amanda/application/amsamba > restore [./file-to-restore]+ > sendbackup: info COMPRESS_SUFFIX=.gz > sendbackup: info end > ? smbclient: tarmode: unrecognised option quiet ? smbclient: > NT_STATUS_IO_TIMEOUT listing \#recycle\Vgen\db\revs\* ? smbclient: > NT_STATUS_CONNECTION_DISCONNECTED listing > \#recycle\Vgen\db\node-origins\* > ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing > \#recycle\Vgen\db\revprops\* > ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing > \#recycle\Vgen\db\locks\* > ? smbclient: NT_STATUS_CONNECTION_DISCONNECTED listing > \#recycle\Vgen\dav\activities.d\* > > That worked with earlier versions, too. > > Greetings > Tobias > On 8/20/21 3:34 PM, Tobias Koeck wrote: > > Well, > > > > it looked like the same problem but I have "estimate server" > > configured a long time ago > > > > The system is Debian 11 (stable) with the installed amanda-server and > > amanda-client packages and the samba version the distribution uses > > > > --- > > > > root@chronos:/var/log/amanda/client/a2g-3# apt-cache show smbclient > > Package: smbclient > > Source: samba > > Version: 2:4.13.5+dfsg-2 > > > > > > ---Package: amanda-client > > Source: amanda > > Version: 1:3.5.1-7 > > Installed-Size: 1088 > > Maintainer: Jose M Calhariz > > > > --- > > Thu Aug 19 14:36:44.929065295 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: pid 4992 ruid 34 euid 34 version 3.5.1: start at Thu Aug 19 > > 14:36:44 2021 > > Thu Aug 19 14:36:44.930225697 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: Arguments: backup > > Thu Aug 19 14:36:44.962332448 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: pid 4992 ruid 34 euid 34 version 3.5.1: rename at Thu Aug 19 > > 14:36:44 2021 > > Thu Aug 19 14:36:44.962380711 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: application: Amsamba > > Thu Aug 19 14:36:44.962432105 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: warning: Use of uninitialized value $regex_match in pattern > > match (m//) at /usr/lib/amanda/application/amsamba line 92. > > Thu Aug 19 14:36:44.962487075 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: Arguments: backup --message line --config a2g-3 --host > > localhost --disk //monster.someurl.de/sysadmin --device > > //monster.someurl.de/sysadmin --level 0 --index line --record > > --exclude-file ./ftp_data_hd --exclude-file ./privat --amandapass > > /etc/amandapass Thu Aug 19 14:36:44.962505169 2021: pid 4992: > > thd-0x55ad3da7ea00: > > Amsamba: command: backup > > Thu Aug 19 14:36:44.962644877 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: amandapass: /etc/amandapass > > Thu Aug 19 14:36:44.968353548 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: password_wtr 6 > > Thu Aug 19 14:36:44.968387602 2021: pid 4994: thd-0x55ad3da7ea00: > > Amsamba: password_rdr 5 > > Thu Aug 19 14:36:44.968472678 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: /bin/tar -tf - > > Thu Aug 19 14:36:44.968509209 2021: pid 4994: thd-0x55ad3da7ea00: > > Amsamba: execute: /usr/bin/smbclient /usr/bin/smbclient > > //monster.someurl.de/sysadmin -d 0 -U backup -E -c tarmode full reset > > hidden system quiet; tar cX - ./ftp_data_hd ./privat Thu Aug 19 > > 14:36:44.990733785 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: index 7 > > Thu Aug 19 14:36:45.842756883 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: stderr: tarmode: unrecognised option quiet Thu Aug 19 > > 14:36:45.842868409 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: smbclient: tarmode: unrecognised option quiet Thu Aug 19 > > 18:05:10.128160354 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: stderr: tarmode is now full, system, hidden, reset, noverbose > > Thu Aug 19 18:05:10.146256679 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: stderr: tar: dumped 7728 files and 0 directories Thu Aug 19 > > 18:05:10.146297388 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: smbclient: tar: dumped 7728 files and 0 directories Thu Aug > > 19 18:05:10.146461082 2021: pid 4992: thd-0x55ad3da7ea00: > > Amsamba: ru_utime : 265 > > Thu Aug 19 18:05:10.146478219 2021: pid
