Gostev wrote:Specifically, changing VBK naming behavior affects two things:
1. Performing active (real) full backup manually or on schedule messes up backup set. The hotfix will disable active fulls altogether when this registry key is enabled, to make sure no one can initiate active full accidentally.
Bunce wrote:Which is a Active Full Backup for reverse-incrementals isn't it?
Bunce wrote:I've just set the existing job to run an Active Full Backup on Tuesday's (today) and am running a backup now... Doesn't seem to be changing the name?
Yuki wrote:I would love to have an ability to set naming schema, at least partially. If i could have the names with a particular string - it would make our backup file off-siting a lot easier since then we could filter based on the name than trying a lot more complex scripts looking at creation date.
Yuki wrote:Maybe something where we can inject a distinct, separate strings into full and incremental.
Please clarify this, because I do not fully understand your request. We do actually allow configuring "base" backup file name in UI today already...
Hmm, so how come different file extensions do not work for you today? File extension is arguably easiest possible method of distinguishing full and incremental backup files, am I not right?
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...
Users browsing this forum: Bing [Bot], Google [Bot], Google Feedfetcher and 16 guests