Availability for the Always-On Enterprise
foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: How to disable VBK rename after maintenance task?

Post by foggy » Oct 05, 2017 1:49 pm

fika wrote:Foggy, one question, if I set DisableVBKRename=1 with a weekly maintenance task enabled, will rename of the .vbk file occur everyday, or only once a week after maintenance task ?
Not sure it will work as you would like, since VBK will be renamed upon compact operation and to get back to the name without a timestamp, you would need to start anew (see below).
fika wrote:If I set this registry key for an already started job, do I need to launch a whole new full backup for the key to take effect ?
According to this KB, the value works for new jobs or jobs for which you first perform the "Remove from backups" command. Also don't forget to restart the backup server after making this registry change.

fika
Influencer
Posts: 12
Liked: 1 time
Joined: Sep 20, 2017 8:10 am
Full Name: fika
Contact:

Re: How to disable VBK rename after maintenance task?

Post by fika » Oct 05, 2017 1:59 pm

Mmmmh so it should work one week, until the Saturday compact operation run.
Once compact will have run, the .vbk will be timestamped.
Then, will the .vbk name change everyday ? Or only the next Saturday, after the next compact operation ?
Thank you again Foggy !

foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: How to disable VBK rename after maintenance task?

Post by foggy » Oct 05, 2017 3:16 pm

VBK will be changed only upon compact operation, so it will remain the same (timstamped with the date of compact) during the week.

fika
Influencer
Posts: 12
Liked: 1 time
Joined: Sep 20, 2017 8:10 am
Full Name: fika
Contact:

Re: How to disable VBK rename after maintenance task?

Post by fika » Oct 05, 2017 3:24 pm

Foggy, thank you very much for your answer !
This behavior could help me a tittle though :)

Btw, did you manage to get in touch with dev team to propose them to support DisableVBKRename=1 even after compact operation ?

Thank you again !

foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: How to disable VBK rename after maintenance task?

Post by foggy » Oct 05, 2017 3:44 pm

We have this filed in our issue/feature tracking system since the beginning of this thread, but there's no particular ETA for this at the moment.

fika
Influencer
Posts: 12
Liked: 1 time
Joined: Sep 20, 2017 8:10 am
Full Name: fika
Contact:

Re: How to disable VBK rename after maintenance task?

Post by fika » Oct 05, 2017 3:48 pm

OK, since about 18 months then :)
Anyway, thank you very much for your confirmation, and let's then stay tuned !

fika
Influencer
Posts: 12
Liked: 1 time
Joined: Sep 20, 2017 8:10 am
Full Name: fika
Contact:

Re: How to disable VBK rename after maintenance task?

Post by fika » Nov 24, 2017 8:54 am

Foggy, I confirm the behaviour, VBK name changes only upon compact operation, otherwise it remains the same (timestamped with the date of compact).

I would really be glad if you could support DisableVBKRename=1 even after compact operation, in upcoming update 3 for Veeam Backup & Replication 9.5.
That would really be good news !
If we think about it, the fix should be quite tiny to write (compared to other ones), don't you think so ?

Thank you very much again to you and dev team for your support !

foggy
Veeam Software
Posts: 16832
Liked: 1361 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: How to disable VBK rename after maintenance task?

Post by foggy » Nov 24, 2017 4:34 pm

This will not be a part of U3.

Dave T
Novice
Posts: 3
Liked: 1 time
Joined: Apr 01, 2018 3:25 pm
Full Name: Dave T
Contact:

Re: How to disable VBK rename after maintenance task?

Post by Dave T » Apr 01, 2018 11:52 pm

I think rsync will have a tough time finding out the bytes unless compression is disabled (which you probably don't want during your WAN transfer).

Currently testing in a home lab but had a similar case where I wanted to get my Veeam backups onto offline cloud storage and noticed that the file had a different name. My thoughts were that this shouldn't matter since the program that I was using (hashbackup) supports deduplication.

The trick to get it to work well (high deduplication with full files regardless of name/timestamp) was to disable compression entirely and keep on inline deduplication optimized for a lan target.

So flow is basically backup takes place with Veeam (no compression). Script runs to trigger hashbackup which compresses and deduplicates the files before putting them on the cloud. A Veeam backup directory of about 46GB would go down to around 6.5GB of files. If enabling any compression it would totally throw off hashbackups deduplication. I'm making some assumptions here but I don't see how rsync would work any better.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 37 guests