Still not backing up latest chain only on v9 U1

Everything about backing up to tape

Still not backing up latest chain only on v9 U1

Veeam Logoby pkelly_sts » Wed Apr 20, 2016 10:31 am

[Ticket num 01769040, previous ticket num: 01721125]

I had a previous ticket where v8 wasn't copying only the latest chain to tape on a first run & was told the issue was fixed in v9 U1. I've now upgraded to v9 U1 & still finding the same issue, when selecting a copy job to then copy to tape, it's selecting a whole heap of restore points when it should only be selecting the latest chain (see below).

What am I missing??

Code: Select all
20/04/2016 10:49:51 :: Building source backup files list started at 20/04/2016 10:49
20/04/2016 10:49:56 :: Synthesized full backup was not created for 17/03/2016: there are no new restore points between 06/03/2016 and 17/03/2016
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-22T194000.vbk restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-19T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-18T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-17T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-16T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-15T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-14T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-13T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-12T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-11T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-10T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-09T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-08T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-07T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-06T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-05T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-04T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-03T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-02T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-04-01T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-31T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-30T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-29T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-28T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-27T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-26T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-25T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-24T194000.vib restore point will be placed to media set 
20/04/2016 10:49:56 :: New <Remote-Copy-Job>-Copy2016-03-23T194000.vib restore point will be placed to media set 
20/04/2016 10:50:09 :: Source backup files detected. VBK: 1, VBK map: 0, VIB: 28
20/04/2016 10:50:12 :: Queued for processing at 20/04/2016 10:50:12
20/04/2016 10:50:12 :: Required backup infrastructure resources have been assigned
20/04/2016 10:50:17 :: Drive 1 (Server: <tape-server-name>, Library: <tape-server-name> LIB-1, Drive ID: Tape1) locked successfully
20/04/2016 10:50:17 :: Loading tape GM8483L6 from Slot 12 to Drive 1 (Server: <tape-server-name>, Library: <tape-server-name> LIB-1, Drive ID: Tape1)
20/04/2016 10:52:10 :: Current tape is GM8483L6
20/04/2016 10:52:41 :: New tape backup session started, encryption: disabled
20/04/2016 10:53:05 :: Processing full backups started at 04/20/2016 10:49:49
20/04/2016 10:53:17 :: Processing <Remote-Copy-Job>-Copy2016-03-22T194000.vbk
[New Sig: PLEASE get GFS tape support for incrementals!!!]
pkelly_sts
Expert
 
Posts: 504
Liked: 55 times
Joined: Thu Jun 13, 2013 10:08 am
Full Name: Paul Kelly

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby pkelly_sts » Wed Apr 20, 2016 10:46 am

Actually, looking again, even though it's starting with the .vbk dated 2016-03-22, I've just realised that that is still the most recent .vbk with an update stamp of last night as expected, but I still don't understand why it's selecting all the incrementals /back/ to that date as well?
[New Sig: PLEASE get GFS tape support for incrementals!!!]
pkelly_sts
Expert
 
Posts: 504
Liked: 55 times
Joined: Thu Jun 13, 2013 10:08 am
Full Name: Paul Kelly

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby v.Eremin » Wed Apr 20, 2016 12:24 pm

Is processing increments option enabled or not? Also, it stands to reason to request this hot fix, as there are some issues with the given option in Update 1. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 969 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby pkelly_sts » Wed Apr 20, 2016 1:04 pm

Increments are enabled, yes. Ah, seems exactly like my issue so hopefully support will pick that up & direct me to the hotfix. Thanks!
[New Sig: PLEASE get GFS tape support for incrementals!!!]
pkelly_sts
Expert
 
Posts: 504
Liked: 55 times
Joined: Thu Jun 13, 2013 10:08 am
Full Name: Paul Kelly

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby alanbolte » Wed Apr 20, 2016 8:02 pm

I took a quick look at your case, and it looks like these tape jobs have been created recently, and have been failing. The "current chain" for a forward incremental job consists of the most recent VBK file, and all VIB files newer than that VBK. So the first time you run a backup to tape job, it will need to write all those files to tape. Were you wanting it to start with a virtual full instead?
alanbolte
Expert
 
Posts: 635
Liked: 170 times
Joined: Mon Jun 18, 2012 8:58 pm
Full Name: Alan Bolte

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby pkelly_sts » Thu Apr 21, 2016 9:11 am

I must be misunderstanding something then (not hard). I assumed that if I selected "most recent chain" it would copy the most recent full, and any subsequent incrementals. In this case it did the most recent full and ALL incrementals (29 restore points - i.e. everything in the repository except for a monhtly full that happened to sit somewhere in the middle).

The scenario I'm trying to look at is making a business decision to start copying a backup to tape "starting from most recent full and continuing thereafter from there".

I don't really understand why older incrementals are deemed necessary in this scenario?

I think I'm going to /need/ to create a synthetic full to get the kind of result I'm after but really just assumed that, seeing as the most recent full, generally dated the previous night, should be really easy to dump to tape as a start to a daily tape plan...
[New Sig: PLEASE get GFS tape support for incrementals!!!]
pkelly_sts
Expert
 
Posts: 504
Liked: 55 times
Joined: Thu Jun 13, 2013 10:08 am
Full Name: Paul Kelly

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby v.Eremin » Thu Apr 21, 2016 11:21 am

I must be misunderstanding something then (not hard). I assumed that if I selected "most recent chain" it would copy the most recent full, and any subsequent incrementals. In this case it did the most recent full and ALL incrementals (29 restore points - i.e. everything in the repository except for a monhtly full that happened to sit somewhere in the middle).

I must have hurried up a bit in recommending a hot fix for you, as it's only applicable for reversed incremental chains.

After having read the whole thread again, it seems to me that everything has worked properly in your case. Being executed on schedule, the backup to tape job copied the most recent full backup and increments dependent on it. So, I cannot see any issues here.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 969 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Still not backing up latest chain only on v9 U1

Veeam Logoby alanbolte » Thu Apr 21, 2016 8:50 pm

pkelly_sts wrote:I think I'm going to /need/ to create a synthetic full to get the kind of result I'm after but really just assumed that, seeing as the most recent full, generally dated the previous night, should be really easy to dump to tape as a start to a daily tape plan...

I think you might be confusing the modified date of the file with the restore point it contains (which is indicated by the file name). In forward forever-incremental, the full backup file is modified with every backup, but it contains the oldest restore point in the chain.
alanbolte
Expert
 
Posts: 635
Liked: 170 times
Joined: Mon Jun 18, 2012 8:58 pm
Full Name: Alan Bolte


Return to Tape



Who is online

Users browsing this forum: MBT, Yahoo [Bot] and 5 guests