I agree with Alan’s comment. You shouldn’t need - - notaper. (But you CAN use it if you want - see below). Some comments below. Deb Baddorf
> On Dec 1, 2015, at 3:18 PM, Chris Lewis <[email protected]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > Running Amanda 3.3.3 on Ubuntu 14.04, with a simple LT04 tape drive. > > I've found myself elected as the "tape backup-er" for three different > (and not network connected machines). The tape drive is on one of the > three (on my machine). > > I've made up an amanda profile for each of the three. > > Backups are done by replicating the desired data to a large portable > raid array (10Tb), the raid is brought over to my place, I mount it, > and back it up. Each of the machines has its own 'profile', and own > set of tapes and label convention. Works fine. > > I just got a 4Tb single drive brought over to be dumped under one of > the profiles. I've mounted it as a new disklist entry under the > corresponding profile. > > If I try to dump directly, the drive can't keep up and the tape > shoe-shines. So, I try to do a "amdump --no-taper <profile>" so the > 4Tb drive gets dumped onto my holding area (which is 50% larger than > the contents of the drive), to flush it later from the faster holding > area. This runs for a while and estimates the amount to dump (much > less than the holding area), and then it fails and bleats: > > localhost /fisher2 lev 0 FAILED [Skipping: new disk can't be dumped > in degraded mode] So then, why is it trying to use “degraded mode”, if the holding disk is big enough to fit all of the data? Check this parameter: reserve 02 # percent # This means save only 2% of the holding disk space for degraded # mode backups. I think the default may be 30%. Or at least, the value mine was initially set for was 30%. If your new disk takes up more than 70% of the holding disk, there would not be 30% left, and THAT could be why it is complaining. But you don’t care, so get rid of that default (or original) value, and set it to a value that YOU want. Mine is the 2% I’ve shown above. Once you get that value low enough, you certainly CAN use - - notaper to force the backup to sit on the holding disk until you are ready to back up the rest of the set. If you like. See if this fixes it. So I guess this was just one comment. Deb Baddorf > > [running amcheck against it is perfectly happy.] > > By this I interpret to mean that it simply won't use the taper for > brand new disklist entries. Right? > > Is there a way to trick it? Like, unmount the disk leaving the > directory, doing a "amdump", then remounting and doing a "amdump > - --no-taper"? Seems kind of ugly, and I can't see why you can't > "--no-taper" a brand new full dump. > > Or do I have to copy the 4Tb drive somewhere faster for this? Ugh. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQEcBAEBAgAGBQJWXg6zAAoJENy2YTBCU1mlpkoH/0eEN1AyxdRXiaUy2RcxM6eJ > 1bglg/wDZtlv/ftCl+onWKQhuOJmls68l+SUsUBqSeqK5caV2iYQdXa0NHbVj/P9 > VrQD9cNT0M/vEZNNk50IYvAlgs4qmg3NqccLyCVNpTszx6uMF411ssGre3Oqqg/P > IhsWz56SiXOqsVuW2WFeCYQ45qdz4mTG3dXGyiiowFuFM4c/3FG9iuayohSVg/w5 > 0P3DjX0tf6aDJBwcSDZQDZyN1aKRzopU9l0tBO5w7fuRzegValjshso5UCj76so9 > xKSwZcj7lroh44QAny9iFNt54CCz2aD43lLB0TkCEUiDo+qMLEmDMZk7Psedemg= > =AYF2 > -----END PGP SIGNATURE-----
