Backup Central

Hi list,

My bacula configuration is not working the way I expect, I hope someone can
give me a pointer,

I want to make a full backup every day, regardless whether there's a different
tape or the same. I use a volume retentio period of 1 hour but when I want to
backup to the same tape I get the follwoing error:

Volume "DefaultVolume-0014" status is Used, but should be Append, Purged or
Recycle

This is the pool definition:

Pool {
Name = "Default"
PoolType = "Backup"
Recycle = "yes"
AutoPrune = "yes"
VolumeRetention = 1 hours
AcceptAnyVolume = "yes"
LabelFormat = "DefaultVolume-"
Use Volume Once = "yes"
}

the last records of "list media" :

| 30 | DefaultVolume-0013 | Used | 1,971,864,651 | 2 |
3,600 | 1 | 0 | 1 | DDS | 2007-06-05 17:06:45 |
| 31 | DefaultVolume-0014 | Used | 4,759,569,367 | 5 |
3,600 | 1 | 0 | 1 | DDS | 2007-06-07 18:06:57 |
| 32 | DefaultVolume-0015 | Used | 4,755,372,018 | 5 |
3,600 | 1 | 0 | 1 | DDS | 2007-06-07 16:05:15 |

The status of DefaultVolume-0014 is "used" but the backup finished more than
an hour ago, what am I doing wrong here?

Thanks, regards Chantal

Hi,

On 6/7/2007 7:26 PM, Chantal Rosmuller wrote:
Hi list,

My bacula configuration is not working the way I expect, I hope someone can
give me a pointer,

I guess I can...

I want to make a full backup every day, regardless whether there's a different
tape or the same. I use a volume retentio period of 1 hour but when I want to
backup to the same tape I get the follwoing error:

Volume "DefaultVolume-0014" status is Used, but should be Append, Purged or
Recycle

This shows that volumes are not recycled.

This is the pool definition:

Pool {
Name = "Default"
PoolType = "Backup"
Recycle = "yes"
AutoPrune = "yes"
VolumeRetention = 1 hours
AcceptAnyVolume = "yes"
LabelFormat = "DefaultVolume-"
Use Volume Once = "yes"
}

the last records of "list media" :
...
The status of DefaultVolume-0014 is "used" but the backup finished more than
an hour ago, what am I doing wrong here?

You've got
"Use Volume Once = <yes|no>
This directive if set to yes specifies that each volume is to be
used only once. This is most useful when the Media is a file and you
want a new file for each backup that is done. The default is no (i.e.
use volume any number of times). This directive will most likely be
phased out (deprecated), so you are recommended to use Maximum Volume
Jobs = 1 instead."

Set which effectively disables volume recycling. Remove that directive,
reload the configuration, update the existing volumes from the pool
resource, , and see what happens...

Arno

Thanks, regards Chantal


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

Attachments: novosirj.vcf

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arno Lehmann wrote:
Hi,

On 6/7/2007 7:26 PM, Chantal Rosmuller wrote:
Hi list,

My bacula configuration is not working the way I expect, I hope someone can
give me a pointer,

I guess I can...

I want to make a full backup every day, regardless whether there's a different
tape or the same. I use a volume retentio period of 1 hour but when I want to
backup to the same tape I get the follwoing error:

Volume "DefaultVolume-0014" status is Used, but should be Append, Purged or
Recycle

This shows that volumes are not recycled.

This is the pool definition:

Pool {
Name = "Default"
PoolType = "Backup"
Recycle = "yes"
AutoPrune = "yes"
VolumeRetention = 1 hours
AcceptAnyVolume = "yes"
LabelFormat = "DefaultVolume-"
Use Volume Once = "yes"
}

the last records of "list media" :
...
The status of DefaultVolume-0014 is "used" but the backup finished more than
an hour ago, what am I doing wrong here?


You've got
"Use Volume Once = <yes|no>
This directive if set to yes specifies that each volume is to be
used only once. This is most useful when the Media is a file and you
want a new file for each backup that is done. The default is no (i.e.
use volume any number of times). This directive will most likely be
phased out (deprecated), so you are recommended to use Maximum Volume
Jobs = 1 instead."

Set which effectively disables volume recycling. Remove that directive,
reload the configuration, update the existing volumes from the pool
resource, , and see what happens...

