Discussions specific to the VMware vSphere hypervisor
Post Reply
Yuki
Veeam ProPartner
Posts: 252
Liked: 26 times
Joined: Apr 05, 2011 11:44 pm
Contact:

Data processing and CBT use

Post by Yuki » Jan 28, 2013 6:10 pm

1) our file server is 10TB with 3.1TB of actual data. During a full backup with CBT the job reports
VM Size: 9.8TB (3.1TB used)
Processed: 4.9TB
Read: 4.9TB
Transfered: 2.7TB


Any particular reason why Veeam would process 2.2TB more data than on the actual machine? We have not deleted 2.2TB of data - this a new file server and we are still moving files to it.

2) One of our VMs is no longer been processed with CBT. This is true for just one vm across all jobs. Verified CBT is enabled for the job and on VM in ESXi. It used it on previous day's runs, but not last one.

Yuki
Veeam ProPartner
Posts: 252
Liked: 26 times
Joined: Apr 05, 2011 11:44 pm
Contact:

Re: Data processing and CBT use

Post by Yuki » Jan 28, 2013 7:21 pm

I think the second issue may be due to Source and Target proxies being the same VM. Both the proxy VM and the server are on the same host.

we are backing up VM1 and in the job we see:
Using source proxy VM2 [hot-add]
Using target proxy VM2 [nbd]

Incremental backups that normally take 20 minutes will not stretch to 4-5 hours as it's reading the entire disk.

foggy
Veeam Software
Posts: 17116
Liked: 1399 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Data processing and CBT use

Post by foggy » Jan 30, 2013 1:47 pm

Yuki wrote:Any particular reason why Veeam would process 2.2TB more data than on the actual machine? We have not deleted 2.2TB of data - this a new file server and we are still moving files to it.
This is the amount of blocks reported as changed by VMware CBT (not zero ones) so Veeam B&R should read them all to define whether to back them up or not.
Yuki wrote:2) One of our VMs is no longer been processed with CBT. This is true for just one vm across all jobs. Verified CBT is enabled for the job and on VM in ESXi. It used it on previous day's runs, but not last one.
This is not connected with the fact that source and target proxies are installed on the same VM. Job logs should be reviewed to identify the reason of CBT not being used during the job run.

Also, we appreciate creating separate threads for different issues so that we could assist you more efficiently and to facilitate things for further readers.

Post Reply

Who is online

Users browsing this forum: No registered users and 21 guests