DisableVBKRename

[hbilke]

Hi fellas,

is there a setting like the REGkey for Windows: DisableVBKRename?

[PTide]

Hi,

Would you provide more details on the challenge that you need the alike setting for?

Thanks

[hbilke]

I'm doing a backup of a Linux Mint to a NAS @ my home-LAN. This NAS is scheduled to do a RSYNC to another NAS that powers on in a given time period and then powers down itself. Every time the VBK is written anew the time won't suffice. Me thinks RSYNC would handle just the changes perfectly.

#Harry

[PTide]

I'm not sure that I get it. Do you mean that RSYNC cannot pick up VBK with a new name? Or does rsyncing VBK takes so long that the NAS shuts itself down before the sync is finished?

Thanks

[hbilke]

It'll pick up and copy the new named vbk (huge block) - taking to much time for the full copy. I could/would wait on the first run but want to have the target NAS offline then. I have not only Linux/Arch within my LAN but Windows and MAC OS, 2!

One alternative would be, if the agent could be configured to use a locked down user/pw combo for accessing the storage.

Cheers

[hbilke]

The agent can be configured using credentials to a share. But the copy could be faster and a device not reachable at all is even better

[PTide]

If you need to keep .vbk name intact for rsync, you can utilize pre/post-job scripts:

Post-job script

1. Save the new VBK name to name_after file
2. Rename VBK to some constant name, rsync_vbk for example

Pre-job script

1. Check if the file name_after exists
a. If not, return "0"
b. If yes, get the value from name_after file and rename rsync_vbk back to that value so the job can work properly.

Do you get the idea?

Thanks

[hbilke]

Yepp - got the idea, but an internal "switch" would be much better, esp. for that "habitat".

Thanks

Harald

[PTide]

Got it. We will consider adding such setting, thank you for your feedback!