The client I'm trying to back up is a FreeNAS appliance, so its not LVM. I don't think the devices are changing boot to boot, but that's possible. Actually, now that I think about it, I don't think it is possible....there is only one device, and I'm sub-dividing that with a bunch of include/exclude lists.....
Here's my ls of my gnutar-lists: -rw------- 1 amanda amanda 0 May 10 08:28 amclient-tdriveCYS-2017-Masters-A-D_0.new -rw------- 1 amanda amanda 0 May 10 08:05 amclient-tdriveCYS-2017-Masters-E-M_0.new -rw------- 1 amanda amanda 0 May 10 08:07 amclient-tdriveCYS-2017-Masters-N-Q_0.new -rw------- 1 amanda amanda 0 May 11 12:06 amclient-tdriveCYS-2017-Masters-R-S_0.new -rw------- 1 amanda amanda 778788 May 9 22:46 amclient-tdriveCYS-2017-Masters-rest_0 -rw------- 1 amanda amanda 9893530 May 12 13:22 amclient-tdriveCYS-2017-Sessions-A-D_0 -rw------- 1 amanda amanda 9886842 May 31 21:57 amclient-tdriveCYS-2017-Sessions-A-D_1 -rw------- 1 amanda amanda 9893530 Jun 13 20:52 amclient-tdriveCYS-2017-Sessions-A-D_1.new -rw------- 1 amanda amanda 8867217 May 12 05:55 amclient-tdriveCYS-2017-Sessions-E-J_0 -rw------- 1 amanda amanda 8867312 May 31 22:07 amclient-tdriveCYS-2017-Sessions-E-J_1 -rw------- 1 amanda amanda 7292999 May 11 21:09 amclient-tdriveCYS-2017-Sessions-K-M_0 -rw------- 1 amanda amanda 7287876 May 31 21:58 amclient-tdriveCYS-2017-Sessions-K-M_1 -rw------- 1 amanda amanda 7292999 Jun 13 20:51 amclient-tdriveCYS-2017-Sessions-K-M_1.new -rw------- 1 amanda amanda 3883757 May 11 03:02 amclient-tdriveCYS-2017-Sessions-N-Q_0 -rw------- 1 amanda amanda 3883757 Jun 11 19:19 amclient-tdriveCYS-2017-Sessions-N-Q_1 -rw------- 1 amanda amanda 6103596 May 12 01:24 amclient-tdriveCYS-2017-Sessions-R-S_0 -rw------- 1 amanda amanda 6103596 May 31 21:51 amclient-tdriveCYS-2017-Sessions-R-S_1 -rw------- 1 amanda amanda 6103596 Jun 13 20:52 amclient-tdriveCYS-2017-Sessions-R-S_1.new -rw------- 1 amanda amanda 4692267 May 11 18:34 amclient-tdriveCYS-2017-Sessions-T-Z_0 -rw------- 1 amanda amanda 4692267 Jun 12 02:02 amclient-tdriveCYS-2017-Sessions-T-Z_1 -rw------- 1 amanda amanda 119633 May 9 15:49 amclient-tdriveCYS-2017-Sessions-rest_0 -rw------- 1 amanda amanda 119586 Jun 13 20:51 amclient-tdriveCYS-2017-Sessions-rest_1 -rw------- 1 amanda amanda 7528145 Jun 3 03:46 amclient-tdriveCYS-2018-Session-A-B_0 -rw------- 1 amanda amanda 7528145 Jun 13 20:51 amclient-tdriveCYS-2018-Session-A-B_1.new -rw------- 1 amanda amanda 15204819 May 22 14:07 amclient-tdriveCYS-2018-Session-A-D_0 -rw------- 1 amanda amanda 4490122 Jun 12 05:28 amclient-tdriveCYS-2018-Session-C_0 -rw------- 1 amanda amanda 4490122 Jun 13 21:00 amclient-tdriveCYS-2018-Session-C_1 -rw------- 1 amanda amanda 6695009 Jun 12 23:33 amclient-tdriveCYS-2018-Session-D-F_0 -rw------- 1 amanda amanda 6689636 Jun 13 20:58 amclient-tdriveCYS-2018-Session-D-F_1 -rw------- 1 amanda amanda 0 May 21 01:56 amclient-tdriveCYS-2018-Session-E-J_0.new -rw------- 1 amanda amanda 10302105 May 21 06:27 amclient-tdriveCYS-2018-Session-K-M_0 -rw------- 1 amanda amanda 174474 May 16 10:55 amclient-tdriveCYS-2018-Session-rest_0 -rw------- 1 amanda amanda 174234 Jun 13 20:52 amclient-tdriveCYS-2018-Session-rest_1 -rw------- 1 amanda amanda 3625170 Jun 2 03:20 amclient-tdriveCYS-2019-Session-A-B_0 -rw------- 1 amanda amanda 6248803 May 15 11:30 amclient-tdriveCYS-2019-Session-A-D_0 -rw------- 1 amanda amanda 7005138 May 28 18:59 amclient-tdriveCYS-2019-Session-A-D_1 -rw------- 1 amanda amanda 2076372 Jun 2 00:37 amclient-tdriveCYS-2019-Session-C_0 -rw------- 1 amanda amanda 3091423 Jun 1 22:39 amclient-tdriveCYS-2019-Session-D-F_0 -rw------- 1 amanda amanda 6217405 May 30 08:30 amclient-tdriveCYS-2019-Session-E-J_0 -rw------- 1 amanda amanda 5489291 May 15 06:34 amclient-tdriveCYS-2019-Session-E-J_1 -rw------- 1 amanda amanda 5644929 May 16 12:08 amclient-tdriveCYS-2019-Session-E-J_2 -rw------- 1 amanda amanda 3878808 Jun 2 05:26 amclient-tdriveCYS-2019-Session-G-H_0 -rw------- 1 amanda amanda 3878808 Jun 12 23:33 amclient-tdriveCYS-2019-Session-G-H_1.new -rw------- 1 amanda amanda 3418950 Jun 11 23:20 amclient-tdriveCYS-2019-Session-I-L_0 -rw------- 1 amanda amanda 3663681 May 8 05:07 amclient-tdriveCYS-2019-Session-K-M_0 -rw------- 1 amanda amanda 4062806 May 14 19:44 amclient-tdriveCYS-2019-Session-K-M_1 -rw------- 1 amanda amanda 4795279 Jun 1 10:32 amclient-tdriveCYS-2019-Session-K-M_2 -rw------- 1 amanda amanda 2792045 Jun 12 20:13 amclient-tdriveCYS-2019-Session-M_0 -rw------- 1 amanda amanda 1814850 May 7 02:52 amclient-tdriveCYS-2019-Session-N-Q_0 -rw------- 1 amanda amanda 2244093 May 14 06:02 amclient-tdriveCYS-2019-Session-N-Q_1 -rw------- 1 amanda amanda 2649037 Jun 1 03:44 amclient-tdriveCYS-2019-Session-N-Q_2 -rw------- 1 amanda amanda 2244093 Jun 12 16:05 amclient-tdriveCYS-2019-Session-N-Q_2.new -rw------- 1 amanda amanda 3725319 May 9 03:59 amclient-tdriveCYS-2019-Session-R-S_0 -rw------- 1 amanda amanda 4024064 May 14 20:21 amclient-tdriveCYS-2019-Session-R-S_1 -rw------- 1 amanda amanda 4639437 Jun 1 08:25 amclient-tdriveCYS-2019-Session-R-S_2 -rw------- 1 amanda amanda 1843488 Jun 12 16:05 amclient-tdriveCYS-2019-Session-R_0 -rw------- 1 amanda amanda 3031738 Jun 11 19:51 amclient-tdriveCYS-2019-Session-S_0 -rw------- 1 amanda amanda 3173615 May 8 01:31 amclient-tdriveCYS-2019-Session-T-Z_0 -rw------- 1 amanda amanda 3449585 May 14 15:40 amclient-tdriveCYS-2019-Session-T-Z_1 -rw------- 1 amanda amanda 3939977 Jun 1 03:03 amclient-tdriveCYS-2019-Session-T-Z_2 -rw------- 1 amanda amanda 3449585 Jun 13 22:37 amclient-tdriveCYS-2019-Session-T-Z_2.new -rw------- 1 amanda amanda 87108 May 6 12:30 amclient-tdriveCYS-2019-Session-rest_0 -rw------- 1 amanda amanda 100420 May 13 12:46 amclient-tdriveCYS-2019-Session-rest_1 -rw------- 1 amanda amanda 128994 May 31 22:14 amclient-tdriveCYS-2019-Session-rest_2 -rw------- 1 amanda amanda 3695323 May 7 02:04 amclient-tdriveCYS-General_0 -rw------- 1 amanda amanda 3767257 May 31 23:46 amclient-tdriveCYS-General_1 -rw------- 1 amanda amanda 3695323 Jun 12 20:13 amclient-tdriveCYS-General_1.new -rw------- 1 amanda amanda 9061561 May 8 04:43 amclient-tdriveCreativeImage_0 -rw------- 1 amanda amanda 9061649 May 31 22:47 amclient-tdriveCreativeImage_1 -rw------- 1 amanda amanda 9061561 Jun 13 20:51 amclient-tdriveCreativeImage_1.new I'm bothered by the .new extensions, and I don't know why they are there. But those are in fact volumes that I've been getting level 0's of even though it claims its a level 1 or 2. Note that this is a HUGE amount of data....Filling one LTO-8M tape takes 26 hrs by itself, so each amanda run takes 2-3 days. I've got a long dumpcycle accordingly. Most of these folders change very rarely, so I'm depneding on the level 0, then near zero level 1's for a month. When something like this happens, it totally breaks my backup (as I now have 40-60TB to back up onto an 8TB tape + 8TB holding disk....I've already had to amcleankup -k two runs because they got stuck due to out of holding disk + out of tape. I don't know if the holding disk contents is even worth flushing. --Jim On Sun, Jun 16, 2019 at 3:40 PM Nathan Stratton Treadway <[email protected]> wrote: > On Sat, Jun 15, 2019 at 20:35:30 +0200, Uwe Menges wrote: > > On 6/15/19 6:43 PM, Jim Kusznir wrote: > > > Ever since, any backup is run as a level 0 (even though it reports > doing > > > a level 1, 2, etc). Everything runs as 0. > > > > > > How do I fix this? > > > > I fixed a similar symptom on my system with > > property "CHECK-DEVICE" "NO" > > (using amgtar), which hands "--no-check-device" to GNU tar, > > which makes it no longer think the toplevel dir has been renamed, > > so it doesn't store all files in its incremental. > > Yes, if the device for the filesystems in question are changing from > boot to boot, then using the --no-check-device option is necessary to > allow the incrementals to work as expected across reboots. But I > believe that option is not available for the GNUTAR application, so > assuming Jim is indeed using GNUTAR then it seems worth making sure > that's actually his problem before trying to implement that particular > solution.... > > > I think what happened to me is that some LVM volumes got mounted with a > > different minor number, triggering that. > > > > Given that LVM is really common nowadays, I wonder if that option should > > be default.. I can't think of a use case where the current default is > > preferable, at the moment. > > Yes. In particular, as long as --one-file-system is passed to GNU tar > (the default situation in Amanda) then every file backed up by that run > of tar is going to be on one single device, and the check-device > operation when building the list of incremental changes is never going > to be useful. (And obviously, in the case of changed device numbers for > the filesystem, the check is actually harmful). > > I don't know about changing the actual default in the amgtar application > itself at this point in time, but perhaps it at least makes sense to > recommend disabling check-device in the example amanda.conf and other > documentation.... > > Nathan > > > ---------------------------------------------------------------------------- > Nathan Stratton Treadway - [email protected] - 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 >
