-
- Enthusiast
- Posts: 94
- Liked: 1 time
- Joined: Dec 06, 2010 10:41 pm
- Full Name: CARLO
- Contact:
Veeam backup proxy detected, changed block tracking is disab
Hi,
why i have a log "Veeam backup proxy detected, changed block tracking is disabled" for a VM that ISN'T a v6 PROXY? This happens in a replica job that starts after (many hours) a backup job of the same VM. This happends every day.
This don't happens if i start another session of the relica job again.
Thanks,
Carlo
why i have a log "Veeam backup proxy detected, changed block tracking is disabled" for a VM that ISN'T a v6 PROXY? This happens in a replica job that starts after (many hours) a backup job of the same VM. This happends every day.
This don't happens if i start another session of the relica job again.
Thanks,
Carlo
-
- Chief Product Officer
- Posts: 31753
- Liked: 7257 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
Hi Carlo, please open support case and have them investigate the logs to see why VM is being detected as Veeam backup proxy. Thanks!
-
- Enthusiast
- Posts: 94
- Liked: 1 time
- Joined: Dec 06, 2010 10:41 pm
- Full Name: CARLO
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
Hi Gostev,
mi support case ID is 5180520
Thanks,
Carlo
mi support case ID is 5180520
Thanks,
Carlo
-
- Influencer
- Posts: 10
- Liked: 1 time
- Joined: May 02, 2011 10:40 pm
- Full Name: Eric Siedentopf
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
What was the resolution on this. I just seen this in my log even thought it used CBT.
Code: Select all
11/2/2012 1:20:06 PM :: Queued for processing at 11/2/2012 1:20:06 PM
11/2/2012 1:20:07 PM :: Required resources have been assigned
11/2/2012 1:20:08 PM :: VM processing started at 11/2/2012 1:20:08 PM
11/2/2012 1:20:08 PM :: VM size: 18.0 GB
11/2/2012 1:20:08 PM :: Veeam backup proxy detected, changed block tracking is disabled.
11/2/2012 1:20:35 PM :: Using source proxy VW-CIT1 [hotadd]
11/2/2012 1:20:38 PM :: Using target proxy VMware Backup Proxy [hotadd]
11/2/2012 1:20:38 PM :: Discovering replica VM
11/2/2012 1:20:38 PM :: Preparing replica VM
11/2/2012 1:20:57 PM :: Preparing guest for hot backup
11/2/2012 1:21:04 PM :: Creating snapshot
11/2/2012 1:21:08 PM :: Releasing guest
11/2/2012 1:21:16 PM :: Processing configuration
11/2/2012 1:21:24 PM :: Creating helper snapshot
11/2/2012 1:21:27 PM :: Hard Disk 1 (15.0 GB)
11/2/2012 1:22:45 PM :: Hard Disk 2 (3.0 GB)
11/2/2012 1:23:21 PM :: Deleting helper snapshot
11/2/2012 1:23:34 PM :: Removing snapshot
11/2/2012 1:23:57 PM :: Swap file blocks skipped: 19.5 MB
11/2/2012 1:23:57 PM :: Finalizing
11/2/2012 1:24:06 PM :: Busy: Source 38% > Proxy 93% > Network 6% > Target 57%
11/2/2012 1:24:06 PM :: Primary bottleneck: Proxy
11/2/2012 1:24:07 PM :: Processing finished at 11/2/2012 1:24:06 PM
-
- VP, Product Management
- Posts: 27347
- Liked: 2785 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
Hi Eric, what is the VM in question? Proxy server?
-
- Influencer
- Posts: 17
- Liked: 3 times
- Joined: Dec 11, 2012 9:11 pm
- Full Name: Luigi Rosa
- Location: Italy
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
Just had this issue with a Veeam 9 upgraded from 8.
The VM is a 2003 Server.
Solved by resetting CBT as per Veeam KB 1113 https://www.veeam.com/kb1113
The VM is a 2003 Server.
Solved by resetting CBT as per Veeam KB 1113 https://www.veeam.com/kb1113
-
- VP, Product Management
- Posts: 27347
- Liked: 2785 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam backup proxy detected, changed block tracking is d
Luigi, do you say that you had a warning message that this VM is a proxy server or just CBT cannot be used message? The KB you've referenced in the post refers only to the second case (just don't want other community members be confused)
Who is online
Users browsing this forum: Google [Bot] and 42 guests