Re: forcing a degraded backup
On Mon, May 13, 2002 at 04:37:35PM +0200, Manuel Bouyer wrote: On Tue, May 07, 2002 at 07:52:10AM -0400, Jean-Louis Martineau wrote: That's BAD, you can't use the same logdir for two configurations, logfile will get erased. You will get the same problem with indexdir if you have a disk in both config. I don't understand why ... note that both configs won't run at the same day (one day for backup to tape, next day a degraded backup). When I use 'history' in amrecover I get all the backups in the list, with the proper tapes. Also the log files are all there. It works now because it's a new config, After tapecycle days, one config will erase the log and index of the other config. Ha OK. Hum, I can see a problem even with one config then: I think I should have dumpcycle=2 weeks and runspercycle=14, (one run per day) but I'll have only have half the expected tapes (as one run out of 2 will go to holding disk and will be flushed with the dump of the next run). I'm not sure how amanda will handle it. I already planned to have 14 tapes to have 2 cycles of tapes, so it should be OK. It should work if you allow full dump in degraded mode by setting the reserve parameter. It's the best solution if you have enough holding disk. If you don't allow full dump in degraded mode, then I thing that setting runspercycle=7 will give better result at balancing full dump. Jean-Louis Why not use one config and edit your amanda.conf everyday, that could be easily done by cron. I though at this, but I prefer static config files. This avoids problems in case the server goes down in the middle of a backup. I think that running a small sed script to patch a static config file template before every amdump run is easier than using two configs. OK, I'll look at this. My problem with this approach is that if the server crashes in the middle of a degraded dump, then the wrong config will be in place until the next run, and amtape won't work (for use with amrecover for example). I agree this would be very bad luck. Also it has to be changed for amcheck too. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] -- -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: forcing a degraded backup
On Tue, May 14, 2002 at 11:34:21AM -0400, Jean-Louis Martineau wrote: It should work if you allow full dump in degraded mode by setting the reserve parameter. It's the best solution if you have enough holding disk. I can't really allow full dumps in degraded mode because I have some very large filesystems (one of 60G, which hopefully will always compress enouth to fit on tape) so if there is too much full dumps to flush the tape may be too small. If you don't allow full dump in degraded mode, then I thing that setting runspercycle=7 will give better result at balancing full dump. OK, I'll let it run a few days and see how it behave. Thanks for the advices ! -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
Re: forcing a degraded backup
On Tue, May 07, 2002 at 07:52:10AM -0400, Jean-Louis Martineau wrote: That's BAD, you can't use the same logdir for two configurations, logfile will get erased. You will get the same problem with indexdir if you have a disk in both config. I don't understand why ... note that both configs won't run at the same day (one day for backup to tape, next day a degraded backup). When I use 'history' in amrecover I get all the backups in the list, with the proper tapes. Also the log files are all there. It works now because it's a new config, After tapecycle days, one config will erase the log and index of the other config. Ha OK. Hum, I can see a problem even with one config then: I think I should have dumpcycle=2 weeks and runspercycle=14, (one run per day) but I'll have only have half the expected tapes (as one run out of 2 will go to holding disk and will be flushed with the dump of the next run). I'm not sure how amanda will handle it. I already planned to have 14 tapes to have 2 cycles of tapes, so it should be OK. Why not use one config and edit your amanda.conf everyday, that could be easily done by cron. I though at this, but I prefer static config files. This avoids problems in case the server goes down in the middle of a backup. I think that running a small sed script to patch a static config file template before every amdump run is easier than using two configs. OK, I'll look at this. My problem with this approach is that if the server crashes in the middle of a degraded dump, then the wrong config will be in place until the next run, and amtape won't work (for use with amrecover for example). I agree this would be very bad luck. Also it has to be changed for amcheck too. -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
Re: forcing a degraded backup
On Mon, May 06, 2002 at 04:18:08PM -0400, Jean-Louis Martineau wrote: On Mon, May 06, 2002 at 11:32:09AM +0200, Manuel Bouyer wrote: On Fri, May 03, 2002 at 03:23:06PM +0200, Manuel Bouyer wrote: Hi, I'm looking for a way to force a backup to degraded mode, to holding disk with 2.4.3b3. Reading the docs I didn't find anything obvious yet. Here's what I'm trying to do: I have a 14 slots DLT changer. With a runspercycle of 7, I have plenty of space left on tapes, so I'd like to put 2 days of backup on a tape. I'm trying to get amanda do a degraded backup to holding disk (incrementals only), which should be quite small (less than 5G), one day out of two. The next day this backup would be flushed to tape before the scheduled backups. Of course I'd like to have all this under the same config, so that peoples running amrecover don't have to know if it was a full or degraded backup. The problem is that I don't know how to make it do a degraded dump when there is a valid tape available. Any idea ? I found a way of doing it: setup a second configuration with a dummy tape device (I used /dev/null) with holding disk, infofile, logdir and indexdir pointing to the same place as the config with tape changer. This seems to work (I tried amrecover from both tape and holding disk). That's BAD, you can't use the same logdir for two configurations, logfile will get erased. You will get the same problem with indexdir if you have a disk in both config. I don't understand why ... note that both configs won't run at the same day (one day for backup to tape, next day a degraded backup). When I use 'history' in amrecover I get all the backups in the list, with the proper tapes. Also the log files are all there. Why not use one config and edit your amanda.conf everyday, that could be easily done by cron. I though at this, but I prefer static config files. This avoids problems in case the server goes down in the middle of a backup. Don't use /dev/null, your backup can go to it, use /dev/nosuchdevice instead. Ha, good point. A minor annoyance is that both amcheck and amdump complain about the invalid tape, amd amdump report claims that something went bad when it's what I wanted. Wish to amanda hackers: would be nice if there was a config option to make amanda work without tape at all, without complains :) Wish you will become an amanda hackers :) Well, I'm already a NetBSD developer. Days only have 24 hours :) -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
Re: forcing a degraded backup
On Tue, May 07, 2002 at 10:18:44AM +0200, Manuel Bouyer wrote: On Mon, May 06, 2002 at 04:18:08PM -0400, Jean-Louis Martineau wrote: On Mon, May 06, 2002 at 11:32:09AM +0200, Manuel Bouyer wrote: On Fri, May 03, 2002 at 03:23:06PM +0200, Manuel Bouyer wrote: Hi, I'm looking for a way to force a backup to degraded mode, to holding disk with 2.4.3b3. Reading the docs I didn't find anything obvious yet. Here's what I'm trying to do: I have a 14 slots DLT changer. With a runspercycle of 7, I have plenty of space left on tapes, so I'd like to put 2 days of backup on a tape. I'm trying to get amanda do a degraded backup to holding disk (incrementals only), which should be quite small (less than 5G), one day out of two. The next day this backup would be flushed to tape before the scheduled backups. Of course I'd like to have all this under the same config, so that peoples running amrecover don't have to know if it was a full or degraded backup. The problem is that I don't know how to make it do a degraded dump when there is a valid tape available. Any idea ? I found a way of doing it: setup a second configuration with a dummy tape device (I used /dev/null) with holding disk, infofile, logdir and indexdir pointing to the same place as the config with tape changer. This seems to work (I tried amrecover from both tape and holding disk). That's BAD, you can't use the same logdir for two configurations, logfile will get erased. You will get the same problem with indexdir if you have a disk in both config. I don't understand why ... note that both configs won't run at the same day (one day for backup to tape, next day a degraded backup). When I use 'history' in amrecover I get all the backups in the list, with the proper tapes. Also the log files are all there. It works now because it's a new config, After tapecycle days, one config will erase the log and index of the other config. Why not use one config and edit your amanda.conf everyday, that could be easily done by cron. I though at this, but I prefer static config files. This avoids problems in case the server goes down in the middle of a backup. I think that running a small sed script to patch a static config file template before every amdump run is easier than using two configs. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Re: forcing a degraded backup
On Fri, May 03, 2002 at 03:23:06PM +0200, Manuel Bouyer wrote: Hi, I'm looking for a way to force a backup to degraded mode, to holding disk with 2.4.3b3. Reading the docs I didn't find anything obvious yet. Here's what I'm trying to do: I have a 14 slots DLT changer. With a runspercycle of 7, I have plenty of space left on tapes, so I'd like to put 2 days of backup on a tape. I'm trying to get amanda do a degraded backup to holding disk (incrementals only), which should be quite small (less than 5G), one day out of two. The next day this backup would be flushed to tape before the scheduled backups. Of course I'd like to have all this under the same config, so that peoples running amrecover don't have to know if it was a full or degraded backup. The problem is that I don't know how to make it do a degraded dump when there is a valid tape available. Any idea ? I found a way of doing it: setup a second configuration with a dummy tape device (I used /dev/null) with holding disk, infofile, logdir and indexdir pointing to the same place as the config with tape changer. This seems to work (I tried amrecover from both tape and holding disk). A minor annoyance is that both amcheck and amdump complain about the invalid tape, amd amdump report claims that something went bad when it's what I wanted. Wish to amanda hackers: would be nice if there was a config option to make amanda work without tape at all, without complains :) -- Manuel Bouyer [EMAIL PROTECTED] --
Re: forcing a degraded backup
On Mon, May 06, 2002 at 11:32:09AM +0200, Manuel Bouyer wrote: On Fri, May 03, 2002 at 03:23:06PM +0200, Manuel Bouyer wrote: Hi, I'm looking for a way to force a backup to degraded mode, to holding disk with 2.4.3b3. Reading the docs I didn't find anything obvious yet. Here's what I'm trying to do: I have a 14 slots DLT changer. With a runspercycle of 7, I have plenty of space left on tapes, so I'd like to put 2 days of backup on a tape. I'm trying to get amanda do a degraded backup to holding disk (incrementals only), which should be quite small (less than 5G), one day out of two. The next day this backup would be flushed to tape before the scheduled backups. Of course I'd like to have all this under the same config, so that peoples running amrecover don't have to know if it was a full or degraded backup. The problem is that I don't know how to make it do a degraded dump when there is a valid tape available. Any idea ? I found a way of doing it: setup a second configuration with a dummy tape device (I used /dev/null) with holding disk, infofile, logdir and indexdir pointing to the same place as the config with tape changer. This seems to work (I tried amrecover from both tape and holding disk). That's BAD, you can't use the same logdir for two configurations, logfile will get erased. You will get the same problem with indexdir if you have a disk in both config. Why not use one config and edit your amanda.conf everyday, that could be easily done by cron. Don't use /dev/null, your backup can go to it, use /dev/nosuchdevice instead. A minor annoyance is that both amcheck and amdump complain about the invalid tape, amd amdump report claims that something went bad when it's what I wanted. Wish to amanda hackers: would be nice if there was a config option to make amanda work without tape at all, without complains :) Wish you will become an amanda hackers :) Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
forcing a degraded backup
Hi, I'm looking for a way to force a backup to degraded mode, to holding disk with 2.4.3b3. Reading the docs I didn't find anything obvious yet. Here's what I'm trying to do: I have a 14 slots DLT changer. With a runspercycle of 7, I have plenty of space left on tapes, so I'd like to put 2 days of backup on a tape. I'm trying to get amanda do a degraded backup to holding disk (incrementals only), which should be quite small (less than 5G), one day out of two. The next day this backup would be flushed to tape before the scheduled backups. Of course I'd like to have all this under the same config, so that peoples running amrecover don't have to know if it was a full or degraded backup. The problem is that I don't know how to make it do a degraded dump when there is a valid tape available. Any idea ? -- Manuel Bouyer, LIP6, Universite Paris VI. [EMAIL PROTECTED] --
