Discussions specific to the VMware vSphere hypervisor
- Posts: 50
- Liked: 2 times
- Joined: Feb 10, 2011 7:27 pm
I had to re-do a replication job containing one vm. It has a large secondary disk that i've excluded, however the job still processes that disk. What might I have over looked? The disk exclusion configuration process is really simple and i've not had this problem before. The second disk got replicated and filled up the target datastore causing all sorts of problems.
It is a Windows Server 2008 R2 vm with vmtools running and App-aware processing off and the Veeam version is 126.96.36.1991. Thanks for any ideas.
- Product Manager
- Posts: 18785
- Liked: 1889 times
- Joined: Oct 26, 2012 3:28 pm
- Full Name: Vladimir Eremin
Did you create a new replication job from scratch and specify disk exclusions again (the exact same way that you'd done before)? If so, the described behavior looks unexpected, and you'd better contact our support team and let them investigate it directly. Thanks.
Users browsing this forum: Bing [Bot] and 25 guests