Re: what leads to a "new disk" ?
Am 05.12.22 um 19:41 schrieb Jose M Calhariz:
I wasn't aware that doing this "resets history" ... I just want to have lev0
runs only on that day
It blocks incremental backups to run until a lev0 is run sucessfully.
Now I only do a "amdmin force " when I know I have lost the previous
lev 0 or incrementals are broken.
So does it reset the history of the algorithm then?
My goal is to let the algorithm do its work and write fulls and
incrementals to storage1 during the week, but "collect" fulls for the
archive runs on sunday (and write those to storage2).
See my config for that "storage2":
define storage archive {
tapepool "archive"
policy "archive"
tapetype "LTO6"
tpchanger "robot_arc"
autolabel "ARC%b"
runtapes 4
dump-selection ALL FULL
flush-threshold-dumped 100 # (or more)
flush-threshold-scheduled 100 # (or more)
taperflush 0
}
"dump-selection" should only write fulls to these tapes.
But if I don't force fulls on sunday, I assume there would be only a few
fulls scheduled by the normal algorithm and I wouldn't get fulls of ALL
DLEs (which is the goal).
I am perfectly aware that I try to work against the original scheduling
of amanda here. But I think it should be possible to achieve what I need
here.
-
I assume this might be also related to my "forcing":
NOTES:
planner: Last full dump of samba.xx.yy:smb-etc on tape ARC940
overwritten in 3 runs.
How to interpret that?
thanks all
Re: what leads to a "new disk" ?
On Mon, Dec 05, 2022 at 03:20:08PM +0100, Stefan G. Weichinger wrote: > Am 05.12.22 um 15:03 schrieb Jose M Calhariz: > > On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote: > > > > > > I have an installation where I didn't add or remove DLEs for a long time. > > > > > > But now an then amanda seems to "forget" a DLE and come up with something > > > like: > > > > > > samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot > > > incremental dump new disk] > > > > > > The DLE is NOT new. Where does that come from? > > > > > > > By chance have you made a "amadmin Config force samba.intra rootfs" > > just before that? > > correct ;-) > > I do that in my crontab: > > 30 19 * * 1-5 /usr/sbin/amdump myconfig -ostorage=storage1; /bin/mt-st -f > /dev/nst0 offl > > 30 02 * * 7 /usr/sbin/amadmin myconfig force; /usr/sbin/amdump myconfig > -ostorage=storage2 > > > I wasn't aware that doing this "resets history" ... I just want to have lev0 > runs only on that day It blocks incremental backups to run until a lev0 is run sucessfully. Now I only do a "amdmin force " when I know I have lost the previous lev 0 or incrementals are broken. > > thx > > > > > Kind regards Jose M Calhariz -- -- O melhor no casamento são as brigas. O resto e mais ou menos. -- Thornton Wilder signature.asc Description: PGP signature
Re: what leads to a "new disk" ?
Am 05.12.22 um 15:03 schrieb Jose M Calhariz: On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote: I have an installation where I didn't add or remove DLEs for a long time. But now an then amanda seems to "forget" a DLE and come up with something like: samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot incremental dump new disk] The DLE is NOT new. Where does that come from? By chance have you made a "amadmin Config force samba.intra rootfs" just before that? correct ;-) I do that in my crontab: 30 19 * * 1-5 /usr/sbin/amdump myconfig -ostorage=storage1; /bin/mt-st -f /dev/nst0 offl 30 02 * * 7 /usr/sbin/amadmin myconfig force; /usr/sbin/amdump myconfig -ostorage=storage2 I wasn't aware that doing this "resets history" ... I just want to have lev0 runs only on that day thx
Re: what leads to a "new disk" ?
On Thu, Dec 01, 2022 at 10:18:03AM +0100, Stefan G. Weichinger wrote: > > I have an installation where I didn't add or remove DLEs for a long time. > > But now an then amanda seems to "forget" a DLE and come up with something > like: > > samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot > incremental dump new disk] > > The DLE is NOT new. Where does that come from? > By chance have you made a "amadmin Config force samba.intra rootfs" just before that? Kind regards Jose M Calhariz -- -- O melhor no casamento são as brigas. O resto e mais ou menos. -- Thornton Wilder signature.asc Description: PGP signature
Re: what leads to a "new disk" ?
Am 05.12.22 um 06:47 schrieb Nathan Stratton Treadway: On Thu, Dec 01, 2022 at 10:18:03 +0100, Stefan G. Weichinger wrote: I have an installation where I didn't add or remove DLEs for a long time. But now an then amanda seems to "forget" a DLE and come up with something like: samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot incremental dump new disk] The DLE is NOT new. Where does that come from? Looks like the source file server-src/planner.c generates that message if the "last_level" data element for the DLE is negative... What does "amadmin info " report for that DLE (during the period when you are getting this message, i.e. before the next successful full dump takes place)? Well, I have to wait for that, I assume. On the weekend I forced a lev0 for all DLEs to get a full archive set onto 4 tapes. So I have something like: Dumps: lev datestmp 0 20221204 for all the DLEs right now. Let me add that this is my "multi storage" setup: I have 2 storages with separate tape sets, and different dumpcycles. ~50 tapes for the daily backups ~16 for the weekends (where I use 4 tapes per run)
Re: what leads to a "new disk" ?
On Thu, Dec 01, 2022 at 10:18:03 +0100, Stefan G. Weichinger wrote: > > I have an installation where I didn't add or remove DLEs for a long time. > > But now an then amanda seems to "forget" a DLE and come up with > something like: > > samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but > cannot incremental dump new disk] > > The DLE is NOT new. Where does that come from? Looks like the source file server-src/planner.c generates that message if the "last_level" data element for the DLE is negative... What does "amadmin info " report for that DLE (during the period when you are getting this message, i.e. before the next successful full dump takes place)? Nathan Nathan Stratton Treadway - natha...@ontko.com - 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
Re: what leads to a "new disk" ?
If you had to restore the whole disk from backup, it now looks like a new un-backed up disk. Something about the backed-up bit for each file having been altered? Or any other procedure which could alter all/most of the backup bits? Deb Baddorf On Thursday, December 1, 2022, 06:26:31 AM EST, Stefan G. Weichinger wrote: I have an installation where I didn't add or remove DLEs for a long time. But now an then amanda seems to "forget" a DLE and come up with something like: samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot incremental dump new disk] The DLE is NOT new. Where does that come from?
what leads to a "new disk" ?
I have an installation where I didn't add or remove DLEs for a long time. But now an then amanda seems to "forget" a DLE and come up with something like: samba.intra rootfs lev 0 FAILED [dumps too big, 42606931 KB, but cannot incremental dump new disk] The DLE is NOT new. Where does that come from?
