New media set created when it should not be...

Everything about backing up to tape

New media set created when it should not be...

Veeam Logoby TommyB » Tue Jan 13, 2015 9:02 am

Hi,

I currently have a single tape job for full and incremental that copies both to the same media pool.

I have set up the media pool to create a new media set every Monday, so I get a weekly set of tapes with full backups on Monday (the backup jobs create synthetic fulls on Saturdays) and incrementals from Tuesday until Friday.

Typically, the full backups fit onto three tapes, with the third tape filled up to 25% capacity. Normally I would expect that the following incrementals would be appended to tape three until it is full and would then continue with tape four of the same media set... and so on.

I'm quite sure this worked as I described above for V7, but since V8, after the third tape is ejected, the system wants to have a new tape which is assigned to a new media set the problem with that is that I run out of tapes because a new media set also gets a new expiration date and sooner or later there are no more tapes in the pool that can be overwritten.

regards
Thomas
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby TommyB » Tue Jan 13, 2015 9:39 am

There seems to be another problem, full backup files that where already backed up on Monday are backed up again on Tuesday, this is the message that shows in the job log:

Modified storage D:\Backups\company_fileserver\company_fileserver2015-01-11T210252.vbk on This server was added to backup list


When looking at the file date, the .vbk file has a timestamp from sunday, so it apparently did not change from Monday to Tuesday. The only file that is newer is a .vib from Monday evening.

Is this expected behaviour?
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby v.Eremin » Tue Jan 13, 2015 10:49 am

Since V8, after the third tape is ejected, the system wants to have a new tape which is assigned to a new media set the problem with that is that I run out of tapes because a new media set also gets a new expiration date and sooner or later there are no more tapes in the pool that can be overwritten.

What time is specified for media set creation? May be a new media set has been created in accordance with the specified settings and, thus, a backup servers asks for a new medium? Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: New media set created when it should not be...

Veeam Logoby martynuk » Tue Jan 13, 2015 12:04 pm

We have been having issues with vbk files being backed up multiple times under v8. We are currently testing a private fix with patch 1, although I still can't be sure if it has completely fixed our problems yet. I am waiting for the backup to tape job to "catch up" with the backlog of vbk files before I can be certain.

Probably worth raising a call with Veeam to see if you have the same problem. Our case number with Veeam is 00690220.
martynuk
Enthusiast
 
Posts: 48
Liked: 9 times
Joined: Fri Aug 16, 2013 1:34 pm
Full Name: Martin Etheridge

Re: New media set created when it should not be...

Veeam Logoby TommyB » Tue Jan 13, 2015 2:00 pm

v.Eremin wrote:What time is specified for media set creation? May be a new media set has been created in accordance with the specified settings and, thus, a backup servers asks for a new medium? Thanks.


The setting is to create a new media set at 00:01 on Monday only.

For the currently week I have a Mediaset "Weekly Backup 12.01.2015 09:01" that was created on Monday, plus a media set "Weekly Backup 13.01.2015 09:17" that was created today (which in my opinion should not happen).

Not sure if this might be related, but I have set up the tape job to eject the tape at the end.

What happened on Monday:

- Inserted Tape 1 -> new media set
- Tape 1 full -> ejected

- Insert Tape 2
- Tape 2 full -> ejected

- Insert Tape 3
- Tape 3 -> ejected

This morning (Tuesday) I inserted Tape 3 again (because it still had plenty of free space) but it was ejected and the next tape I inserted got a new media set (and sequence no. 1)

I now had to change the tape retention to only 1 week instead of 2 because otherwise I would run out of available tapes. :?

regards
Thomas
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby Dima P. » Tue Jan 13, 2015 4:38 pm

Thomas,
From the top of my head - any time zone or time changes inside your infrastructure / backup server?
Dima P.
Veeam Software
 
Posts: 6242
Liked: 440 times
Joined: Mon Feb 04, 2013 2:07 pm
Location: SPb
Full Name: Dmitry Popov

Re: New media set created when it should not be...

Veeam Logoby v.Eremin » Wed Jan 14, 2015 9:05 am

And just to be sure there is only Monday selected in "Mediaset -> Daily at -> On these days -> Days" settings? Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: New media set created when it should not be...

Veeam Logoby TommyB » Wed Jan 14, 2015 9:33 am

Yes, see screenshot here:

http://pbrd.co/1Bo8pAI

And it seems I can't get the tape backup to an end because every morning it adds another old .vbk file:

14.01.2015 09:13:42 :: Modified storage D:\Backups\ellis_Archiv _ DC - ELTAS2 _ ELTDC1\ellis_Archiv _ DC - ELTAS2 _ ELTDC12015-01-11T210326.vbk on This server was added to backup list
14.01.2015 09:13:42 :: Changes in source storage detected. Scan for changes
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby v.Eremin » Wed Jan 14, 2015 10:10 am

Is retention for given media pool shorter than retention for source backup jobs? Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: New media set created when it should not be...

Veeam Logoby TommyB » Wed Jan 14, 2015 10:54 am

v.Eremin wrote:Is retention for given media pool shorter than retention for source backup jobs? Thanks.


The media pool currently has 1 week retention, the backup jobs have different retention settings ranging from 7 (vsphere appliance ) to 45 (Exchange server)

But how can this be "longer" or "shorter"?

Retention for backup jobs is "number of restore points" and for media pools it is "number of days/weeks/months"... how can you compare number of restore points to a time span?
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby v.Eremin » Wed Jan 14, 2015 11:00 am

The main idea is that backups should be stored longer on tapes, than they are on disks. Otherwise, the information about those backups would be removed from tape catalogue (in accordance with the specified media pool settings) and backup server would try to archive to tapes those backups (that are still present on disks) once again. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: New media set created when it should not be...

Veeam Logoby TommyB » Wed Jan 14, 2015 1:36 pm

v.Eremin wrote:The main idea is that backups should be stored longer on tapes, than they are on disks. Otherwise, the information about those backups would be removed from tape catalogue (in accordance with the specified media pool settings) and backup server would try to archive to tapes those backups (that are still present on disks) once again. Thanks.


Well, before the problem with the .vbk files (=before 8.x) the tape retention was two weeks and I never had any problem with the same backup files being backed up multiple times or wrong media sets... I also never saw the message "Modified storage xxxx on This server was added to backup list" before 8.0.

And since the .vbk file was created on Sunday, and was already backed up on Monday, it should not being copied to tape again one day later... with 1 week retention setting.
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun

Re: New media set created when it should not be...

Veeam Logoby v.Eremin » Wed Jan 14, 2015 2:11 pm

Yep, based on the provided settings, it should not have been copied indeed. I'd recommend opening a ticket with our support team, as debug logs should shed some light on the experienced behaviour. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 968 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: New media set created when it should not be...

Veeam Logoby TommyB » Thu Jan 15, 2015 8:11 am

Done, case ID 00727703

By the way, the backup that just started created a new media set again... despite the fact that 575 GB where free on the last tape from yesterday :(

At least it only processes the incrementals from the last two days.
TommyB
Expert
 
Posts: 115
Liked: 15 times
Joined: Wed Aug 28, 2013 9:46 am
Location: Germany.Europe.Terra.Sol.Milkyway.Localgroup.Virgo
Full Name: Thomas Braun


Return to Tape



Who is online

Users browsing this forum: No registered users and 9 guests