Configure tape job

[bplancic]

HI everyone,

we have standalone tape drive and are changing tapes manually. We are doing jobs to tape backup

I would like to ask you how to do the following when backing up to tape:

1) Tape currently in drive should be always overwritten (no retention) with full backup
2) If there is Veeam data already on tape i don't want appending - just overwrite.

I have created tape pool with this settings:

1) Create new media set
2) Do not protect data (cyclicaly...)

And nevertheless today job was waiting for the tape - when I said to mark it as free I got the message that retention period is not over.

What am I doing wrong ?

Regards

[Dima P.]

Hello,
Please, try to modify the settings for the media pool/media set according to your scenario:

1) Create new media set

Change it to create media set for each backup session

2) Do not protect data (cyclicaly...)

Agree on this one

If it is possible mark all existing tapes free, and check if export/eject option is off in Tape Job settings.
Thank you.

[veremin]

Just out of curiosity - what product version you're using? Thanks.

[bplancic]

Just out of curiosity - what product version you're using? Thanks.

I'm using latest version (7.0.0.771)

Today it happened again - although I set "no retention period" and "create new backup set" status was "waiting for tape".

So just to clarify - I put the tape in the drive on friday (and set it as free). Backup was made to tape over night and it was succesfull on Saturday. Same tape stayed in drive (I'm not at work to change it) and it was supposed to be overwritten overnight (Saturday to Sunday) but it says that retention period is not over...

Is there some requirement for the tape to be ejected and inserted again ?

Regards

[Dima P.]

Thank you for the heads up.
This issue was addressed in the latest patch but since you mentioned that you are running the latest available build I need to ask you to contact with the support team. Please, let them check if the update to R2A (7.0.0.771) was smooth and all VBR system files were updated correctly. Also, I would highly appreciate if you update this thread with the case ID.

[Reiner63]

Hi bplanic,

any Solutions in your Problem?

I´ve got the same behaviour with my Quantum LTO4.

Thank you!

[Dima P.]

Reiner,
This is a known issue and would be fixed in the upcoming patch 3. Stay tuned.