DNS is a great technology that everyone uses over internet. How would you reach a given website if you weren’t able to solve its name to the IP address? Would you memorize the public IP addresses of any website you want to reach? No, and with IPv6 coming in the future, DNS will become even more important for internet consumption. But DNS has one drawback: its records are usually static, and if a platform is dynamic and spawn/removes instances on the fly, it needs to have a way to modify the DNS records that are published, so that a non-reachable instances is not even listed.
If you ever tried to do any file operation via the management interface of an ESXi host, like uploading an ISO file or running a backup using Network Mode, you may know the management interface is not running at the full speed of the underlying network interface, and the bandwidth you end up using is only a percentage of the total available. This limit is designed to preserve the availability of the management interface, but still there are situations where this limit is a problem, and you would like to increase it. Hopefully, there’s a solution.
I’ve always been a fan of scale-out storage architecture, I’ve always said that The future of storage is Scale Out, and I’ve spent a fair amount of time studying software-only solutions like Ceph. The new solution from Microsoft, Storage Spaces Direct, seems like another great solution that will be soon available to us, so I decided to test it in my lab.
Ceph Storage can be completely managed and monitored via its command line tools. But, wouldn’t it be better to have a nice interface to see it running, checking its status, and have some performance statistics? Well, yes, and here’s a way to have it, thanks to Ceph Dash.
One year ago, i published a series of 10 blog posts called My adventures with Ceph Storage. As I had recently to rebuild my Ceph cluster from scratch, I decided it was time to create a quick guide to build the cluster as fast as possible.
In 2012 I published a post with a Powershell script to be able to check all the available VM’s in a given vSphere environment, and verify which ones were protected by Veeam Backup & Replication. Time to update the script to make it work with the latest versions of the two software.
Is it better to use real public IP’s or NAT-ed IP’s when publishing Veeam Cloud Connect Replication? Here’s why I think real public IP’s are a better choice.
The best part of the new Veeam Standalone Console is the fact that Veeam PowerShell snap-in installs as part of this component, and it includes a new cmd-let: Connect-VBRServer. YES! No more PowerShell remoting to invoke your Veeam PowerShell scripts.