Re: autoflush and amstatus

2007-05-31 Thread Marc Muehlfeld
Hi, James Brown schrieb: I have 500GB of data from a single dump to flush that barely overflows a single tape. I'd prefer not to flush and waste all that space on the second tape. What I have been doing in these cases is to fill the rest of our terabyte holdingdisk, and then flush to two

Re: autoflush and amstatus

2007-05-30 Thread James Brown
I have 500GB of data from a single dump to flush that barely overflows a single tape. I'd prefer not to flush and waste all that space on the second tape. What I have been doing in these cases is to fill the rest of our terabyte holdingdisk, and then flush to two tapes. It would be nice if the

Re: autoflush and amstatus

2007-05-30 Thread Jon LaBadie
On Wed, May 30, 2007 at 11:28:22AM -0700, James Brown wrote: I have 500GB of data from a single dump to flush that barely overflows a single tape. I'd prefer not to flush and waste all that space on the second tape. Set runtapes to 1 and do an amflush. It will only fill one tape and the

Re: autoflush and amstatus

2007-05-30 Thread Jean-Louis Martineau
I still don't understand what you want? You should be a lot more descriptive about your setup how you expect amanda to behave. How many DLE? total size? You said you ask only for full dump? how do you configured amanda? You want a full dump done at which interval? every days? week? ...

Re: autoflush and amstatus

2007-05-29 Thread Jean-Louis Martineau
Why run amdump if you don't want new dump? Why not use amflush? If the answer is: Because amdump only dump a few dle. Then you should set the reserve to a value below 100. With reserve==100, amdump record full dump only once they are put on tape, that's why it retry it. With reserve 100,

Re: autoflush and amstatus

2007-05-29 Thread James Brown
--- Jean-Louis Martineau [EMAIL PROTECTED] wrote: James Brown wrote: Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I

Re: autoflush and amstatus

2007-05-29 Thread Jon LaBadie
On Tue, May 29, 2007 at 07:36:20AM -0700, James Brown wrote: This is a problem for me. The particular configuration I am using does FULL backups only. In this case, I don't need the extra backup and I can't remove the job from the disklist since Amanda won't flush otherwise. What is the

autoflush and amstatus

2007-05-28 Thread James Brown
Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup again!). With

Re: autoflush and amstatus

2007-05-28 Thread Jean-Louis Martineau
James Brown wrote: Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I didn't want to run the 500GB backup

Re: autoflush and amstatus

2007-05-28 Thread Toomas Aas
E, 28 mai 2007 kirjutas James Brown [EMAIL PROTECTED]: After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I

Re: autoflush and amstatus

2007-05-28 Thread Bruce Thompson
On May 28, 2007, at 11:36 AM, James Brown wrote: Hi, After enabling 'autoflush' in amanda.conf, and starting new amdump, I saw two entries for a backup job that was already on holding disk. One was waiting to be flushed, the other was getting estimates. (I had to kill the job since I