I would disagree with that. As far as I know, Use Volume Once has been
removed for some time. However, the replacement (Maximum Volume Jobs =
1) I use on my system to cause volumes to be marked used after one use.

However, this does not affect recycling in my situation.

I would suggest the original poster may have forgotten to update volumes
(having created the volume before the current pool directives were in
place).

Chantal, I'd want to see at a minimum an llist on the volume in
question, just to verify that at the very least the parameters have made
it to the volume in the first place.

In addition: keep in mind that the volume may very well not show
recycled right after the retention time is up. There are some actions
that will cause the volume recycling algorithm to be run through -- one
would be attempting a backup against the volume, and I believe 'status
dir' might be another. Not sure of specifics. Bacula does not, however,
throw away the contents of the volume right away on its own -- it
attempts to keep the data as long as possible.

- --
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$&| |__| | | |__/ | \| _| |novosirj < at > um... - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaKyKmb+gadEcsb4RArtMAKDbsXiDXLpHeBm9HNSD5SOYWZv+4gCg3CGK
IYd71svC9205Z09gBNPk1PI=
=LIsH
-----END PGP SIGNATURE-----

On Friday 08 June 2007 03:10, Ryan Novosielski wrote:
<snip>

I would disagree with that. As far as I know, Use Volume Once has been
removed for some time.

No I could still set it to yes in this version.

However, the replacement (Maximum Volume Jobs =
1) I use on my system to cause volumes to be marked used after one use.

However, this does not affect recycling in my situation.

I would suggest the original poster may have forgotten to update volumes
(having created the volume before the current pool directives were in
place).

Chantal, I'd want to see at a minimum an llist on the volume in
question, just to verify that at the very least the parameters have made
it to the volume in the first place.

here it is:
MediaId: 31
VolumeName: DefaultVolume-0014
Slot: 0
PoolId: 1
MediaType: DDS
FirstWritten: 2007-06-08 07:26:01
LastWritten: 2007-06-08 07:26:01
LabelDate: 2007-06-08 07:26:01
VolJobs: 0
VolFiles: 0
VolBlocks: 0
VolMounts: 7
VolBytes: 1
VolErrors: 0
VolWrites: 156,381
VolCapacityBytes: 0
VolStatus: Append
Recycle: 1
VolRetention: 7,200
VolUseDuration: 0
MaxVolJobs: 1
MaxVolFiles: 0
MaxVolBytes: 0
InChanger: 1
EndFile: 4
EndBlock: 2,170
VolParts: 0
LabelType: 0
StorageId: 2

status is append at the moment because a backup is running

In addition: keep in mind that the volume may very well not show
recycled right after the retention time is up. There are some actions
that will cause the volume recycling algorithm to be run through -- one
would be attempting a backup against the volume, and I believe 'status
dir' might be another. Not sure of specifics. Bacula does not, however,
throw away the contents of the volume right away on its own -- it
attempts to keep the data as long as possible.

Any idea how long this takes? Approximately?

I am testing Arno's suggestion now, to use "Maximum Volume
Jobs = 1". I'll let you know what happens.

This morning I noticed another problem, the backup was running for an hour and
then I got this message:

08-Jun 02:05 Server-sd: BackupAll.2007-06-08_01.00.00 Error: block.c:538 Write
error at 4:2171 on device "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: BackupAll.2007-06-08_01.00.00 Error: Error writing
final EOF to tape. This Volume may not be readable.
dev.c:1542 ioctl MTWEOF error on "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: End of medium on Volume "DefaultVolume-0014"
Bytes=4,139,734,897 Blocks=64,170 at 08-Jun-2007 02:06.

then bacula requested another tape, what does this mean? Something wrong with
the tape? it is impossible that the tape is full because it's 12G and I
backup 4G, and it was definitely not appending the data.

Chantal

Attachments: novosirj.vcf

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chantal Rosmuller wrote:
On Friday 08 June 2007 03:10, Ryan Novosielski wrote:
<snip>
I would disagree with that. As far as I know, Use Volume Once has been
removed for some time.

No I could still set it to yes in this version.

Doesn't mean it was doing anything! What version is this, by the way
- -- you never said.

