Is there a way to force more than one synthetic full per day

[ian0x0r]

Hi,

Is there a way to force more than one syntehtic full backup on an incremental job per day. For example, If I was to run an incremental job every hour, with 3 recovery points, I will end up with 24 VIB's before the next days syntehtic full backup runs. It would be useful if the syntehtic full could be scheduled more regularly.

Sorry if ive overlooked a topic about this already, I couldnt find anything specifically about this though.

Thanks

Ian

[foggy]

Ian, currently there's no way to perform synthetic fulls more often than daily.

[ThomasMc]

PowerShell?

Code: Select all

Get-VBRJob | WHERE {$_.name -eq "JobToRun"} | Start-VBRJob -FullBackup

[ian0x0r]

Does that perform an active full or a synthetic full though? An active full does not seem to remove the incremental chain.

Thanks for suggestion.

Ian

[ThomasMc]

Does that perform an active full or a synthetic full though? An active full does not seem to remove the incremental chain.

Thanks for suggestion.

Ian

Sorry Ian, I wouldn't know just floating the idea

[foggy]

Right, this will trigger an active full, not a synthetic one.

[ThomasMc]

Right, this will trigger an active full, not a synthetic one.

Well that takes care of that then

[Sethbartlett]

If you are wanting to keep a retention policy like 3 points and doing multiple runs per day or even running daily, your best bet would usually be reversed incremental then. It will do the synthetic basically every run and keep your retention policy at 3.

[ian0x0r]

Reversed incrementals are good, however this was for a crazy scenario where the VBK file is 1TB, but the VIB's were maybe 1Gig. Was looking to take changed data off site over WAN link during the day, and then probably the full VBK during the evening. This was going to work on a time stamp basis. If I did it with reverse incremental, then it would try and copy the 1TB vbk every time :/.

No worries though, think im going to do it a different way now. Was curious to see if you could force the incremental chain rollup TBH.

Thanks for help as always.

Ian

[Vitaliy S.]

Hi Ian, what were you planning to use as an offsite replication tool? Have you considered using reversed incremental backup mode + rsync to send changed blocks only?

[ian0x0r]

Hi Ian, what were you planning to use as an offsite replication tool? Have you considered using reversed incremental backup mode + rsync to send changed blocks only?

So does this still work if the name of the VBK is changing when the reverse incremental runs? Do you need to hard code the name somehow?

Thanks,

Ian

EDIT: Just been looking through the forums, ive seen how you do this now. Now for the silly part. COuld this be used to copy the changes from VBK and ALSO maintain a VRB reverse incremental chain? So copy block changes from VBK and copy VRBs? Is the name of the VBK file going to break the reversed incremental chain?

Thanks

[Vitaliy S.]

I don't think you need to do that, basically the rsync script should look like this.

[ian0x0r]

Thats the topic I looked at


The only reason I was looking to also copy the VRB's was to have the ability to roll back more than the latest reversed incremental VBK. I know what I am asking for is essentially Veeam replication , but syncing backups instead.

Thanks for help,

Ian

[Vitaliy S.]

Is the name of the VBK file going to break the reversed incremental chain?

I don't think it is going to break anything. There is no hardcoded reference to the VBK file name when you import the backup chain to the Veeam console.