Re: tapelist format
On Mon, Feb 27, 2017 at 02:23:10PM -0500, Jon LaBadie wrote: > On Mon, Feb 27, 2017 at 11:31:38AM -0500, Jean-Louis Martineau wrote: > > On 25/02/17 01:58 PM, Jon LaBadie wrote: > > > I'm getting a lot of these messages in my nightly report > > > > > >planner: Last full dump of cyber.jgcomp.com:Home on tape DS1-084 > > > overwritten in 1 run. > > >planner: Last full dump of cyber.jgcomp.com:Vault on tape DS1-079 > > > overwritten in 1 run. > > > > > > It made little sense as there are many full dumps or these > > > various DLEs sprinkled back to tape DS1-000. And, although > > > there were about 10 unused tapes remaining, I added a bunch > > > more which had no effect on the "will be overwritten" messages. > > > > > > Then I looked at the tapelist and found 2 different formats. > > > This is certainly due to my switching from CentOS packages > > > (amanda 3.3.3.) to Zmanda pre-built binaries for RHEL (amanda > > > 3.4.1). > > > > > > Previously labeled tapes have a 4 column layout but when the > > > new amanda version uses a tape, it modifies that layout to a > > > 7 column format adding "POOL", "STORAGE", and "CONFIG" columns. > > > Now my tapelist has 4 contiguous groups. > > > > > > recently labeled unused 7 column layout > > >previously labeled unused 4 column layout > > >previously labeledused 7 column layout > > >previously labeledused 4 column layout > > > > > > Why does the planner think it will overwrite the last full dumps? > > > > > > Would simply adding the additional 7 fields to the tapelist > > > correct this error or would other things have to change also? > > Jon, > > It should fix the issue. > > > > > > Would adding the extra columns adversely affect anything else? > > no. > > I didn't think so, I'll make the change and check tonights results. backup ran normally last night, no overwrite messages. Jon -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
Re: tapelist format
On Mon, Feb 27, 2017 at 11:31:38AM -0500, Jean-Louis Martineau wrote:
> Jon,
>
> Can you try the attached patch?
I'm running the zmanda pre-builts and do not have a build
system set up here.
>
> On 25/02/17 01:58 PM, Jon LaBadie wrote:
> > I'm getting a lot of these messages in my nightly report
> >
> >planner: Last full dump of cyber.jgcomp.com:Home on tape DS1-084
> > overwritten in 1 run.
> >planner: Last full dump of cyber.jgcomp.com:Vault on tape DS1-079
> > overwritten in 1 run.
> >
> > It made little sense as there are many full dumps or these
> > various DLEs sprinkled back to tape DS1-000. And, although
> > there were about 10 unused tapes remaining, I added a bunch
> > more which had no effect on the "will be overwritten" messages.
> >
> > Then I looked at the tapelist and found 2 different formats.
> > This is certainly due to my switching from CentOS packages
> > (amanda 3.3.3.) to Zmanda pre-built binaries for RHEL (amanda
> > 3.4.1).
> >
> > Previously labeled tapes have a 4 column layout but when the
> > new amanda version uses a tape, it modifies that layout to a
> > 7 column format adding "POOL", "STORAGE", and "CONFIG" columns.
> > Now my tapelist has 4 contiguous groups.
> >
> > recently labeled unused 7 column layout
> >previously labeled unused 4 column layout
> >previously labeledused 7 column layout
> >previously labeledused 4 column layout
> >
> > Why does the planner think it will overwrite the last full dumps?
> >
> > Would simply adding the additional 7 fields to the tapelist
> > correct this error or would other things have to change also?
> It should fix the issue.
> >
> > Would adding the extra columns adversely affect anything else?
> no.
I didn't think so, I'll make the change and check tonights results.
Jon
>
> Jean-Louis
> diff --git a/server-src/planner.c b/server-src/planner.c
> index 3464810..4d2b55b 100644
> --- a/server-src/planner.c
> +++ b/server-src/planner.c
> @@ -1291,6 +1291,8 @@ static int when_overwrite(
> int nb_in_storage;
> int runtapes;
> storage_t *st;
> +policy_s *po;
> +intretention_tapes;
>
> if ((tp = lookup_tapelabel(label)) == NULL)
> return 1; /* "shouldn't happen", but trigger warning message */
> @@ -1308,13 +1310,17 @@ static int when_overwrite(
> }
> if (!st)
> return 1;
> +po = lookup_policy(storage_get_policy(st));
> +if (!po)
> + return 1;
> +retention_tapes = policy_get_retention_tapes(po);
> runtapes = storage_get_runtapes(st);
> if (runtapes == 0) runtapes = 1;
>
> -nb = tape_overwrite(tp);
> -nb_in_storage = nb_tape_in_storage(tp->storage);
> -if (conf_tapecycle+1 > nb_in_storage)
> - nb += (conf_tapecycle+1 - nb_in_storage);
> +nb = tape_overwrite(st, tp);
> +nb_in_storage = nb_tape_in_storage(st);
> +if (retention_tapes > nb_in_storage)
> + nb += (retention_tapes - nb_in_storage + 1);
>
> tp->when_overwrite = (nb - 1) / runtapes;
> if (tp->when_overwrite < 0)
> diff --git a/server-src/tapefile.c b/server-src/tapefile.c
> index 7e0d81f..63f8ebf 100644
> --- a/server-src/tapefile.c
> +++ b/server-src/tapefile.c
> @@ -1175,14 +1175,21 @@ get_retention_type(
>
> int
> tape_overwrite(
> +storage_t *st,
> tape_t *tp)
> {
> tape_t *tp1;
> int nb_tapes = 0;
>
> for (tp1 = tp; tp1 != NULL; tp1 = tp1->next) {
> - if (!tp1->retention && tp1->storage && tp->storage &&
> - g_str_equal(tp->storage, tp1->storage)) {
> + if (!tp1->retention &&
> + (((!tp1->storage || !tp->storage) &&
> + match_labelstr(storage_get_labelstr(st),
> + storage_get_autolabel(st),
> + tp1->label, tp1->barcode, tp1->meta,
> + storage_name(st))) ||
> + (tp1->storage && tp->storage &&
> + g_str_equal(tp->storage, tp1->storage {
> nb_tapes++;
> }
> }
> @@ -1191,14 +1198,18 @@ tape_overwrite(
>
> int
> nb_tape_in_storage(
> -char *storage_name)
> +storage_t *st)
> {
> tape_t *tp;
> int nb_tapes = 0;
> -
> +char *storage = storage_name(st);
> for (tp = tape_list; tp != NULL; tp = tp->next) {
> - if ((!storage_name && !tp->storage) ||
> - (storage_name && tp->storage &&
> g_str_equal(storage_name,tp->storage))) {
> + if (((!storage || !tp->storage) &&
> + match_labelstr(storage_get_labelstr(st),
> + storage_get_autolabel(st),
> + tp->label, tp->barcode, tp->meta,
> + storage_name(st))) ||
> + (storage && tp->storage && g_str_equal(storage, tp->storage))) {
> nb_tapes++;
> }
> }
> diff --git a/server-src/tapefile.h b/server-src/tapefile.h
> index 4af86da..547f8ef 100644
> --- a/server-src/tapefile.h
> +++ b/server-src/tapefile.h
> @@ -35,6 +35,
Re: tapelist format
Jon,
Can you try the attached patch?
On 25/02/17 01:58 PM, Jon LaBadie wrote:
> I'm getting a lot of these messages in my nightly report
>
>planner: Last full dump of cyber.jgcomp.com:Home on tape DS1-084
> overwritten in 1 run.
>planner: Last full dump of cyber.jgcomp.com:Vault on tape DS1-079
> overwritten in 1 run.
>
> It made little sense as there are many full dumps or these
> various DLEs sprinkled back to tape DS1-000. And, although
> there were about 10 unused tapes remaining, I added a bunch
> more which had no effect on the "will be overwritten" messages.
>
> Then I looked at the tapelist and found 2 different formats.
> This is certainly due to my switching from CentOS packages
> (amanda 3.3.3.) to Zmanda pre-built binaries for RHEL (amanda
> 3.4.1).
>
> Previously labeled tapes have a 4 column layout but when the
> new amanda version uses a tape, it modifies that layout to a
> 7 column format adding "POOL", "STORAGE", and "CONFIG" columns.
> Now my tapelist has 4 contiguous groups.
>
> recently labeled unused 7 column layout
>previously labeled unused 4 column layout
>previously labeledused 7 column layout
>previously labeledused 4 column layout
>
> Why does the planner think it will overwrite the last full dumps?
>
> Would simply adding the additional 7 fields to the tapelist
> correct this error or would other things have to change also?
It should fix the issue.
>
> Would adding the extra columns adversely affect anything else?
no.
Jean-Louis
diff --git a/server-src/planner.c b/server-src/planner.c
index 3464810..4d2b55b 100644
--- a/server-src/planner.c
+++ b/server-src/planner.c
@@ -1291,6 +1291,8 @@ static int when_overwrite(
int nb_in_storage;
int runtapes;
storage_t *st;
+policy_s *po;
+intretention_tapes;
if ((tp = lookup_tapelabel(label)) == NULL)
return 1; /* "shouldn't happen", but trigger warning message */
@@ -1308,13 +1310,17 @@ static int when_overwrite(
}
if (!st)
return 1;
+po = lookup_policy(storage_get_policy(st));
+if (!po)
+ return 1;
+retention_tapes = policy_get_retention_tapes(po);
runtapes = storage_get_runtapes(st);
if (runtapes == 0) runtapes = 1;
-nb = tape_overwrite(tp);
-nb_in_storage = nb_tape_in_storage(tp->storage);
-if (conf_tapecycle+1 > nb_in_storage)
- nb += (conf_tapecycle+1 - nb_in_storage);
+nb = tape_overwrite(st, tp);
+nb_in_storage = nb_tape_in_storage(st);
+if (retention_tapes > nb_in_storage)
+ nb += (retention_tapes - nb_in_storage + 1);
tp->when_overwrite = (nb - 1) / runtapes;
if (tp->when_overwrite < 0)
diff --git a/server-src/tapefile.c b/server-src/tapefile.c
index 7e0d81f..63f8ebf 100644
--- a/server-src/tapefile.c
+++ b/server-src/tapefile.c
@@ -1175,14 +1175,21 @@ get_retention_type(
int
tape_overwrite(
+storage_t *st,
tape_t *tp)
{
tape_t *tp1;
int nb_tapes = 0;
for (tp1 = tp; tp1 != NULL; tp1 = tp1->next) {
- if (!tp1->retention && tp1->storage && tp->storage &&
- g_str_equal(tp->storage, tp1->storage)) {
+ if (!tp1->retention &&
+ (((!tp1->storage || !tp->storage) &&
+ match_labelstr(storage_get_labelstr(st),
+ storage_get_autolabel(st),
+ tp1->label, tp1->barcode, tp1->meta,
+ storage_name(st))) ||
+ (tp1->storage && tp->storage &&
+ g_str_equal(tp->storage, tp1->storage {
nb_tapes++;
}
}
@@ -1191,14 +1198,18 @@ tape_overwrite(
int
nb_tape_in_storage(
-char *storage_name)
+storage_t *st)
{
tape_t *tp;
int nb_tapes = 0;
-
+char *storage = storage_name(st);
for (tp = tape_list; tp != NULL; tp = tp->next) {
- if ((!storage_name && !tp->storage) ||
- (storage_name && tp->storage && g_str_equal(storage_name,tp->storage))) {
+ if (((!storage || !tp->storage) &&
+ match_labelstr(storage_get_labelstr(st),
+ storage_get_autolabel(st),
+ tp->label, tp->barcode, tp->meta,
+ storage_name(st))) ||
+ (storage && tp->storage && g_str_equal(storage, tp->storage))) {
nb_tapes++;
}
}
diff --git a/server-src/tapefile.h b/server-src/tapefile.h
index 4af86da..547f8ef 100644
--- a/server-src/tapefile.h
+++ b/server-src/tapefile.h
@@ -35,6 +35,7 @@
#define TAPEFILE_H
#include "amanda.h"
+#include "conffile.h"
typedef enum {
RETENTION_NO = 0,
@@ -110,7 +111,7 @@ int volume_is_reusable(const char *label);
int guess_runs_from_tapelist(void);
gchar **list_new_tapes(char *storage_n, int nb);
RetentionType get_retention_type(char *pool, char *label);
-int tape_overwrite(tape_t *tp);
-int nb_tape_in_storage(char *storage_name);
+int tape_overwrite(storage_t *st, tape_t *tp);
+int nb_tape_in_storage(storage_t *st);
#endif /* !TAPEFILE_H */
Re: Tapelist
On Tue, Mar 11, 2008 at 11:57:05AM -0500, Arthur Smith wrote: > Jon, > > Thanks! I want to be sure I understand correctly: > > I have 10 tapes, labeled monday1, tuesday1, etc.. through friday2. I > should now be able to recreate the tapelist file like so: > > 0 monday1 reuse > 0 tuesday1 reuse > > and so on, and amanda will use them in the order they are put in, > correct? As if they were actually new tapes (even though they're not)... > > Am I on track? > > --acorn > > Jon LaBadie wrote: > >On Tue, Mar 11, 2008 at 10:25:11AM -0500, Arthur Smith wrote: > > > >>Hi all, I'm hoping someone can help me with a confusing situation i've > >>gotten myself into... > >> > >>First of all, I have configured and tested Amanda to satisfaction, and > >>am ready to use it in production. Thus, I found and followed the steps > >>in this FAQ: > >> > >>http://www.amanda.org/docs/faq.html#id346890 > >> > >> > >> > >>Ok, I'm done with testing /Amanda/, now I want to put it in production. > >>How can I reset its databases so as to start from scratch? > >> > >> > >> > >... > > > >> TAPE MANAGEMENT > >> > >>The /tapelist/ file contains the list of tapes in active use. This file > >>is maintained entirely by Amanda and should not be created or edited > >>during normal operation. > >> > >> > >>So Now that i have amanda all set up, and have all my tapes properly > >>labeled, I have deleted my tapelist file, and don't know where to go > >>from here! > >> > >>Thanks in advance for any help! > >> > > > > > >You certainly can relabel all the tapes. Use the -f option to > >force overwriting the existing amanda label on the tape. > >First you may have to create an empty tapelist file, > >owned by the amanda user/group with rw for owner. > > > >Alternatively you can manually create the entire file with > >lines of the form: > > > > 0 reuse > > > >For example here are four lines from an old tapelist file: > > > > > >0 FTape-12 reuse > >0 FTape-11 reuse > >20031031 FTape-10 reuse > >20031030 FTape-09 reuse > > > >The top two tapes have not been used yet, the bottom two were. > >Your entries should look like the top two but with your tape > >labels rather than FTape-XX. > > > >jl > > > Others have already commented on DOW labeling, to which I'll add a simple YECH to show I agree. As to the tapelist file, amanda will happily use ANY unused tape (noted with a 0 date) in the tapelist file. Its prefered order has the "next expected tape" at the bottom of the file. The most recently used tape is at the top. If you really are going to use DOW labelling I have recommendation for the first set of runs. Edit the tapelist file before each run and add the tape you plan to use that day. You could create all entries but make all but the active one "noreuse". Then edit that to "reuse" for each daily tape. Otherwise you could be out of order right from the start. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: Tapelist
On Tue, Mar 11, 2008 at 11:57:05AM -0500, Arthur Smith enlightened us: > Jon, > > Thanks! I want to be sure I understand correctly: > > I have 10 tapes, labeled monday1, tuesday1, etc.. through friday2. I > should now be able to recreate the tapelist file like so: > > 0 monday1 reuse > 0 tuesday1 reuse > > and so on, and amanda will use them in the order they are put in, > correct? As if they were actually new tapes (even though they're not)... > > Am I on track? > Yes, with the exception of labeling tapes with days of the week. It's generally not recommended because amanda has no concept of what day it is and will merely ask for the next tape needed. So if you miss a day, run over onto another tape, etc., you end up with strange situations like using monday1 on a Thursday. It also makes writing the regexp in your config file harder. It is recommended to have some prefix string (e.g. Daily, Archive, Monthly) followed by incremental numbers. Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263
Re: Tapelist
On 2008-03-11 17:57, Arthur Smith wrote: Thanks! I want to be sure I understand correctly: I have 10 tapes, labeled monday1, tuesday1, etc.. through friday2. I should now be able to recreate the tapelist file like so: 0 monday1 reuse 0 tuesday1 reuse and so on, and amanda will use them in the order they are put in, correct? As if they were actually new tapes (even though they're not)... Am I on track? You are on track about the format of the tapelist file but falling off on the other side of the track when choosing the tape labels. :-) It's not a good idea to label the tapes "monday" etc, unless you are 100% sure that backup on each day succeed, and you never take a day off or forget to switch tapes. The first time the backups from e.g. monday are not on that tape the tapes get out of sequence. That can happen because you forgot it insert it, or because the server crashed, or you need that tape to flush the holdingdisk on the previous day, or you need to keep one tape aside because it contains a full backup of a server that crashed, and you're waiting for the new disks to arrive, etc. (And I probably forgot another 100 reasons...) Just number them "Daily-01" etc. My 0.02€ advice. -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: Tapelist
Jon, Thanks! I want to be sure I understand correctly: I have 10 tapes, labeled monday1, tuesday1, etc.. through friday2. I should now be able to recreate the tapelist file like so: 0 monday1 reuse 0 tuesday1 reuse and so on, and amanda will use them in the order they are put in, correct? As if they were actually new tapes (even though they're not)... Am I on track? --acorn Jon LaBadie wrote: On Tue, Mar 11, 2008 at 10:25:11AM -0500, Arthur Smith wrote: Hi all, I'm hoping someone can help me with a confusing situation i've gotten myself into... First of all, I have configured and tested Amanda to satisfaction, and am ready to use it in production. Thus, I found and followed the steps in this FAQ: http://www.amanda.org/docs/faq.html#id346890 Ok, I'm done with testing /Amanda/, now I want to put it in production. How can I reset its databases so as to start from scratch? ... TAPE MANAGEMENT The /tapelist/ file contains the list of tapes in active use. This file is maintained entirely by Amanda and should not be created or edited during normal operation. So Now that i have amanda all set up, and have all my tapes properly labeled, I have deleted my tapelist file, and don't know where to go from here! Thanks in advance for any help! You certainly can relabel all the tapes. Use the -f option to force overwriting the existing amanda label on the tape. First you may have to create an empty tapelist file, owned by the amanda user/group with rw for owner. Alternatively you can manually create the entire file with lines of the form: 0 reuse For example here are four lines from an old tapelist file: 0 FTape-12 reuse 0 FTape-11 reuse 20031031 FTape-10 reuse 20031030 FTape-09 reuse The top two tapes have not been used yet, the bottom two were. Your entries should look like the top two but with your tape labels rather than FTape-XX. jl -- Arthur Smith, MCP Network Administrator SomethingCool.com LLC
RE Tapelist
re-label your tapes (if you don't care about the data they contain). This will re-populate your tapelist file. Use the "force" switch if needed. Cyr Arthur Smith <[EMAIL PROTECTED]> Envoyé par : [EMAIL PROTECTED] 11/03/2008 16:25 A [email protected] cc Objet Tapelist Hi all, I'm hoping someone can help me with a confusing situation i've gotten myself into... First of all, I have configured and tested Amanda to satisfaction, and am ready to use it in production. Thus, I found and followed the steps in this FAQ: http://www.amanda.org/docs/faq.html#id346890 Ok, I'm done with testing /Amanda/, now I want to put it in production. How can I reset its databases so as to start from scratch? First, remove the `curinfo' database. By default, it is a directory, but, if you have selected any other database format (don't, they're deprecated), they may be files with extensions such as .dir and .pag. Then, remove any log files from the log directory: |log..| and |amdump.|. Finally, remove the |tapelist| file, stored in the directory that contains |amanda.conf|, unless |amanda.conf| specifies otherwise. Depending on the tape changer you have selected, you may also want to reset its state file. This I did, and now, when running amcheck i get: "/etc/amanda/DailySet1/disklist", line 82: disk dumptype expected Amanda Tape Server Host Check -- ERROR: tapefile /etc/amanda/DailySet1/tapelist: No such file or directory, you must create an empty file. So, I search for the permissions the empty file needs to be created with, but stumble upon this: http://www.linuxmanpages.com/man8/amanda.8.php TAPE MANAGEMENT The /tapelist/ file contains the list of tapes in active use. This file is maintained entirely by Amanda and should not be created or edited during normal operation. So Now that i have amanda all set up, and have all my tapes properly labeled, I have deleted my tapelist file, and don't know where to go from here! Thanks in advance for any help! --acorn
Re: Tapelist
On Tue, Mar 11, 2008 at 10:25:11AM -0500, Arthur Smith wrote: > Hi all, I'm hoping someone can help me with a confusing situation i've > gotten myself into... > > First of all, I have configured and tested Amanda to satisfaction, and > am ready to use it in production. Thus, I found and followed the steps > in this FAQ: > > http://www.amanda.org/docs/faq.html#id346890 > > > > Ok, I'm done with testing /Amanda/, now I want to put it in production. > How can I reset its databases so as to start from scratch? > > ... > > >TAPE MANAGEMENT > > The /tapelist/ file contains the list of tapes in active use. This file > is maintained entirely by Amanda and should not be created or edited > during normal operation. > > > So Now that i have amanda all set up, and have all my tapes properly > labeled, I have deleted my tapelist file, and don't know where to go > from here! > > Thanks in advance for any help! You certainly can relabel all the tapes. Use the -f option to force overwriting the existing amanda label on the tape. First you may have to create an empty tapelist file, owned by the amanda user/group with rw for owner. Alternatively you can manually create the entire file with lines of the form: 0 reuse For example here are four lines from an old tapelist file: 0 FTape-12 reuse 0 FTape-11 reuse 20031031 FTape-10 reuse 20031030 FTape-09 reuse The top two tapes have not been used yet, the bottom two were. Your entries should look like the top two but with your tape labels rather than FTape-XX. jl -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 12027 Creekbend Drive (703) 787-0884 Reston, VA 20194 (703) 787-0922 (fax)
Re: tapelist no-reuse set automatically
On 2006-09-27 16:54, McGraw, Robert P. wrote: I run an archive once a month and would like to mark tapes that have been used by the archive as no-reuse. I have to do this manually now. Is there a way that this can be done automatically with an amanda configuration parameter? I have looked for something like this and have not seen anything but just wanted to be sure. If not any other suggestions. Untested... (sorry, no time to test, but you get the idea...) #!/bin/sh # Run this command by cron instead of amdump # like: /usr/local/bin/amandabackup archive CONFIG=$1 amdump $CONFIG LOGF=`ls -t /var/lib/amanda/$CONFIG/log.2* | head -1` grep '^START taper .* label ' $LOGF | while read start taper datestamp thedatestamp label thelabel rest do amadmin $CONFIG no-reuse $thelabel done -- Paul Bijnens, xplanation Technology ServicesTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, ^^, * * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ... * * ... "Are you sure?" ... YES ... Phew ... I'm out * ***
Re: tapelist no-reuse set automatically
On Wed, Sep 27, 2006 at 10:54:20AM -0400, McGraw, Robert P. wrote: > > I run an archive once a month and would like to mark tapes that have been > used by the archive as no-reuse. I have to do this manually now. > > Is there a way that this can be done automatically with an amanda > configuration parameter? I have looked for something like this and have not > seen anything but just wanted to be sure. If not any other suggestions. I.e. you want to use a "new", "labeled", "never previously used by amanda" tape each run. tapecycle 100 Should cover quite a few years. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist - how to edit
Thanks for your insight into this. As it stands, I'm only using 5 tapes and amanda hasn't "gone into production" yet. So it really is a small matter if I "lose" what has already been backed up to those tapes. In fact, if I amrmtape'd all of the existing tapes and start over again, it wouldn't really matter at this stage. However, I want to put amanda into production this week, so would like to have everything looking nice and neat. This is purely as a convenience to me - I just don't like the tape numbers being out of sequence... Jon LaBadie wrote: > > On Mon, Aug 07, 2006 at 09:02:48AM -0400, Jon LaBadie wrote: >> On Mon, Aug 07, 2006 at 02:19:12AM -0700, Joe Donner (sent by Nabble.com) >> wrote: >> > >> > Does anyone know, please? >> > >> > Will appreciate your thoughts a lot. >> > >> > Thanks. >> > >> > >> > Joe Donner wrote: >> > > >> > > Dear all, >> > > >> > > my tapelist has become a bit confused, due to my own fault, by me >> adding >> > > tapes in the "middle" of my numbered sequence. At the moment it >> looks >> > > like this: >> > > 20060803 daily-5 reuse >> > > 20060802 daily-1 reuse >> > > 20060801 daily-3 reuse >> > > 20060731 daily-4 reuse >> > > 20060731 daily-2 reuse >> > > >> > > daily-5 was used last night, and amanda now wants daily-2. >> > > >> > > What is the correct way of editing this so amanda will use the >> daily-1 >> > > next, then daily-2, etc.? >> > > >> > > Would this be correct (I'm not sure of the implications of the dates >> in >> > > the tapelist, and whether I will need to adjust those dates as >> well)?: >> > > 20060803 daily-5 reuse >> > > 20060731 daily-4 reuse >> > > 20060801 daily-3 reuse >> > > 20060731 daily-2 reuse >> > > 20060802 daily-1 reuse >> > > >> > > (I'm using full dumps at the moment for every amdump run, if that >> > > helps...) >> > > >> > > Your advice will be much appreciated, as always. >> > > >> >> I think tapelist sequence is the last thing considered when >> selecting the next tape to be used. Only those used earlier >> or equal to tapecycle runs ago are considered. >> >> So yes, date does matter. >> >> Be aware that if you overwrite a tape out of sequence, >> the dumps of each DLE higher in level and newer lose a >> lot of their backup value. >> > > Meant to add, amcheck -s and amtape taper each show what > tape will be selected to use next. > > Save a copy of your tapelist file, edit and test. > > -- > Jon H. LaBadie [EMAIL PROTECTED] > JG Computing > 4455 Province Line Road(609) 252-0159 > Princeton, NJ 08540-4322 (609) 683-7220 (fax) > > -- View this message in context: http://www.nabble.com/tapelist---how-to-edit-tf2050982.html#a5702341 Sent from the Amanda - Users forum at Nabble.com.
Re: tapelist - how to edit
> > my tapelist has become a bit confused, due to my own fault, by me adding > > tapes in the "middle" of my numbered sequence. At the moment it looks > > like this: > > 20060803 daily-5 reuse > > 20060802 daily-1 reuse > > 20060801 daily-3 reuse > > 20060731 daily-4 reuse > > 20060731 daily-2 reuse If the matter is just to make your life easy, have a natural sequence of numbers when picking up the next tape for backup, why not changing the label sticker on the tape (not Amanda label). And on the sticker you write in big: TAPE 1 and in small daily-1 TAPE 2 daily-3 TAPE 3 daily-4 TAPE 4 daily-2 TAPE 5 daily-5 And you do not confuse Amanda :) That is definitely how I would do. Bests, Olivier
Re: tapelist - how to edit
On Mon, Aug 07, 2006 at 09:02:48AM -0400, Jon LaBadie wrote: > On Mon, Aug 07, 2006 at 02:19:12AM -0700, Joe Donner (sent by Nabble.com) > wrote: > > > > Does anyone know, please? > > > > Will appreciate your thoughts a lot. > > > > Thanks. > > > > > > Joe Donner wrote: > > > > > > Dear all, > > > > > > my tapelist has become a bit confused, due to my own fault, by me adding > > > tapes in the "middle" of my numbered sequence. At the moment it looks > > > like this: > > > 20060803 daily-5 reuse > > > 20060802 daily-1 reuse > > > 20060801 daily-3 reuse > > > 20060731 daily-4 reuse > > > 20060731 daily-2 reuse > > > > > > daily-5 was used last night, and amanda now wants daily-2. > > > > > > What is the correct way of editing this so amanda will use the daily-1 > > > next, then daily-2, etc.? > > > > > > Would this be correct (I'm not sure of the implications of the dates in > > > the tapelist, and whether I will need to adjust those dates as well)?: > > > 20060803 daily-5 reuse > > > 20060731 daily-4 reuse > > > 20060801 daily-3 reuse > > > 20060731 daily-2 reuse > > > 20060802 daily-1 reuse > > > > > > (I'm using full dumps at the moment for every amdump run, if that > > > helps...) > > > > > > Your advice will be much appreciated, as always. > > > > > I think tapelist sequence is the last thing considered when > selecting the next tape to be used. Only those used earlier > or equal to tapecycle runs ago are considered. > > So yes, date does matter. > > Be aware that if you overwrite a tape out of sequence, > the dumps of each DLE higher in level and newer lose a > lot of their backup value. > Meant to add, amcheck -s and amtape taper each show what tape will be selected to use next. Save a copy of your tapelist file, edit and test. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist - how to edit
On Mon, Aug 07, 2006 at 02:19:12AM -0700, Joe Donner (sent by Nabble.com) wrote: > > Does anyone know, please? > > Will appreciate your thoughts a lot. > > Thanks. > > > Joe Donner wrote: > > > > Dear all, > > > > my tapelist has become a bit confused, due to my own fault, by me adding > > tapes in the "middle" of my numbered sequence. At the moment it looks > > like this: > > 20060803 daily-5 reuse > > 20060802 daily-1 reuse > > 20060801 daily-3 reuse > > 20060731 daily-4 reuse > > 20060731 daily-2 reuse > > > > daily-5 was used last night, and amanda now wants daily-2. > > > > What is the correct way of editing this so amanda will use the daily-1 > > next, then daily-2, etc.? > > > > Would this be correct (I'm not sure of the implications of the dates in > > the tapelist, and whether I will need to adjust those dates as well)?: > > 20060803 daily-5 reuse > > 20060731 daily-4 reuse > > 20060801 daily-3 reuse > > 20060731 daily-2 reuse > > 20060802 daily-1 reuse > > > > (I'm using full dumps at the moment for every amdump run, if that > > helps...) > > > > Your advice will be much appreciated, as always. > > I think tapelist sequence is the last thing considered when selecting the next tape to be used. Only those used earlier or equal to tapecycle runs ago are considered. So yes, date does matter. Be aware that if you overwrite a tape out of sequence, the dumps of each DLE higher in level and newer lose a lot of their backup value. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist - how to edit
Does anyone know, please? Will appreciate your thoughts a lot. Thanks. Joe Donner wrote: > > Dear all, > > my tapelist has become a bit confused, due to my own fault, by me adding > tapes in the "middle" of my numbered sequence. At the moment it looks > like this: > 20060803 daily-5 reuse > 20060802 daily-1 reuse > 20060801 daily-3 reuse > 20060731 daily-4 reuse > 20060731 daily-2 reuse > > daily-5 was used last night, and amanda now wants daily-2. > > What is the correct way of editing this so amanda will use the daily-1 > next, then daily-2, etc.? > > Would this be correct (I'm not sure of the implications of the dates in > the tapelist, and whether I will need to adjust those dates as well)?: > 20060803 daily-5 reuse > 20060731 daily-4 reuse > 20060801 daily-3 reuse > 20060731 daily-2 reuse > 20060802 daily-1 reuse > > (I'm using full dumps at the moment for every amdump run, if that > helps...) > > Your advice will be much appreciated, as always. > -- View this message in context: http://www.nabble.com/tapelist---how-to-edit-tf2050982.html#a5681796 Sent from the Amanda - Users forum at Nabble.com.
Re: Tapelist issue only using 3 tape out of a tapecycle of 10.
Hi In fact I have used both procedures but I had notes from a particular url that had a list of the usual error and solutions. My Amanda also reports that I need to use DailySet101 next Thus it's back to normal. As it did only cycle through DailySet108 - DailySet110. Thanks for the advice. Cheers On Thu, 2005-10-06 at 10:10 +0200, Stefan G. Weichinger wrote: > Chuck Amadi Systems Administrator wrote: > > > In order to keep the set of tapes consistant, the new tape should have > > the same label as the old tape. So I used the label DailySet107. > > > > 1. Connect on Amanda server, first as root, then change to the user > > amanda, with the command su. > > 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line > > containing the label,(DailySet107) Usually the line is the last > > one of the file. > > 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the > > same way. Usually the line is the one before the last. > > 4. prepare a new tape and write the label on it with the command: > > amlabel normal DailySet107. > > 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that > > the line with the label is back, but it is now at the top of the > > file, and the number at the begining is 0. Just move that line > > to the bottom of the file. This worked So I assumed. > > Editing the tapelist by hand should be avoided, in general. > Your procedure works, but you could have just used "amlabel -f" on the > new tape as well ... > > Stefan > -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: Tapelist issue only using 3 tape out of a tapecycle of 10.
Chuck Amadi Systems Administrator wrote: In order to keep the set of tapes consistant, the new tape should have the same label as the old tape. So I used the label DailySet107. 1. Connect on Amanda server, first as root, then change to the user amanda, with the command su. 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line containing the label,(DailySet107) Usually the line is the last one of the file. 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the same way. Usually the line is the one before the last. 4. prepare a new tape and write the label on it with the command: amlabel normal DailySet107. 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that the line with the label is back, but it is now at the top of the file, and the number at the begining is 0. Just move that line to the bottom of the file. This worked So I assumed. Editing the tapelist by hand should be avoided, in general. Your procedure works, but you could have just used "amlabel -f" on the new tape as well ... Stefan -- Stefan G. Weichinger AMANDA core team member mailto://[EMAIL PROTECTED] -- oops! linux consulting & implementation http://www.oops.co.at --
RE: Tapelist issue only using 3 tape out of a tapecycle of 10.
Could your tapecycle be smaller now than when you labelled the tapes? I am not sure exactly the effect this would have but if it were reduced it may ignore the other tapes Scott... Scott R. Burns NETCON Technologies Incorporated Suite 135 - 4474 Blakie Road London, Ontario, Canada N6L 1G7 Voice: +1.519.652.0401 Fax: +1.519.652.9275 Web: www.netcontech.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chuck Amadi Systems Administrator Sent: Wednesday, October 05, 2005 5:07 AM To: Amanda List Cc: Chuck Subject: Tapelist issue only using 3 tape out of a tapecycle of 10. Hi I have noticed that the backup schedule as changed somehow and is only using DailySet108 to DailySet110 (3 tapes) is there away to check and force it to use the next tape after DailySet110 which should be DailySet101. I did relabel a faulty tape recently. finaceserver:/etc/amanda/DailySet1 # less tapelist 20051005 DailySet109 reuse 20050930 DailySet108 reuse 20050929 DailySet107 reuse 20050922 DailySet106 reuse 20050916 DailySet105 reuse 20050915 DailySet104 reuse 20050909 DailySet103 reuse 20050908 DailySet102 reuse 20050907 DailySet101 reuse 20050906 DailySet110 reuse I did Replace a tape DailySet107 which Amanda reports a tape to be faulty, the label could not be read on the tape, or the data could not be saved on the tape. It is time to replace the tape. In order to keep the set of tapes consistant, the new tape should have the same label as the old tape. So I used the label DailySet107. 1. Connect on Amanda server, first as root, then change to the user amanda, with the command su. 2. Edit the file /etc/amanda/DailySet1/tapelist and remove the line containing the label,(DailySet107) Usually the line is the last one of the file. 3. Edit the file /usr/local/etc/amanda/tapelist.yesterday in the same way. Usually the line is the one before the last. 4. prepare a new tape and write the label on it with the command: amlabel normal DailySet107. 5. Edit the file /etc/amanda/DailySet1/tapelist again, note that the line with the label is back, but it is now at the top of the file, and the number at the begining is 0. Just move that line to the bottom of the file. This worked So I assumed. Cheers -- Unix/ Linux Systems Administrator Chuck Amadi The Surgical Material Testing Laboratory (SMTL), Princess of Wales Hospital Coity Road Bridgend, United Kingdom, CF31 1RQ. Email chuck.smtl.co.uk Tel: +44 1656 752820 Fax: +44 1656 752830
Re: tapelist~ file ?
Guy Dallaire a e'crit: > I have a file named tapelist~ in my amanda config directory. Can it be > safely removed ? That's a question for the Emacs mailing list: [email protected] :)
Re: tapelist~ file ?
Guy Dallaire wrote: I have a file named tapelist~ in my amanda config directory. Can it be safely removed ? That's an editor backup file, emacs perhaps. amanda doesn't use it for anything. Alex -- Alexander Jolk / BUF Compagnie tel +33-1 42 68 18 28 / fax +33-1 42 68 18 29
Re: tapelist and amcheck disagree
This one time, at band camp, Brian Cuttler wrote: > >Did you have some flushes during the last period ? Yeah, many. >I believe its not just the eldest reusable tape, I believe amanda >will not want to re-use it with tapecycle dates of it having been >last written. Ok, thanks, that may be it. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg
Re: tapelist and amcheck disagree
Did you have some flushes during the last period ? I believe its not just the eldest reusable tape, I believe amanda will not want to re-use it with tapecycle dates of it having been last written. On Wed, Oct 06, 2004 at 06:14:19PM +1000, Jamie Wilkinson wrote: > The tapelist file says my tape ANCHOR3 is reusable. Grepping through the > output of amadmin export for ANCHOR3 returns nothing. However, amcheck > tells me that it can't overwrite active tape ANCHOR3. > > There are 16 tapes in the tapecycle, runtapes is 1, dumpcycle is 5 days, > runspercycle is 5. > > Where is amcheck looking for the active tape list? How can I see what > amcheck thinks is on ANCHOR3 that is so important still? > > -- > [EMAIL PROTECTED] http://spacepants.org/jaq.gpg --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
Re: tapelist and amcheck disagree
This one time, at band camp, Jamie Wilkinson wrote: >This one time, at band camp, Jamie Wilkinson wrote: >>The tapelist file says my tape ANCHOR3 is reusable. Grepping through the >>output of amadmin export for ANCHOR3 returns nothing. However, amcheck >>tells me that it can't overwrite active tape ANCHOR3. >> >>There are 16 tapes in the tapecycle, runtapes is 1, dumpcycle is 5 days, >>runspercycle is 5. >> >>Where is amcheck looking for the active tape list? How can I see what >>amcheck thinks is on ANCHOR3 that is so important still? > >Further to this, the file ANCHOR3.toc in /var/lib/amanda/anchor tells me the >date of all the dumps on that tape date back 3 months. That's probably >correct, and there have definitely been level 0 dumps of everything since >then. Bah, I created those files in July! Anyway, I've cross checked this tape against the database with amadmin find, and I'm confident it doesn't have anything important on it, so amrmtape and amlabel later i have a shiny new ANCHOR3 which amcheck is accepting. I'd still like to know why amcheck didn't like it in the first place. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg
Re: tapelist and amcheck disagree
This one time, at band camp, Jamie Wilkinson wrote: >The tapelist file says my tape ANCHOR3 is reusable. Grepping through the >output of amadmin export for ANCHOR3 returns nothing. However, amcheck >tells me that it can't overwrite active tape ANCHOR3. > >There are 16 tapes in the tapecycle, runtapes is 1, dumpcycle is 5 days, >runspercycle is 5. > >Where is amcheck looking for the active tape list? How can I see what >amcheck thinks is on ANCHOR3 that is so important still? Further to this, the file ANCHOR3.toc in /var/lib/amanda/anchor tells me the date of all the dumps on that tape date back 3 months. That's probably correct, and there have definitely been level 0 dumps of everything since then. -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg
Re: tapelist file
On Mon, Oct 04, 2004 at 07:02:01PM -0400, Gene Heskett wrote: > On Monday 04 October 2004 06:41, [EMAIL PROTECTED] wrote: > >Hi, > > i' m trying to label a tape with the command > > amlabel -f "config" "string" and the answer is "amlabel: could not > > load tapelis "PATH_TO_TAPELIST" > > i' ve tried with an empty tapelist file , without tapelist file > > and with a tapelist file with only ste "string" ; also in my > > amanda.conf file as "labelstr" i got only th "string": So what' s > > up please HLP! > > Teo > > Your amanda.conf file should have a line in it that points at the file > "tapelist", in my case its: > tapelist "/usr/local/etc/amanda/Daily/tapelist" > > This file must exist, and it must be owned/readable/writeable by > amanda. Its sufficient, generally, to just have the user amanda > touch it to create it with the correct perms. Also, in the error > message you quoted, the final 't' is missing, so I'd suspect a typo > of some sort there. > I forget the details now, and whether it was fixed, but someone reported that the tapelist file not only had to exist, but either had to be zero length (not even a blank line) or had to have a blank line. Sorry I forget which. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist file
On Monday 04 October 2004 06:41, [EMAIL PROTECTED] wrote: >Hi, > i' m trying to label a tape with the command > amlabel -f "config" "string" and the answer is "amlabel: could not > load tapelis "PATH_TO_TAPELIST" > i' ve tried with an empty tapelist file , without tapelist file > and with a tapelist file with only ste "string" ; also in my > amanda.conf file as "labelstr" i got only th "string": So what' s > up please HLP! > Teo Your amanda.conf file should have a line in it that points at the file "tapelist", in my case its: tapelist "/usr/local/etc/amanda/Daily/tapelist" This file must exist, and it must be owned/readable/writeable by amanda. Its sufficient, generally, to just have the user amanda touch it to create it with the correct perms. Also, in the error message you quoted, the final 't' is missing, so I'd suspect a typo of some sort there. The "string" specified in your amanda.conf as a regex expandable, must match the label you are trying to use. If not, its not an amanda tape. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.27% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Re: tapelist file
On Mon, Oct 04, 2004 at 12:41:04PM +0200, [EMAIL PROTECTED] wrote: > Hi, > i' m trying to label a tape with the command > amlabel -f "config" "string" and the answer is "amlabel: could not load > tapelis "PATH_TO_TAPELIST" >i' ve tried with an empty tapelist file , without tapelist file and > with a tapelist file with only ste "string" ; also in my amanda.conf > file as "labelstr" i got only th "string": So what' s up >please HLP! Couple of things of the type "is it plugged in?" variety. - can you manipulate your tape drive with non-amanda commands, eg. dd, mt, tar, ... - did you use real values rather than "config" and "string" - have you gone throught the amanda.conf file and set the 99 values that need conversion from forms such as "string" to things such as "/dev/nst0" and commented and uncommented as appropriate - can you manipulate your tape drive with amanda commands such as ammt and amtape - does amcheck with options for server and client checks give reasonable reports -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist and tape order
On Sat, Jan 25, 2003 at 03:16:19PM -0500, Jon LaBadie wrote: > > Are there undesired consequences to reordering the tapelist now, > placing the example tape 4 between tapes 3 & 5 with the same date as tape 5? It you change the datestamp of a tape then amanda will lose all informations of what's on that tape. 'amadmin find' will report that it doesn't find the log for that tape. amrecover will not be able to recover from that tape. The log files 'log..' will be erased. The index files for the dump on that tape will be erased. You can change the datestamp, but do it at the appropriate time, just before you want to reuse that tape. 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: tapelist and tape order
>Amazing but true, occasionally I fail to read my reports each morning``sla>p'' >(that was me slapping myself in the face). :-) :-) >Are there undesired consequences to reordering the tapelist now, >placing the example tape 4 between tapes 3 & 5 with the same date as tape 5? I don't think so. I don't thing anything (such as amrecover and friends) other than the "which one is next" code look at the tapelist file. You should be able to go ahead and reorder things now and they should sink down to the bottom of the file, at which point "the right thing" will happen and order will be re-established. Note, however, my *strong* suggestion that you make a copy of the file first. If I'm wrong, I can still say "I told you so" :-). >Jon H. LaBadie John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tapelist and tape order
On Sat, Jan 25, 2003 at 10:48:19AM -0500, John R. Jackson wrote: > >What (if anything) should I do to correct the order? > > Here's what I've done in the past (not that I've ever gotten things > scrambled, of course :-): > > * Wait until your Amanda report says an "out of order" tape is going > to be skipped. In your case: > > These dumps were to tape DailySet1-03. > ... > The next tape Amanda expects to use is: DailySet1-05. > > So DailySet1-04 is being bypassed here. > [[ Editing guide snipped ]] John, Amazing but true, occasionally I fail to read my reports each morning``slap'' (that was me slapping myself in the face). Are there undesired consequences to reordering the tapelist now, placing the example tape 4 between tapes 3 & 5 with the same date as tape 5? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist and tape order
>What (if anything) should I do to correct the order? As others have mentioned, the labels don't really matter except to keep us humans sane (not that that's not important :-). Amanda isn't paying any attention to the actual "text". If you want to improve your sanity :-), the first thing to understand is how Amanda processes the tapelist file. Assuming you have enough "reuse" tapes in the file to fulfill tapecycle, Amanda looks for the oldest tape (lowest datestamp). If there are multiple tapes with the same datestamp, it will pick the one that appears last in the file. There isn't any (easy) way to manipulate this file with Amanda tools. But it's text, so your favorite editor will do fine. Here's what I've done in the past (not that I've ever gotten things scrambled, of course :-): * Wait until your Amanda report says an "out of order" tape is going to be skipped. In your case: These dumps were to tape DailySet1-03. ... The next tape Amanda expects to use is: DailySet1-05. So DailySet1-04 is being bypassed here. Note that another way to see the tape order is: # amadmin DailySet1 tape The next Amanda run should go onto tape DailySet1-05 or a new tape. * Make a copy of the tapelist file just in case your editor (or fingers :-) go wacky. * Bring up the editor. The first line of the file should reference the tape just written (DailySet1-03). The last line of the file should be the next tape to write (DailySet1-05). For instance: 20030116 DailySet1-03 reuse ... 20021230 DailySet1-05 reuse * Find the line for the "missing" tape (DailySet1-04) and move it to the end of the file. Change the datestamp field of the new last line (DailySet1-04) to match the value of the previous last line (DailySet1-05). For instance: 20030116 DailySet1-03 reuse ... 20021230 DailySet1-05 reuse 20021230 DailySet1-04 reuse * Write the file. Make sure it is still owned by your Amanda user and writable by it. "amcheck -l " can help here. * See if Amanda agrees with you about the next tape: # amadmin DailySet1 tape The next Amanda run should go onto tape DailySet1-04 or a new tape. One thing you need to be **very** careful of. When you shift a tape like this, it creates a "hole" in your backups until you get through a full cycle again. For instance, if your dumpcycle is 7 days and DailySet1-04 is within 7 days of the top of the tapelist file, putting it at the end (and overwriting it on the next run) may make it impossible to do a full restore if it contained the latest level. >dk John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tapelist and tape order
On Sunday 19 January 2003 06:46, Christoph Scheeder wrote: >Sure there is a simple solution to this: >edit your amanda.conf, lower tapecycle and dumpcycle to 5 and >next time when amanda tells you it expects tape DailySet1-05, >she will happily write to tape DailySet1-04, as it's old enough >to be overwritten. Same for tape DailySet1-07 a few days later. >after that increase your tape and Dumpcycle to the old values > again and you are done. >Christoph Neat idea. Assumes one can walk and chew gum at the same time, but doable. Shows what can happen when full brain power is applied. Thanks Christoph. >Gene Heskett schrieb: >> On Friday 17 January 2003 21:13, DK Smith wrote: >>>I finally determined why my tape order is not what I expected. >>> (by looking at the tapelist file). I do not recall why my tape >>> order managed to get into this state... When I originally set >>> things up, *i thought* the tapes were in order... >>> >>>I was seeing... >>> >>>## >>> >>>Tues: DailySet1 AMANDA MAIL REPORT FOR January 14, 2003 >>> >>>These dumps were to tape DailySet1-01. >>>The next tape Amanda expects to use is: DailySet1-02. >>> >>>## >>> >>>Wed: DailySet1 AMANDA MAIL REPORT FOR January 15, 2003 >>> >>>These dumps were to tape DailySet1-02. >>>The next tape Amanda expects to use is: DailySet1-03. >>> >>>## >>> >>>Thur: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 >>> >>>These dumps were to tape DailySet1-03. >>>*** A TAPE ERROR OCCURRED: [[writing filemark: I/O error]]. >>>Some dumps may have been left in the holding disk. >>>Run amflush to flush them to tape. >>>The next tape Amanda expects to use is: DailySet1-05. >>> >>>## >>> >>>Fri: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 >>> >>>These dumps were to tape DailySet1-05. >>>The next tape Amanda expects to use is: DailySet1-06. >>> >>>## >>> >>> >>>After (finally) taking a look at my tapelist in the >>> configuration, I realized the reason for change in order of use >>> that I observed: >>> >>>20030117 DailySet1-06 reuse >>>20030116 DailySet1-05 reuse >>>20030116 DailySet1-03 reuse >>>20030116 DailySet1-02 reuse >>>20030114 DailySet1-01 reuse >>>20030113 DailySet1-15 reuse >>>20030110 DailySet1-07 reuse >>>20030109 DailySet1-04 reuse >>>20030108 DailySet1-16 reuse >>>20030107 DailySet1-14 reuse >>>20030106 DailySet1-13 reuse >>>20030103 DailySet1-12 reuse >>>20030102 DailySet1-11 reuse >>>20030101 DailySet1-10 reuse >>>20021231 DailySet1-09 reuse >>>20021230 DailySet1-08 reuse >>> >>> >>> >>> >>>What (if anything) should I do to correct the order? >>> >>>Can anyone suggest an elegant way to correct the order by using >>>interfaces supplied with AMANDA? (as opposed to starting over >>> and re-labelling a whole new magazine of tapes, as one option) >> >> Not that I've ran into. I had one tape out of order for nearly >> a year before I had to do a clean install for other reasons. As >> long as you know about it, I'd just put them into whatever >> storage you use in the reverse of the order shown above. >> >> I'm told that if you try to edit the above file to restore the >> useage order, that the backups may be scheduled odd ball or >> something because the dates on the index files won't then match >> the order of the tapes. That would eventually fix itself, but >> it might take a tapecycles worth of runs to square it all away >> again. Thats what somebody here said, so I never tried it. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
Re: tapelist and tape order
Sure there is a simple solution to this: edit your amanda.conf, lower tapecycle and dumpcycle to 5 and next time when amanda tells you it expects tape DailySet1-05, she will happily write to tape DailySet1-04, as it's old enough to be overwritten. Same for tape DailySet1-07 a few days later. after that increase your tape and Dumpcycle to the old values again and you are done. Christoph Gene Heskett schrieb: On Friday 17 January 2003 21:13, DK Smith wrote: I finally determined why my tape order is not what I expected. (by looking at the tapelist file). I do not recall why my tape order managed to get into this state... When I originally set things up, *i thought* the tapes were in order... I was seeing... ## Tues: DailySet1 AMANDA MAIL REPORT FOR January 14, 2003 These dumps were to tape DailySet1-01. The next tape Amanda expects to use is: DailySet1-02. ## Wed: DailySet1 AMANDA MAIL REPORT FOR January 15, 2003 These dumps were to tape DailySet1-02. The next tape Amanda expects to use is: DailySet1-03. ## Thur: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 These dumps were to tape DailySet1-03. *** A TAPE ERROR OCCURRED: [[writing filemark: I/O error]]. Some dumps may have been left in the holding disk. Run amflush to flush them to tape. The next tape Amanda expects to use is: DailySet1-05. ## Fri: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 These dumps were to tape DailySet1-05. The next tape Amanda expects to use is: DailySet1-06. ## After (finally) taking a look at my tapelist in the configuration, I realized the reason for change in order of use that I observed: 20030117 DailySet1-06 reuse 20030116 DailySet1-05 reuse 20030116 DailySet1-03 reuse 20030116 DailySet1-02 reuse 20030114 DailySet1-01 reuse 20030113 DailySet1-15 reuse 20030110 DailySet1-07 reuse 20030109 DailySet1-04 reuse 20030108 DailySet1-16 reuse 20030107 DailySet1-14 reuse 20030106 DailySet1-13 reuse 20030103 DailySet1-12 reuse 20030102 DailySet1-11 reuse 20030101 DailySet1-10 reuse 20021231 DailySet1-09 reuse 20021230 DailySet1-08 reuse What (if anything) should I do to correct the order? Can anyone suggest an elegant way to correct the order by using interfaces supplied with AMANDA? (as opposed to starting over and re-labelling a whole new magazine of tapes, as one option) Not that I've ran into. I had one tape out of order for nearly a year before I had to do a clean install for other reasons. As long as you know about it, I'd just put them into whatever storage you use in the reverse of the order shown above. I'm told that if you try to edit the above file to restore the useage order, that the backups may be scheduled odd ball or something because the dates on the index files won't then match the order of the tapes. That would eventually fix itself, but it might take a tapecycles worth of runs to square it all away again. Thats what somebody here said, so I never tried it.
Re: tapelist and tape order
On Friday 17 January 2003 21:13, DK Smith wrote: >I finally determined why my tape order is not what I expected. (by > looking at the tapelist file). I do not recall why my tape order > managed to get into this state... When I originally set things > up, *i thought* the tapes were in order... > >I was seeing... > >## > >Tues: DailySet1 AMANDA MAIL REPORT FOR January 14, 2003 > >These dumps were to tape DailySet1-01. >The next tape Amanda expects to use is: DailySet1-02. > >## > >Wed: DailySet1 AMANDA MAIL REPORT FOR January 15, 2003 > >These dumps were to tape DailySet1-02. >The next tape Amanda expects to use is: DailySet1-03. > >## > >Thur: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 > >These dumps were to tape DailySet1-03. >*** A TAPE ERROR OCCURRED: [[writing filemark: I/O error]]. >Some dumps may have been left in the holding disk. >Run amflush to flush them to tape. >The next tape Amanda expects to use is: DailySet1-05. > >## > >Fri: DailySet1 AMANDA MAIL REPORT FOR January 16, 2003 > >These dumps were to tape DailySet1-05. >The next tape Amanda expects to use is: DailySet1-06. > >## > > >After (finally) taking a look at my tapelist in the configuration, > I realized the reason for change in order of use that I observed: > >20030117 DailySet1-06 reuse >20030116 DailySet1-05 reuse >20030116 DailySet1-03 reuse >20030116 DailySet1-02 reuse >20030114 DailySet1-01 reuse >20030113 DailySet1-15 reuse >20030110 DailySet1-07 reuse >20030109 DailySet1-04 reuse >20030108 DailySet1-16 reuse >20030107 DailySet1-14 reuse >20030106 DailySet1-13 reuse >20030103 DailySet1-12 reuse >20030102 DailySet1-11 reuse >20030101 DailySet1-10 reuse >20021231 DailySet1-09 reuse >20021230 DailySet1-08 reuse > > > > >What (if anything) should I do to correct the order? > >Can anyone suggest an elegant way to correct the order by using > interfaces supplied with AMANDA? (as opposed to starting over and > re-labelling a whole new magazine of tapes, as one option) Not that I've ran into. I had one tape out of order for nearly a year before I had to do a clean install for other reasons. As long as you know about it, I'd just put them into whatever storage you use in the reverse of the order shown above. I'm told that if you try to edit the above file to restore the useage order, that the backups may be scheduled odd ball or something because the dates on the index files won't then match the order of the tapes. That would eventually fix itself, but it might take a tapecycles worth of runs to square it all away again. Thats what somebody here said, so I never tried it. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
Re: tapelist and tape order
On Fri, Jan 17, 2003 at 06:13:31PM -0800, DK Smith wrote: > > I finally determined why my tape order is not what I expected. (by looking at the >tapelist file). I do not recall why my tape order managed to get into this state... >When I originally set things up, *i thought* the tapes were in order... > > > What (if anything) should I do to correct the order? > > Can anyone suggest an elegant way to correct the order by using interfaces supplied >with AMANDA? (as opposed to starting over and re-labelling a whole new magazine of >tapes, as one option) > You probably realize that they are in order -- as far as amanda is concerned. Amanda does not care about the labels. You could call them huey, dewey, and louie with a labelstr of '^.*$'. So the problem is you, or your perception of order. Maybe others have an elegant reordering tip. I've only done crude reordering. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist query
On Wed, Jul 17, 2002 at 03:33:54AM +0100, Mark Cooke wrote: > Hi, > > I've been pre labeling some tapes to do backups for 6 day cycle, > with a tape cycle of 7 tapes (I'm currently testing at present). > > cut > > dumpcycle 6 days > runspercycle 6 > tapecycle 7 tapes > > cut > Ive just pre labeled all the tapes using: > > /usr/sbin/amlabel DailySet DailySet-01 ... and so forth thru to 07 > > I have just check /etc/amanda/DailySet and noted two files: > > tapelist > tapelist.amlabel > > the file called: tapelist lists all 7 tapes, but the file called > 'tapelist.amlabel' only lists 6. > amlabel copies the current tapelist to tapelist.amlabel before creating an updated tapelist. Not used otherwise. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Wed, 5 Jun 2002, Jon LaBadie wrote: > On Wed, Jun 05, 2002 at 12:53:00PM -0500, Dave Sherohman wrote: > > > > I'm on slightly less shaky ground, as I increased my tapecycle a couple > > months ago, but my recollection is that amanda refused to overwrite used > > tapes until all new tapes had been used. I know that it requested a > > new tape each time until all new tapes had been used. > > Agreed if you are increasing the tapecycle. Amanda refuses to use any > old tapes until at least tapecycle number of tapes are in use. > > But ahall, the OP, was changing tape types, ait-1 to ait-2 if I recall. > Thus the new tapes were not for an increased tapecycle. They were > simply unused and labeled with the same label as the previous tapes. So the question is what happens in tapelist to tape labels that are "relabeled". Will they end up at the top with the date stamp zero? If so, then they would appear just like newly added tapes, wouldn't they? -- Ulrik Sandberg
Re: tapelist issue?
On Wed, Jun 05, 2002 at 12:53:00PM -0500, Dave Sherohman wrote: > On Wed, Jun 05, 2002 at 01:42:23PM -0400, Jon LaBadie wrote: > > I'm on really shakey ground here, meaning I've never tested it, but I > > don't think amanda goes looking for new tapes anywhere in the list. > > I'm on slightly less shaky ground, as I increased my tapecycle a couple > months ago, but my recollection is that amanda refused to overwrite used > tapes until all new tapes had been used. I know that it requested a > new tape each time until all new tapes had been used. > > Working around this to get my tapes back into the right order is how I > became familiar with tapelist... Agreed if you are increasing the tapecycle. Amanda refuses to use any old tapes until at least tapecycle number of tapes are in use. But ahall, the OP, was changing tape types, ait-1 to ait-2 if I recall. Thus the new tapes were not for an increased tapecycle. They were simply unused and labeled with the same label as the previous tapes. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Wed, Jun 05, 2002 at 01:42:23PM -0400, Jon LaBadie wrote: > I'm on really shakey ground here, meaning I've never tested it, but I > don't think amanda goes looking for new tapes anywhere in the list. I'm on slightly less shaky ground, as I increased my tapecycle a couple months ago, but my recollection is that amanda refused to overwrite used tapes until all new tapes had been used. I know that it requested a new tape each time until all new tapes had been used. Working around this to get my tapes back into the right order is how I became familiar with tapelist...
Re: tapelist issue?
On Wed, Jun 05, 2002 at 11:01:43AM -0500, Dave Sherohman wrote: > On Tue, Jun 04, 2002 at 11:45:22PM -0400, Jon LaBadie wrote: > > What is the purpose of "dating" the tape. > > To prevent it from being immediately requested. > > > I presume 0 indicates not yet used. > > Doesn't amanda accept a "new" tape at anytime? > > Yes. However, in the example presented, the new tape was #6 and we > wanted to use #4 next. Since amanda doesn't like reusing old tapes when > new tapes are available, #6 needs to be dated manually so that #4 and > #5 will be used first. I'm on really shakey ground here, meaning I've never tested it, but I don't think amanda goes looking for new tapes anywhere in the list. I think it looks at the tape available in the drive, then checks whether it is a valid tape to use. Then the date comes into play. That is "date" or "new" comes into play. If I'm correct, then the new tapes position in the list won't matter as long as amanda sees the tapes in the correct order in the drive itself. Again, if I'm correct (and I'm not certain), the advantage of dating the new tapes is to prevent accidentally using them out of order. But as long as you present #4 and #5 to amanda first, it won't reject them and go looking for that #6 just because it is new. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Tue, Jun 04, 2002 at 11:45:22PM -0400, Jon LaBadie wrote: > What is the purpose of "dating" the tape. To prevent it from being immediately requested. > I presume 0 indicates not yet used. > Doesn't amanda accept a "new" tape at anytime? Yes. However, in the example presented, the new tape was #6 and we wanted to use #4 next. Since amanda doesn't like reusing old tapes when new tapes are available, #6 needs to be dated manually so that #4 and #5 will be used first.
Re: tapelist issue?
On Wednesday 05 June 2002 04:08 am, Ulrik Sandberg wrote:
>On Tue, 4 Jun 2002, Jon LaBadie wrote:
>> On Wed, Jun 05, 2002 at 12:35:31AM +0200, Ulrik Sandberg wrote:
>> ...
>>
>> > Then, fix time stamp so that the new tape has the same time
>> > stamp as the previous entry ('previous' meaning 'below'):
>> >
>> > 20020602 DailySet1-003 reuse
>> > 20020601 DailySet1-002 reuse
>> > 20020531 DailySet1-001 reuse
>> > 20020530 DailySet1-006 reuse <-- time stamp now same as for
>> > 005 20020530 DailySet1-005 reuse
>> > 20020529 DailySet1-004 reuse <-- this tape is due
>>
>> What is the purpose of "dating" the tape.
>> I presume 0 indicates not yet used.
>> Doesn't amanda accept a "new" tape at anytime?
>
>Perhaps. I just quote from
> http://www.backupcentral.com/amanda-18.html :
>
>"Set the date stamp on the new tapes to the same as the previous
> tape, e.g. make them the same for Daily-099 and Daily-100."
>
>So if 005 did have zero, the new 006 should have zero as well. In
> our case, 005 didn't have zero, but 20020530.
AIUI that date string is the date the tape was last used, and helps
amrecover to locate its copy of the tapes index on the server in
the event you needed to recover. It also tells amdump and
amandaidx which index trees to remove from the system when the tape
is being re-used. This information is also on the tape in the
first block if you dd the first block and look at it. But I don't
think the index is removed based on the tape header, rather from
the tapelist entry instead.
John, can you clarify this?
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
98.96+% setiathome rank, not too shabby for a hillbilly
Re: tapelist issue?
On Tue, 4 Jun 2002, Jon LaBadie wrote:
> On Wed, Jun 05, 2002 at 12:35:31AM +0200, Ulrik Sandberg wrote:
> ...
> > Then, fix time stamp so that the new tape has the same time stamp as the
> > previous entry ('previous' meaning 'below'):
> >
> > 20020602 DailySet1-003 reuse
> > 20020601 DailySet1-002 reuse
> > 20020531 DailySet1-001 reuse
> > 20020530 DailySet1-006 reuse <-- time stamp now same as for 005
> > 20020530 DailySet1-005 reuse
> > 20020529 DailySet1-004 reuse <-- this tape is due
>
> What is the purpose of "dating" the tape.
> I presume 0 indicates not yet used.
> Doesn't amanda accept a "new" tape at anytime?
Perhaps. I just quote from http://www.backupcentral.com/amanda-18.html :
"Set the date stamp on the new tapes to the same as the previous tape,
e.g. make them the same for Daily-099 and Daily-100."
So if 005 did have zero, the new 006 should have zero as well. In our
case, 005 didn't have zero, but 20020530.
--
Ulrik Sandberg
Re: tapelist issue?
On Wed, Jun 05, 2002 at 12:35:31AM +0200, Ulrik Sandberg wrote:
> On Tue, 4 Jun 2002 [EMAIL PROTECTED] wrote:
>
> > > Have you recently edited the tapelist file or changed the number of
> > > tapes in use? Rotated a tape into or out of circulation?
> >
> > Yes. I have been replacing my AIT-1 tapes with AIT-2. I have been
> > relabling them with the same label as the one I am removing. I did not
> > see how this could have caused an error.
>
> I will here give a somewhat verbose explanation about fixing up tapelist.
> Perhaps it will shed some light on your problem.
>
...
> How do you fix this up? Simple. Reorder and set time stamp. First,
> reorder:
>
> 20020602 DailySet1-003 reuse
> 20020601 DailySet1-002 reuse
> 20020531 DailySet1-001 reuse
> 0 DailySet1-006 reuse <-- new tape now in correct position
> 20020530 DailySet1-005 reuse
> 20020529 DailySet1-004 reuse <-- this tape is due
>
> Then, fix time stamp so that the new tape has the same time stamp as the
> previous entry ('previous' meaning 'below'):
>
> 20020602 DailySet1-003 reuse
> 20020601 DailySet1-002 reuse
> 20020531 DailySet1-001 reuse
> 20020530 DailySet1-006 reuse <-- time stamp now same as for 005
> 20020530 DailySet1-005 reuse
> 20020529 DailySet1-004 reuse <-- this tape is due
What is the purpose of "dating" the tape.
I presume 0 indicates not yet used.
Doesn't amanda accept a "new" tape at anytime?
jon
--
Jon H. LaBadie [EMAIL PROTECTED]
JG Computing
4455 Province Line Road(609) 252-0159
Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: tapelist issue?
On Tue, 4 Jun 2002 [EMAIL PROTECTED] wrote:
> > Have you recently edited the tapelist file or changed the number of
> > tapes in use? Rotated a tape into or out of circulation?
>
> Yes. I have been replacing my AIT-1 tapes with AIT-2. I have been
> relabling them with the same label as the one I am removing. I did not
> see how this could have caused an error.
I will here give a somewhat verbose explanation about fixing up tapelist.
Perhaps it will shed some light on your problem.
***
Let's say you have five tapes. It's time for tape 004, so the tapelist
looks like this:
20020602 DailySet1-003 reuse
20020601 DailySet1-002 reuse
20020531 DailySet1-001 reuse
20020530 DailySet1-005 reuse
20020529 DailySet1-004 reuse <-- this tape is due
You then add a tape and label it number 006. The new tape ends up at the
top. The tapelist now looks like this:
0 DailySet1-006 reuse <-- newly added tape
20020602 DailySet1-003 reuse
20020601 DailySet1-002 reuse
20020531 DailySet1-001 reuse
20020530 DailySet1-005 reuse
20020529 DailySet1-004 reuse <-- this tape is due
Will this cause problems? Well, the tapes will be requested in order 001,
002, 003, 006, 004, 005, etc. Non-intuitive, right?
^
How do you fix this up? Simple. Reorder and set time stamp. First,
reorder:
20020602 DailySet1-003 reuse
20020601 DailySet1-002 reuse
20020531 DailySet1-001 reuse
0 DailySet1-006 reuse <-- new tape now in correct position
20020530 DailySet1-005 reuse
20020529 DailySet1-004 reuse <-- this tape is due
Then, fix time stamp so that the new tape has the same time stamp as the
previous entry ('previous' meaning 'below'):
20020602 DailySet1-003 reuse
20020601 DailySet1-002 reuse
20020531 DailySet1-001 reuse
20020530 DailySet1-006 reuse <-- time stamp now same as for 005
20020530 DailySet1-005 reuse
20020529 DailySet1-004 reuse <-- this tape is due
Voila.
--
Ulrik Sandberg
Re: tapelist issue?
> > 3) any idea how this happened? > > Have you recently edited the tapelist file or changed the number of > tapes in use? Rotated a tape into or out of circulation? > Yes. I have been replacing my AIT-1 tapes with AIT-2. I have been relabling them with the same label as the one I am removing. I did not see how this could have caused an error. Andrew
Re: tapelist issue?
On Tue, Jun 04, 2002 at 10:29:55AM -0400, [EMAIL PROTECTED] wrote: > 1) why does amanda want to use a tape in a cycle when two tapes past said > tape are already used? Because it has the oldest data on it. The numbers on the tape labels mean nothing to amanda, it just asks for whatever is (according to tapelist) oldest. > 2) how do I get amanda to use the correct tape in my cycle. Edit your tapelist file (/etc/amanda/Daily/tapelist for my system, probably somewhere else on yours), find the tape that you want to use next, and change the date associated with the tape you want to move. The order of the lines in the file is normally ignored, but if there are two tapes with the same date, the one closer to the bottom of the list is considered to be older. > 3) any idea how this happened? Have you recently edited the tapelist file or changed the number of tapes in use? Rotated a tape into or out of circulation?
Re: Tapelist
Sorry, I just found my question in the FAQ. Please ignore and forgive me for asking before reading! Thanks Jan Jan Boshoff wrote: > Hi Everyone > > Again a general question. I added some tapes to our cycle, but in such > a way that my tapelist looks as follows: > > 20020305 Weekly1 reuse > 20020302 Weekly6 reuse > 20020228 Weekly5 reuse > 20020226 Weekly4 reuse > 20020223 Weekly8 reuse > 20020221 Weekly7 reuse > 20020218 Weekly3 reuse > 20020216 Weekly2 reuse > > So you see I use tapes in the order 1,2,3,7,8,4,5,6 > > I'd like this to be 1,2,3,4,5,6,7,8, for the sake of the guy taking over > from me not being confused, and also for my left-brain mentality to not > crinch every time amanda asks for tape 7 after tape 3. :) > > Any ideas? > > Another thing, if I'd now like to add a tape, Weekly9, after Weekly8, is > it okay to update amanda.conf today, and rigging the tapelist file as > follows: > > 20020305 Weekly1 reuse > 20020302 Weekly6 reuse > 20020228 Weekly5 reuse > 20020226 Weekly4 reuse > 20020224 Weekly9 reuse <--- Added this entry with fictitious date > 20020223 Weekly8 reuse > 20020221 Weekly7 reuse > 20020218 Weekly3 reuse > 20020216 Weekly2 reuse > > Thanks! > Jan Boshoff
Re: Tapelist
I also am confused by the dumpcycle, runspercycle, tapecycle values. I have a ten tape change with 8 tapes, currently. I want to rotate tapes once a month. I tried 'dumpcycle 1 month' but Amanda doesn't seem to understand that. If I use 'dumpcycle 30 days' it's much harder to remember when the tapes need to be changed. However, if I go with the 30 days, would I then do this? dumpcycle 30 days runspercycle 7 tapecycle 8 tapes And then setup cron to call amdump on seven days throughout the month? If I added the last few tapes so the changer is full at ten, then would I use this? dumpcycle 30 days runspercycle 9 tapecycle 10 tapes And then setup cron to call amdump on nine days throughout the month? Thanks, -- Jeremy Wadsack Wadsack-Allen Digital Group
Re: Tapelist
> clem wrote: > > Hi, > > I would like to know the perfect settings for my Amanda config as I > seem to be having problems with tape rotations. > > I have 21 tapes for a 3 weeks worth of backup before I start to rotate > them. Furthermore I have 3 extra tapes. What figures should I be > putting in my Amanda config file so that I preserve the 3 weeks backup > before I start to overwrite it. dumpcycle 21 days runspercycle 21 tapecycle 24 tapes
Re: tapelist
>... I don't know what happened but some tape are not in >proper order (sequence). ... But I would like to know >if it is possible to put in correct order all my tapes ... I wrote a lengthy description of this about a month and a half ago (early March and again mid-March). Look in the E-mail archives for Subject "Add more tapes on the backup cycle" or "Changing the order in which tapes are used". >Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: tapelist
It will take a while, but you can straighten your tape order out. When amcheck says it's about to use a tape that is out of sequence, use 'amadmin CONFIG no-reuse TAPENAME' to take it out of the rotation. Make a note of which tapes you take out of rotation. When the tape cycle comes around to where you want that tape, use 'amadmin CONFIG reuse TAPENAME' to bring it back. amcheck should then show it as the next tape to be used. -Original Message- From: Sandra Panesso [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 26, 2001 1:38 PM To: [EMAIL PROTECTED] Subject: tapelist Hi everybody: one month ago, I changed my tape server for Hp Surestore 24X6 so I use amlabel force and t relabel my new tapes, in this way I be able to use my old configuration (25 tapes, runtapes, etc) but I have problems with my tapelist because I don't know what happened but some tape are not in proper order (sequence). I know that's matter for amanda. But I would like to know if it is possible to put in correct order all my tapes because something is confusing when i going to put my six tapes at the same time and I use the human sequence. This my tapelist now 20010321 miro_daily-10 reuse 20010320 miro_daily-9 reuse 20010319 miro_daily-3 reuse -- out the order 20010319 miro_daily-8 reuse 20010317 miro_daily-7 reuse 20010316 miro_daily-6 reuse 20010315 miro_daily-5 reuse 20010314 miro_daily-4 reuse 20010314 miro_daily-2 reuse 20010312 miro_daily-1 reuse 20010312 miro_daily-25 reuse 20010310 miro_daily-24 reuse 20010309 miro_daily-18 reuse - out the order 20010308 miro_daily-21 reuseout the order 20010307 miro_daily-23 reuse 20010306 miro_daily-22 reuse 20010305 miro_daily-20 reuse 20010305 miro_daily-19 reuse 20010302 miro_daily-17 reuse 20010301 miro_daily-16 reuse 20010228 miro_daily-15 reuse 20010227 miro_daily-14 reuse 20010227 miro_daily-13 reuse Any suggestion? thanks to everybody for your help. Sandra
Re: Tapelist
>one last question (promise) ... Oh, sure. How many times have we heard **that** line? :-) :-) :-) >... how does amanda figure out what to dump and when to >dump? I mean what is the algorithm? I haven't been able to figure this >out and yet it must be documented somewhere. There are really two questions here, and I'm not sure which one you're asking. My apologies if the first is obvious to you and you really wanted the answer to the second. One question is "which files are backed up when I dump disk X on client Y". That algorithm is not part of Amanda, it's part of whatever dump program you're using. With the dump programs Amanda currently supports, it's based on comparing the last modification/change time on each item with some reference and doing everything that appears to be new or altered. The reference is called a "level". Level 0 is special and means "dump everything". Level 'N' means dump everything new or changed since the last level less than 'N'. For instance, a level 1 will compare against level 0. A level 2 will compare against either a level 1 or level 0, depending on which was done most recently. The next question is "what level does Amanda use". To make that decision, Amanda (planner) first asks how big dump images will be for the levels it might end up using. It always asks for the size of a level 0 (full dump). It usually asks for the size of the same level that it ran last time. And it may ask for the size of the next higher level based on the "bump*" parameters that control how often it is allowed to go up a level. Then it analyzes all the estimates it gets back. If it is time for a level 0 (see below), that's what is picked. Otherwise it picks one of the two possible incremental levels (the same as last time and the next level) based on whether it is time to bump (bumpdays) and whether it would save enough space by going to the next level (bumpsize and bumpmult). When to do the next level 0 is based on several things: * "amadmin force" forces a level 0 * strategies "nofull" and "incronly" never (in theory) do a full * strategy "noinc" always does a full * new disks always do a full * when the last full was done plus dumpcycle determines when to do the next full * and more below At this point, planner has what is called the "initial schedule" (you can read along with all of this in an amdump. file). Next, planner compares the total size to dump against the tape size and delays dumps to get it to fit: * any dumps are larger than a tape are deferred since they will never fit * the lowest priority full dumps are demoted to incrementals * incremental dumps are deferred until the next run Next, planner promotes some incrementals to full dumps if there is room. The goal is to balance the size of the level 0 dumps done during every run. At this point, the final schedule is set and it is passed to driver to process. The only thing that can change what happens after this is if there is a tape error and Amanda drops into "degraded mode" where it may do an incremental rather than the requested full dump, depending on the "reserve" parameter. It may also start skipping dumps if the holding disk fills. There is more about this in the papers at ftp.amanda.org. And the best place, of course, is the planner.c code itself (which is what I just read through and translated to the above). >Ross John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Tapelist
On Thu, 08 Mar 2001 17:18:37 -0500 "John R. Jackson" <[EMAIL PROTECTED]> wrote: > >In other backup systems I've used, I have always kept certain level 0's > >out of the rotation so's that I could alway go back quite a bit if > >necessary. > > That's harder to do with Amanda because when a level 0 is done is not > deterministic (well, it is, but it's much more complicated than "it's > Thursday"). > > >Can I add as many new ones as I want then? ... > > Yup. > > >And yet there are over 100 tapes in the tapelist file! > > That just means the tapecycle value didn't get updated when more tapes > were added. If tapelist has less entries than tapecycle, Amanda will > ask for new tapes. But if it has more, Amanda just cycles through them > and pays no attention to tapecycle. > > Tapecycle is used for some other things (how long to keep some log files). > > >Do these figures mean that a level 0 must be done on each file system > >at least once every 4 weeks? > > Yes. But notice what you said. "At least", not "Every". In other words, > it might only be a couple of days between doing level 0's or it might be > the full four weeks. It's all up to how Amanda wants to balance the load. one last question (promise) and this is what I've been trying to figure out all along, is how does amanda figure out what to dump and when to dump? I mean what is the algorithm? I haven't been able to figure this out and yet it must be documented somewhere. Thanks again, Ross > > >And I guess if all the tapes are being reused then these backups are > >just for emergencies and if you wanted to look at something from say 3 > >years ago, you couldn't. > > Correct, without taking other action to save that data. > > >Ross > > John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED]
Re: Tapelist
>In other backup systems I've used, I have always kept certain level 0's >out of the rotation so's that I could alway go back quite a bit if >necessary. That's harder to do with Amanda because when a level 0 is done is not deterministic (well, it is, but it's much more complicated than "it's Thursday"). >Can I add as many new ones as I want then? ... Yup. >And yet there are over 100 tapes in the tapelist file! That just means the tapecycle value didn't get updated when more tapes were added. If tapelist has less entries than tapecycle, Amanda will ask for new tapes. But if it has more, Amanda just cycles through them and pays no attention to tapecycle. Tapecycle is used for some other things (how long to keep some log files). >Do these figures mean that a level 0 must be done on each file system >at least once every 4 weeks? Yes. But notice what you said. "At least", not "Every". In other words, it might only be a couple of days between doing level 0's or it might be the full four weeks. It's all up to how Amanda wants to balance the load. >And I guess if all the tapes are being reused then these backups are >just for emergencies and if you wanted to look at something from say 3 >years ago, you couldn't. Correct, without taking other action to save that data. >Ross John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Tapelist
On Mar 8, 2001, Ross Macintyre <[EMAIL PROTECTED]> wrote:
> I think it would be a good idea to keep all
> the tapes in the tapelist for recycling but on top of this Iwould like
> to do a one-off level 0 of everything and keep that aside.
> Is there an easy way to do this?
Yep. http://amanda.sourceforge.net/cgi-bin/fom?file=30
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Tapelist
On Tue, 06 Mar 2001 16:18:02 -0500 "John R. Jackson" <[EMAIL PROTECTED]> wrote: > >so I moved tape1_131 to the bottom, expecting amanda to look for > >tape1_131. It wasn't a big deal but when I ran amflush(the previous > >night's had failed) the message was that it expected tape1_132, but it > >still ran. So how did it know to expect tape1_132? > > The primary key is the date string, not the VSN. Amanda doesn't care if > you label your tapes "larry", "moe" and "curly", so VSN is not a valid > sort criteria. > > The secondary sort key is the position within the file. So to "move" > a tape back into what a human wants for order, you need to send it to > the bottom and change the datestring to match the previous line. > > You can test this with "amadmin tape" which will show you the > next tape(s) expected. thanks for this information - this is very helpful > > >The other question I have is this: > >all the lines in the file tapelist say 'reuse'. So how are we expected > >to know which tapes to keep? > > What do you mean by "which tapes to keep"? In other backup systems I've used, I have always kept certain level 0's out of the rotation so's that I could alway go back quite a bit if necessary. > > The "reuse" flag tells Amanda it may use this tape again when it is > the next one in the list. You can tell Amanda to not reuse a tape with > "amadmin no-reuse ...". When Amanda looks at that tape > it will skip over it. > > Note that if you mark some tapes as "no-reuse", Amanda will ask for "new" > tapes until there are "tapecycle" reusable ones again. Can I add as many new ones as I want then? At the moment the configuration is like this: dumpcycle 4 weeks # the number of days in the normal dump cycle runspercycle 20 # the number of amdump runs in dumpcycle days # (4 weeks * 5 amdump runs per week -- just weekdays) tapecycle 40 tapes # the number of tapes in rotation # 4 weeks (dumpcycle) times 5 tapes per week I didn't set these; the previous administrator did. And yet there are over 100 tapes in the tapelist file! Do these figures mean that a level 0 must be done on each file system at least once every 4 weeks? And I guess if all the tapes are being reused then these backups are just for emergencies and if you wanted to look at something from say 3 years ago, you couldn't. I guess what I'm saying is: I think it would be a good idea to keep all the tapes in the tapelist for recycling but on top of this Iwould like to do a one-off level 0 of everything and keep that aside. Is there an easy way to do this? Thanks agian for your help on this. Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED]
Re: Tapelist
>so I moved tape1_131 to the bottom, expecting amanda to look for >tape1_131. It wasn't a big deal but when I ran amflush(the previous >night's had failed) the message was that it expected tape1_132, but it >still ran. So how did it know to expect tape1_132? The primary key is the date string, not the VSN. Amanda doesn't care if you label your tapes "larry", "moe" and "curly", so VSN is not a valid sort criteria. The secondary sort key is the position within the file. So to "move" a tape back into what a human wants for order, you need to send it to the bottom and change the datestring to match the previous line. You can test this with "amadmin tape" which will show you the next tape(s) expected. >The other question I have is this: >all the lines in the file tapelist say 'reuse'. So how are we expected >to know which tapes to keep? What do you mean by "which tapes to keep"? The "reuse" flag tells Amanda it may use this tape again when it is the next one in the list. You can tell Amanda to not reuse a tape with "amadmin no-reuse ...". When Amanda looks at that tape it will skip over it. Note that if you mark some tapes as "no-reuse", Amanda will ask for "new" tapes until there are "tapecycle" reusable ones again. >Ross John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Tapelist
On 06 Mar 2001 06:47:28 -0300 Alexandre Oliva <[EMAIL PROTECTED]> wrote: > On Mar 6, 2001, Olivier Collet <[EMAIL PROTECTED]> wrote: > > > Can I just change it manually > > Yep > > > Also I would like to get ride of one tape called backup00 which was use > > for tests. Can I just wipe it out from this file ? > > Yep. Or amrmtape it. I'm in a similar situation. I've taken over someone else's installation of amanda and am just learning about it. I noticed that the tapes in the file tapelist were not in order; in particular the end of the list looked like this: tape1_134 tape1_133 tape1_131 tape1_132 so I moved tape1_131 to the bottom, expecting amanda to look for tape1_131. It wasn't a big deal but when I ran amflush(the previous night's had failed) the message was that it expected tape1_132, but it still ran. So how did it know to expect tape1_132? The other question I have is this: all the lines in the file tapelist say 'reuse'. So how are we expected to know which tapes to keep? Ross -- Ross Macintyre Heriot-Watt University [EMAIL PROTECTED]
Re: Tapelist
On Mar 6, 2001, Olivier Collet <[EMAIL PROTECTED]> wrote:
> Can I just change it manually
Yep
> Also I would like to get ride of one tape called backup00 which was use
> for tests. Can I just wipe it out from this file ?
Yep. Or amrmtape it.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: tapelist question
>... I changed my amanda >configuration to use the DDS3 tape and I would like to know if i can >relabel my new tapes or if I have to create another tapecycle. ... I'm not sure I fully understand your question, but if you just want to replace the existing tapes with the new ones, you can amlabel each just before it is to be used and Amanda should accept it. >when i ran >amcheck to see if it can recognize the tape, I saw something like >this "amcheck -server: slot 1 : date X" ... Amlabel writes "X" in the date field to indicate it is a new tape, so that's normal. >so i checked the tapelist >and i found that the tape that i relabeled had a zero on the date >field. ... And it creates a new tapelist entry with 0 as the date, which will cause this tape to be the first one requested (since it looks like it is the oldest) >Sandra John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: tapelist
On Feb 15, 2001, Monserrat Seisdedos Nuñez <[EMAIL PROTECTED]> wrote:
> i have 2 configuration files, 1 for weekly days and 1 for wednesday, there
> is just one tapelist in the first one directory.
This probably means the `tapelist' entry in the second directory's
amanda.conf says it should use the same tapelist file as the other
configuration.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