Chantal, I'd want to see at a minimum an llist on the volume in
question, just to verify that at the very least the parameters have made
it to the volume in the first place.

here it is:
MediaId: 31
VolumeName: DefaultVolume-0014
Slot: 0
PoolId: 1
MediaType: DDS
FirstWritten: 2007-06-08 07:26:01
LastWritten: 2007-06-08 07:26:01
LabelDate: 2007-06-08 07:26:01
VolJobs: 0
VolFiles: 0
VolBlocks: 0
VolMounts: 7
VolBytes: 1
VolErrors: 0
VolWrites: 156,381
VolCapacityBytes: 0
VolStatus: Append
Recycle: 1
VolRetention: 7,200
VolUseDuration: 0
MaxVolJobs: 1
MaxVolFiles: 0
MaxVolBytes: 0
InChanger: 1
EndFile: 4
EndBlock: 2,170
VolParts: 0
LabelType: 0
StorageId: 2

status is append at the moment because a backup is running

Other than your volume retention being 2 hours, not the 1 hour you had
set in the pool (7200 seconds), this looks like what you'd expect.

In addition: keep in mind that the volume may very well not show
recycled right after the retention time is up. There are some actions
that will cause the volume recycling algorithm to be run through -- one
would be attempting a backup against the volume, and I believe 'status
dir' might be another. Not sure of specifics. Bacula does not, however,
throw away the contents of the volume right away on its own -- it
attempts to keep the data as long as possible.

Any idea how long this takes? Approximately?

It will not happen until it is necessary, ie. the next backup begins, or
someone uses 'status dir' possibly (which needs to know for reasons I do
not recall). Bacula always avoids removing data. In fact, if you have
another volume in the pool that is appendable, AFAIK Bacula will never
recycle.

I am testing Arno's suggestion now, to use "Maximum Volume
Jobs = 1". I'll let you know what happens.

That appears to already be set, but you may have made this change prior
to this current run.

This morning I noticed another problem, the backup was running for an hour and
then I got this message:

08-Jun 02:05 Server-sd: BackupAll.2007-06-08_01.00.00 Error: block.c:538 Write
error at 4:2171 on device "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: BackupAll.2007-06-08_01.00.00 Error: Error writing
final EOF to tape. This Volume may not be readable.
dev.c:1542 ioctl MTWEOF error on "tape" (/dev/nst0). ERR=Input/output error.
08-Jun 02:06 Server-sd: End of medium on Volume "DefaultVolume-0014"
Bytes=4,139,734,897 Blocks=64,170 at 08-Jun-2007 02:06.

then bacula requested another tape, what does this mean? Something wrong with
the tape? it is impossible that the tape is full because it's 12G and I
backup 4G, and it was definitely not appending the data.

Did you ever conduct the btape tests? Generally if this is a nuance of
your hardware, the btape tests will turn that up. As far as whether it's
the media -- it's often difficult to tell. Changing out for another tape
is a way to find out. You might even consider erasing that tape. But I'd
only recommend that if you know that the btape tests worked correctly.

- --
---- _ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III
|$&| |__| | | |__/ | \| _| |novosirj < at > um... - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGaQUumb+gadEcsb4RAkqlAKCVbVGT+lNatbenuhUjUI0ZjGUvjQCfTz+/
XLz5QbceFDxaIjgn2GH6Iqc=
=Ebnp
-----END PGP SIGNATURE-----

<snip>

then bacula requested another tape, what does this mean? Something wrong
with the tape? it is impossible that the tape is full because it's 12G
and I backup 4G, and it was definitely not appending the data.

Did you ever conduct the btape tests? Generally if this is a nuance of
your hardware, the btape tests will turn that up. As far as whether it's
the media -- it's often difficult to tell. Changing out for another tape
is a way to find out. You might even consider erasing that tape. But I'd
only recommend that if you know that the btape tests worked correctly.

Yes I did, the test showed no problems. I am succesfully making backups so
there can't be anything wrong with the hardware. But it has to start working
without user interference.

On Friday 08 June 2007 09:28, Ryan Novosielski wrote:
<snip>

It will not happen until it is necessary, ie. the next backup begins, or
someone uses 'status dir' possibly (which needs to know for reasons I do
not recall). Bacula always avoids removing data. In fact, if you have
another volume in the pool that is appendable, AFAIK Bacula will never
recycle.


