Is there an option to keep the same file names for the VBK images when using the synthetic fulls?
They now seem to append a date to the file name. It was really handy to have the same name each day as we use this in a selection list for archiving to tape.
We have worked around this by backing up the directory but exclusing all vrb files but would be nice have an option to go back to the good old days of the same file name each day
one other problem we see with this - We had a plan to use a syncronisation tool to sync the vbk file to a remote store. As the file name is changing the program we use will see this as a new file and send the whole thing across not just the changes....
This is also a problem with our setup here. We copy the vbk file off to tape and when the name changes every day it will make things difficult. I use Netvault to do that and I have the ability to exclude all the vrb files which will work for me. Would be better though if they file stayed the same name though.
Hi,
check out this one, i found out how to do it with backup exec. as i don´t know other tape tools you will have to figure out how to exlude files older than one day. the way for be is described in the linked thread.
best regards, Joerg
thanks for the link, I dont think this is going to work with our offsite copy though. We use a tool called superflexible to only copy the changes across.
This will see the file as new and copy all of it again. I guess we can move from a synth full and just use incrementals and copy the directory across
If the tool is called "superflexible" then I am sure it should have basic functionality rsync provides, and that is using the same target file for any source file name...
maybe, I will still have the same problem feeding superflexible the new file name - but I am sure there is a way of doing this.
Just trying to get my head around why we are having to apply work arounds for something that worked. Maybe there is a technical reason for the change in V5????
Yes, there were a few reasons to implement this change - this was need for both current and future functionality. But trust me, I was equally upset to learn about this change when I first heard about it it certainly adds some complexity and brakes existing way of doing things. Well, at least this should allow for more positive effects, than this one negative.
I will discuss with devs if it is possible to make this toggleable via registry key...
We are also using Super Flexble File Synchronizer and since upgrading to v5 it now copies/synchronizes over 500GB nightly vs around 30GB before. This is due to the file name of the vbk files, new name = new file. At least that's what SuperFlex thinks . If possible, I would like a way to be able to choose which name to use for the vbk files.
Same here. We have certain customers were we are using rsync for offsite backup.
This is not working anymore because of the filename change. Any update on this? I didn't see a need to change this because the file has a timestamp so you can exactly see when the backups are taken ..
Same with backup to tape. I had to change the selection to only include the .vbk.
Problem is that we only selected the "backupname.vbk" file in backup since this was the last full and the other full backups are still on the disk.
Now we cannot use the same method, I am trying the method to exclude the *.vbr files and include the *.vbk files only if these files are modified...
rsync backup is not a problem, it can be configured to write into the same target file, I attached sample shell script that selects the latest VBK and copies it over to the existing VBK file on target.
Tape backup is not a problem either, see backup naming when using reversed incremental. But the benefit is that now you can actually see by file name of backup stored on tape or elsewhere when it was taken... while previously, you would have dozens of file with the same name...
We are looking at possibility to provide a registry key that optionally disables VBK stamping, we will try to put this into next update (no promises, only if it shows it does not brake anything).
Gostev wrote:rsync backup is not a problem, it can be configured to write into the same target file, I attached sample shell script that selects the latest VBK and copies it over to the existing VBK file on target.
Tape backup is not a problem either, see backup naming when using reversed incremental. But the benefit is that now you can actually see by file name of backup stored on tape or elsewhere when it was taken... while previously, you would have dozens of file with the same name...
Gostev, we use deltacopy to rsync towards our NAS.
Deltacopy is a windows based rsync so I doubt that script will help me any further
Well, for Windows you can simply use the referenced PowerShell script with little customization...
I assume deltacopy allows for choosing destination file as well, just like rsync?
Gostev wrote:Well, for Windows you can simply use the referenced PowerShell script with little customization...
I assume deltacopy allows for choosing destination file as well, just like rsync?
Yes, you can choose a destination. But I do not see how I can use this script in our environments.
Well I don't know how I could use Deltacopy or rsync with your PS script to select the latest full backup and merge the incremental differences in the backup dir.
If I check the GUI from deltacopy i can see the run command:
Well, since you are using reversed incremental mode, at any given moment there should be only 1 VBK file.
But even if you have multiple VBK, PowerShell script I have provided actually does select latest backup file (in case of multiple files). You just need to launch this command line above with using the variable the script produces, instead of static file name (for source file).
I'm sorry but I don't think the VEEAM engineers thought this through very well before implementing the .VBK filename change. Seems like many of us are relying on the .VBK filename not changing to move the file to offsite or tape storage.
What Backup Solution to tape you are using? Most of em will let you select files by their age. With rsync i could imagine a command like
rsync -avt `find /blabla -name "*" -type f -mtime -1` /blablabla
should solve it and do what you want.
Drew9k wrote:I'm sorry but I don't think the VEEAM engineers thought this through very well before implementing the .VBK filename change.
We do not disagree with you and we are working on adding a registry key to 5.0.1 to provide you with ability to revert naming behavior to v4 style (no file stamping).
We`re using HP Dataprotector 6.10 to copy the data to tape. It`s not possible to select files based on creation date. We can only filter on filename or extention.
I`m still on version 4.1 because this filename thing is a dealbreaker for copying to tape.
We would like to make a full backup to tape in the weekends, and incremental files on weekdays.
I`d be really pleased to see the possibility to change the way files are named when using forward incremental, so i can either select a specific filename or extention to copy to tape.
Hi AJ83, have you though of simply creating symbolic link (soft link) with post-job script, and naming the forward incremental backup files in any way you want?
then I am sure it should have basic functionality rsync provides, and that is using the same target file for any source file name...
it certainly adds some complexity and brakes existing way of doing things. Well, at least this should allow for more positive effects, than this one negative.
and we are working on adding a registry key to 5.0.1 to provide you with ability to revert naming behavior to v4 style (no file stamping).