Lately, different bugs involving VMware CBT in vSphere 6 have created some justified concerns among users. But there are ways to guarantee successful backups even in these conditions.
One of the features coming in Veeam Backup & Replication v9 is per-VM backup chains.This great addition was in between a general announcement related to other backup storage improvements; in case you missed it, here we go with a dedicated post, because this feature is going to be great!
vSphere tags are incredibly powerful objects, that can be used in many and amazing ways. One of the possible use cases for tags is Data Protection. Veeam supports vSphere tags in both vSphere 5.5 and 6.0, and with them you can create advanced policy-based data protection rules.
A new species of Backup Repository is coming from Veeam: Scale-Out Backup Repository. With it, users will be able to simplify backup job management, improve backup performance, and spend less on backup storage. Veeam’s new Scale-out Backup Repository delivers these benefits by providing an abstraction layer over individual storage devices, effectively creating a single virtual pool of backup storage to which you can assign backup jobs, and offering the freedom to easily extend capacity as needed by simply adding additional storage devices into the existing pool.
When you have to deal with a large environment and several jobs in Veeam, automation via powershell is the only possible solution.
In powershell, in order to use credentials to authenticate against different systems you have different options. When running scripts interactively, we can configure the powershell command to ask us for username and password, but saving passwords in clear text into a script is a bad security practice. Powershell however has a way to hide passwords in commands and scripts.
During the just concluded VMworld 2015, EMC released a VSA named VVols Tech Preview to help people to test this technology in their labs. I was just waiting for the first vendor to offer the possibility to easily test VVOLs capabilities, so thanks to EMC for this. Time to deploy it in my lab!
I’ve waited a week after VMworld ended in San Francisco before writing this post: there were too many blog posts from every blogger trying to cover any new announcement like a newspaper, and with the addition of news collected directly from the Expo Floor, sessions I’ve attended and other sources, the amount of info to digest required a bit of time. This post is not a recap of the event, just the things that I’ve seen and I found interesting. If something is not here, it may be that I’ve missed it rather than don’t liking it.