wait a minute are you serious? I have lots of appendable volumes! i just
relabeled a bunch of tapes:

list media:

| 23 | DefaultVolume-0006 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 24 | DefaultVolume-0007 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 25 | DefaultVolume-0008 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 26 | DefaultVolume-0009 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 27 | DefaultVolume-0010 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 28 | DefaultVolume-0011 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 29 | DefaultVolume-0012 | Purged | 2,644,475,759 | 3 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-07 12:44:55 |
| 30 | DefaultVolume-0013 | Used | 1,971,864,651 | 2 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-05 17:06:45 |
| 31 | DefaultVolume-0014 | Used | 4,764,121,146 | 5 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-08 08:37:45 |
| 32 | DefaultVolume-0015 | Used | 4,755,372,018 | 5 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-07 16:05:15 |

+---------+--------------------+-----------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+

So what to do, should I change their status to Used?

Chantal

Hi,

On 6/8/2007 3:10 AM, Ryan Novosielski wrote:
... recycling volumes...

You've got
"Use Volume Once = <yes|no>
This directive if set to yes specifies that each volume is to be
used only once. This is most useful when the Media is a file and you
want a new file for each backup that is done. The default is no (i.e.
use volume any number of times). This directive will most likely be
phased out (deprecated), so you are recommended to use Maximum Volume
Jobs = 1 instead."

Set which effectively disables volume recycling. Remove that directive,
reload the configuration, update the existing volumes from the pool
resource, , and see what happens...

I would disagree with that. As far as I know, Use Volume Once has been
removed for some time. However, the replacement (Maximum Volume Jobs =
1) I use on my system to cause volumes to be marked used after one use.

However, this does not affect recycling in my situation.

I somehow had the impression that the deprecated directive also prvented
recycling, but admittedly, I never tried it.

The recommended options clearly separate number of jobs and recycling
settings, THAT I know because I use it :-)

I would suggest the original poster may have forgotten to update volumes
(having created the volume before the current pool directives were in
place).

Quite possible...

Chantal, I'd want to see at a minimum an llist on the volume in
question, just to verify that at the very least the parameters have made
it to the volume in the first place.

In addition: keep in mind that the volume may very well not show
recycled right after the retention time is up. There are some actions
that will cause the volume recycling algorithm to be run through -- one
would be attempting a backup against the volume, and I believe 'status
dir' might be another. Not sure of specifics. Bacula does not, however,
throw away the contents of the volume right away on its own -- it
attempts to keep the data as long as possible.

Arno

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

<snip>

I would suggest the original poster may have forgotten to update volumes
(having created the volume before the current pool directives were in
place).

Quite possible...

<snip>

No sorry guys, I didn't forget . I posted the last records of list media
remember? I don't have time to test now but tomorrow I will, I changed

use volume once into no
maximum volume jobs into 1
and I manually set all appendable volumes to "Used"

Chantal

Hi,

On 6/8/2007 12:06 PM, Chantal Rosmuller wrote:
On Friday 08 June 2007 09:28, Ryan Novosielski wrote:
<snip>
It will not happen until it is necessary, ie. the next backup begins, or
someone uses 'status dir' possibly (which needs to know for reasons I do
not recall).

To determine which volumes will be used.

Bacula always avoids removing data. In fact, if you have
another volume in the pool that is appendable, AFAIK Bacula will never
recycle.


wait a minute are you serious? I have lots of appendable volumes! i just
relabeled a bunch of tapes:

list media:

| 23 | DefaultVolume-0006 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 24 | DefaultVolume-0007 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 25 | DefaultVolume-0008 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 26 | DefaultVolume-0009 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 27 | DefaultVolume-0010 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 28 | DefaultVolume-0011 | Append | 1 | 0 |
7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |
| 29 | DefaultVolume-0012 | Purged | 2,644,475,759 | 3 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-07 12:44:55 |
| 30 | DefaultVolume-0013 | Used | 1,971,864,651 | 2 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-05 17:06:45 |
| 31 | DefaultVolume-0014 | Used | 4,764,121,146 | 5 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-08 08:37:45 |
| 32 | DefaultVolume-0015 | Used | 4,755,372,018 | 5 |
7,200 | 1 | 0 | 1 | DDS | 2007-06-07 16:05:15 |
+---------+--------------------+-----------+----------------+----------+--------------+---------+------+-----------+-----------+---------------------+

