I had an issue that happened repeatedly with RecoverPoint for Virtual Machines. It usually happened with new VMs that were cloned from templates and/or other VM. When I try to replicate it, I found this error message
When we start a new project, I got the same question from top managers, what is the available capacity in our vSAN cluster? in fact, the hidden question was: what is the raw vs used capacity of the vSAN cluster, and how to plan our project.
I was freaked out when I saw this message. Usually, the vCenter server appliance upgrade process is easy and simple (just next - next - finish). but this time wasn't.…
On July 8th, Runecast announced new -and huge- features included in their 5.1 release. The new updates were expected and if you are familiar with this product, you will definitely see that coming.
A little investigation, I found something called "unassociated vSAN objects". It could happen for many reasons. For example -in my case-, The replication solution I use accidently left those objects.