Discussions related to exporting backups to tape and backing up directly to tape.
Post Reply
DaStivi
Service Provider
Posts: 295
Liked: 46 times
Joined: Jun 30, 2015 9:13 am
Full Name: Stephan Lang
Location: Austria
Contact:

2 Drives causing multiple Media Sets with parallel processing, but why?

Post by DaStivi »

Hi, got some interesseting quirk, in the firstplace i have to admit that i was not aware of that behaviour at all, an support Case did showed me the correct part in Veeam online docs instantly:
https://helpcenter.veeam.com/docs/backu ... ml?ver=100

Parallel Processing with Daily at Option
When the media pool is set to Daily at option, several media sets (per each drive) are opened on the scheduled day. If tape jobs run twice or more before the scheduled day, they continue these media sets — in this case, the jobs use tapes that have most free space first.
Image

nothing to complain about this... its how i did see it... but...

Conditions as following:

1 Library, 2 Drives (24Tapes)

1 MediaPool with setting that each Saturday a new MediaSet should be "created"
both incremental and Full Jobs using the same Mediaset... so basically All-In

What i would think is that Full and corresponding incrementals should be on the same MediaSet for Exportability... the MediaSet should be then write protected for 1 year...
Even with 2 drives used in parallel processing, the tapes should be in the same Mediaset, so that the protection is the same and also its entierly clear when exporting the tapes "for a week" this is MediaSet #X

But, with the two MediaSets created from the Backup to Tape Jobs, it happens that the same Job that started the MediaSet#2 just writes it's next backup to mediaSet#1
Fullbackup NDMP to MediaSet1 (drive1)
Fullbackup VMs to mediaset2 (drive2)...

but the following incrementell backups of VMs has been written to MediaSet1/drive1 again... :roll:

am i wrong with my assumption, what a mediaset is good for? this is the exact reason to have the mediasets/mediapools... to have a logical container that helps organzing the tapes... but in this particual case that dont help, it makes it rather more complicated...
Dima P.
Product Manager
Posts: 14726
Liked: 1707 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: 2 Drives causing multiple Media Sets with parallel processing, but why?

Post by Dima P. »

Hello DaStivi,
But, with the two MediaSets created from the Backup to Tape Jobs, it happens that the same Job that started the MediaSet#2 just writes it's next backup to mediaSet#1
Correct, within single media pools media job will continue any opened media set to maximize the usage of available media free space. Moreover, there is a logic to select the media set with the most free space available when multiple media sets are opened.
am i wrong with my assumption, what a mediaset is good for? this is the exact reason to have the mediasets/mediapools... to have a logical container that helps organzing the tapes... but in this particual case that dont help, it makes it rather more complicated...
If you want to sperate one backups from another (based of fulls vs increments, workload type, retention etc) multiple media pools should be used; media set in simple media pool represent the tape sequence and should not be considered as organizational entity (except GFS media pools where every media set has it's own retention). Cheers!
Post Reply

Who is online

Users browsing this forum: Semrush [Bot] and 11 guests