So what to do, should I change their status to Used?

No. These volumes are not usd yet, and then "Append" is the correct
state for them.

In fact, I don't quite understand your problem now... it seems that,
even if you've got lots of usable (i.e. "Append") volumes available you
want to recycle other volumes.

That's not how Bacula prefers to work.

If you want to make sure that Bacula tries using whatever is loaded in
the tape drive, "Recycle current volume" might help you, but should be
used with care.

Arno

Chantal

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > li...
https://lists.sourceforge.net/lists/listinfo/bacula-users

--
IT-Service Lehmann al < at > it...
Arno Lehmann http://www.its-lehmann.de

On Friday 08 June 2007 13:03, Arno Lehmann wrote:
Hi,

On 6/8/2007 12:06 PM, Chantal Rosmuller wrote:
On Friday 08 June 2007 09:28, Ryan Novosielski wrote:
<snip>

It will not happen until it is necessary, ie. the next backup begins, or
someone uses 'status dir' possibly (which needs to know for reasons I do
not recall).

To determine which volumes will be used.

Bacula always avoids removing data. In fact, if you have

another volume in the pool that is appendable, AFAIK Bacula will never
recycle.

wait a minute are you serious? I have lots of appendable volumes! i just
relabeled a bunch of tapes:

list media:
| 23 | DefaultVolume-0006 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 24 | DefaultVolume-0007 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 25 | DefaultVolume-0008 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 26 | DefaultVolume-0009 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 27 | DefaultVolume-0010 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 28 | DefaultVolume-0011 | Append | 1 | 0 |

7,200 | 1 | 0 | 1 | DDS | 0000-00-00 00:00:00 |

| 29 | DefaultVolume-0012 | Purged | 2,644,475,759 | 3 |

7,200 | 1 | 0 | 1 | DDS | 2007-06-07 12:44:55 |

| 30 | DefaultVolume-0013 | Used | 1,971,864,651 | 2 |

7,200 | 1 | 0 | 1 | DDS | 2007-06-05 17:06:45 |

| 31 | DefaultVolume-0014 | Used | 4,764,121,146 | 5 |

7,200 | 1 | 0 | 1 | DDS | 2007-06-08 08:37:45 |

| 32 | DefaultVolume-0015 | Used | 4,755,372,018 | 5 |

7,200 | 1 | 0 | 1 | DDS | 2007-06-07 16:05:15 |
+---------+--------------------+-----------+----------------+----------+-
-------------+---------+------+-----------+-----------+-------------------
--+

So what to do, should I change their status to Used?

No. These volumes are not usd yet, and then "Append" is the correct
state for them.

In fact, I don't quite understand your problem now... it seems that,
even if you've got lots of usable (i.e. "Append") volumes available you
want to recycle other volumes.

That's not how Bacula prefers to work.

If you want to make sure that Bacula tries using whatever is loaded in
the tape drive, "Recycle current volume" might help you, but should be
used with care.

Arno

Hi Arno,

Yes it is absolutely necessary that bacula uses the tape that is in the drive,
That is what the customer wants. They want to switch the tapes every day
themselves but when they forget they still want a new backup to be made. I
noticed that that's not exactly the bacula logic, but it should be possible I
think.

Chantal

<snip>

Hi Arno,

Yes it is absolutely necessary that bacula uses the tape that is in the
drive, That is what the customer wants. They want to switch the tapes every
day themselves but when they forget they still want a new backup to be
made. I noticed that that's not exactly the bacula logic, but it should be
possible I think.

Chantal

</snip>

I still haven't solved this problem..... The old tape has to be automatically
overwritten when the user forgets to change it. The retention period seems to
work now, but the following happened:

- the backup on the "used" tape did not take place, message was the same:
Volume "DefaultVolume-0014" status is Used, but should be Append, Purged or
Recycle
- I canceled the job and started one manually, still nothing
- then I manually mounted the tape and the backup started

So the recycling works but the tape has to be unmounted and remounted, is
there anyway to do this automatically?

Chantal

Thanks, everything works now,
Chantal