Veeam: VBRCatalog is already in use by another share


Today I was trying to upgrade a test Veeam server with a Veeam v5 deployment to the latest v6.1 release. I used the following KB article to perform the upgrade KB1363. But when I tried to install the v6.1 software I got the following warning message:

image

I think this ‘issue’ is some legacy stuff from moving the VBR catalog to another location. If you want to know how you can move the VBRCatalog to a different partition. Just read my previous post Winking smile.

To fix this ‘issue’ just remove the file share:

image

Now you’re good to go. Just restart the setup wizard and install version 6.1 and have fun.

Host Profiles: Ruleset xxxx doesn’t match the specification


Today I was testing Host Profiles (again) and I must say it works a lot better than during my previous tests. There was only one thing very annoying during my tests. When the host was in maintenance mode, I applied the Host Profile and performed a check. Everything was OK and the host was compliant.  But when the host was out Maintenance mode and I checked if the host was still compliant, I received the following message:

image

Unfortunately there’s no knowledgebase article which describes those messages so I started to Google and found a post on the VMware Communites by khushal: http://communities.vmware.com/message/1357268

1. Open vCenter go to Home — > Management –> Host Profiles

2. Right Click on the Host Profile you are using for your Cluster and Select Edit

3. Expand the profile Profile

– Profile-name

– Firewall configuration

*     – Ruleset Configuration*

*     – faultTolerance*

       Select Ruleset and check the checkbox in right hand “*Flag Indicating whether ruleset should be enabled”

Click OK.

and check Compliance again in Cluster.

To fix the annoying messages I did change the aam and faultTolerance settings via:

Continue reading “Host Profiles: Ruleset xxxx doesn’t match the specification”