Comprehensive data protection for all workloads
Post Reply
squirrelly
Novice
Posts: 8
Liked: never
Joined: Apr 14, 2013 6:11 pm
Full Name: Patrick Hurley
Contact:

Warning in Free Version

Post by squirrelly » Apr 14, 2013 6:13 pm

What does this mean?

win-ad-dns-dhcp 67 Warning 11:09:03 PM 11:46:25 PM 120.0 GB 116.0 GB 4.2 GB 0:37:22 Changed block tracking cannot be enabled: one or more snapshots present.

I do have a couple snapshots. Should I delete them for changed block tracking to work with the free version?

Vitaliy S.
Product Manager
Posts: 23001
Liked: 1557 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Warning in Free Version

Post by Vitaliy S. » Apr 14, 2013 8:32 pm

Hi Patrick,

Yes, once you delete existing snapshots on the VMs you're trying to backup, VMware CBT will be enabled for them, however there is no need to do that if you're just using VeeamZIP functionality to backup your VMs. VeeamZIP does not perform incremental backups, you need to use regular backup jobs that are available in full version only.

Thanks!

squirrelly
Novice
Posts: 8
Liked: never
Joined: Apr 14, 2013 6:11 pm
Full Name: Patrick Hurley
Contact:

Re: Warning in Free Version

Post by squirrelly » Apr 15, 2013 4:53 am

yes. thanks. I deleted the snapshots and did not get the warning.

zoltank
Expert
Posts: 225
Liked: 37 times
Joined: Feb 18, 2011 5:01 pm
Contact:

Re: Warning in Free Version

Post by zoltank » Apr 15, 2013 9:29 pm

Why were you keeping one or more snapshots of a server?

Gostev
SVP, Product Management
Posts: 24804
Liked: 3566 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Warning in Free Version

Post by Gostev » Apr 15, 2013 10:45 pm

Common reason is forgetting to delete those after testing/patching... I recommend using Veeam ONE to alert you on presence of abandoned snapshots (this functionality is included in Free Edition as well). Thanks!

zoltank
Expert
Posts: 225
Liked: 37 times
Joined: Feb 18, 2011 5:01 pm
Contact:

Re: Warning in Free Version

Post by zoltank » Apr 16, 2013 1:03 pm

Unless there's a very good reason to keep snapshots around, they should be removed as soon as possible. You're inviting a host of issues keeping them around. They can not only compromise the performance of the VM, they can also causes issues trying to commit, and in a worse case scenario they can cause the datastore to run out of space and cause data corruption (ask me how I know). If you don't have Veeam ONE you can set vCenter to alert when a VM is running on a snapshot:
http://kb.vmware.com/selfservice/micros ... Id=1018029

Also, here are VMWare's best practices regarding snapshots:
http://kb.vmware.com/selfservice/micros ... Id=1025279

Post Reply

Who is online

Users browsing this forum: Baidu [Spider] and 15 guests