Re: To flush or not to flush, that is the question....
I get odd things orphaned occasionally too, even without failing drives. Backups that failed halfway, and then were retried successfully, I think (never really looked). I tend to see them months later, and delete them, since amanda no longer recognizes them. Deb Baddorf Fermilab On Oct 30, 2015, at 1:47 PM, Chris Nighswonger wrote: > Hi Jean-Louis, > > On Fri, Oct 30, 2015 at 1:24 PM, Jean-Louis Martineau > wrote: >> Chris, >> >> You can use the following command to list all amanda dump in holding disk: >> $ amadmin CONFIG holding list -l >> >> What's in the holding (with the 'ls' command), it looks you have a lot of >> files not recognized by amanda. > > backup@scriptor:/storage/campus$ amadmin campus holding list -l > size (kB) lv outd dump specification > > So it looks like Amanda thinks there is nothing there. However, > between your suggestion and Debra's, I took a look at my holding disk > (I should have done this already) and found quite a large collection > of (very) old dumps. After cleaning up the holding disk, the flush > notice in the amreport is gone. > > I'm not sure what all may have transpired to result in these orphaned > dumps, but it probably had to do with the failing tape library we > replaced last month. > > Thanks to you and Debra for pointing me in the right direction! > > Kind regards, > Chris
Re: To flush or not to flush, that is the question....
Hi Jean-Louis, On Fri, Oct 30, 2015 at 1:24 PM, Jean-Louis Martineau wrote: > Chris, > > You can use the following command to list all amanda dump in holding disk: > $ amadmin CONFIG holding list -l > > What's in the holding (with the 'ls' command), it looks you have a lot of > files not recognized by amanda. backup@scriptor:/storage/campus$ amadmin campus holding list -l size (kB) lv outd dump specification So it looks like Amanda thinks there is nothing there. However, between your suggestion and Debra's, I took a look at my holding disk (I should have done this already) and found quite a large collection of (very) old dumps. After cleaning up the holding disk, the flush notice in the amreport is gone. I'm not sure what all may have transpired to result in these orphaned dumps, but it probably had to do with the failing tape library we replaced last month. Thanks to you and Debra for pointing me in the right direction! Kind regards, Chris
Re: To flush or not to flush, that is the question....
Didn’t see the original. Must’ve gotten lost. There are now more settings for “flush” …. one of them requires that flush disks be listed by NAME. The other setting does not. Looking at my config file, I think “autoflush yes” requires that you name the DLEs. “autoflush all” does not. (a) try setting it to all (b) and /or in the mean while, look at your holding disk for the names of the DLE’s still sitting there, and try amflush campus nodename1 DLE1 nodename2 DLE2 nodename3 DLE3 etc Deb Baddorf Fermilab On Oct 30, 2015, at 12:14 PM, Chris Nighswonger wrote: > No takers? > > On Tue, Oct 27, 2015 at 3:48 PM, Chris Nighswonger > wrote: >> Here is one for the list: >> >> backup@scriptor:~/campus$ amreport campus >> Hostname: scriptor >> Org : Daily CAMPUS Backup >> Config : campus >> Date: October 27, 2015 >> >> These dumps were to tape campus-NGH862L4. >> There are 59843032k of dumps left in the holding disk. >> They will be flushed on the next run. >> >> >> And yet: >> >> backup@scriptor:~/campus$ amflush campus >> Could not find any Amanda directories to flush. >> >> >> Any idea what's up with all of that? And how to fix it? >> >> Kind regards, >> Chris
Re: To flush or not to flush, that is the question....
Chris, You can use the following command to list all amanda dump in holding disk: $ amadmin CONFIG holding list -l What's in the holding (with the 'ls' command), it looks you have a lot of files not recognized by amanda. Jean-Louis On 30/10/15 01:14 PM, Chris Nighswonger wrote: No takers? On Tue, Oct 27, 2015 at 3:48 PM, Chris Nighswonger wrote: Here is one for the list: backup@scriptor:~/campus$ amreport campus Hostname: scriptor Org : Daily CAMPUS Backup Config : campus Date: October 27, 2015 These dumps were to tape campus-NGH862L4. There are 59843032k of dumps left in the holding disk. They will be flushed on the next run. And yet: backup@scriptor:~/campus$ amflush campus Could not find any Amanda directories to flush. Any idea what's up with all of that? And how to fix it? Kind regards, Chris
Re: To flush or not to flush, that is the question....
No takers? On Tue, Oct 27, 2015 at 3:48 PM, Chris Nighswonger wrote: > Here is one for the list: > > backup@scriptor:~/campus$ amreport campus > Hostname: scriptor > Org : Daily CAMPUS Backup > Config : campus > Date: October 27, 2015 > > These dumps were to tape campus-NGH862L4. > There are 59843032k of dumps left in the holding disk. > They will be flushed on the next run. > > > And yet: > > backup@scriptor:~/campus$ amflush campus > Could not find any Amanda directories to flush. > > > Any idea what's up with all of that? And how to fix it? > > Kind regards, > Chris
