Hi,
Does Veeam share CBT data between backup jobs? Or would it be different for each backup job?
We had a VMserver crash, and so all CBT data is invalid.
Some of the VM's on the server are backed up / replicated in a number of different jobs, and the first time each job ran it had to re-read the entire VMDK. I expected this for the first job, but I thought it wouldn't be needed for any further jobs?
As I am typing, part of me thinks that the CBT data would be per job, as it is tracking changes between job runs, and is correct only for a particular "point in time".
Just thought I'd ask, as I am not sure
Thanks,
Mike
-
- Novice
- Posts: 6
- Liked: never
- Joined: Apr 17, 2014 7:04 pm
- Full Name: Michael Goodwin
- Contact:
-
- VP, Product Management
- Posts: 27377
- Liked: 2800 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Share CBT data between backup jobs?
Hi Mike,
CBT data is stored per job, cause these jobs can have different schedule, VMs etc.
Thanks!
CBT data is stored per job, cause these jobs can have different schedule, VMs etc.
Thanks!
-
- VeeaMVP
- Posts: 6166
- Liked: 1971 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
- Contact:
Re: Share CBT data between backup jobs?
CBT infos are not stored by Veeam, but they are in the vSphere environment, specifically in the same folder of the vmx configuration file, in a dedicated file. Veeam read those info during an incremental run.
If CBT for any reason has to be reset, no matter what's the history of the VM in previous job runs, the first job hitting the VM after a CBT reset has to read again the virtual disk as there's no CBT information anymore.
CBT is like a change log for vmdk blocks, and it's read by any job accessing the same VM. There's no issue in having multiple jobs accessing the same VMs.
If CBT for any reason has to be reset, no matter what's the history of the VM in previous job runs, the first job hitting the VM after a CBT reset has to read again the virtual disk as there's no CBT information anymore.
CBT is like a change log for vmdk blocks, and it's read by any job accessing the same VM. There's no issue in having multiple jobs accessing the same VMs.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Principal EMEA Cloud Architect @ Veeam Software
@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Who is online
Users browsing this forum: Bing [Bot] and 63 guests