Categories
AWS Veeam VMware VMware Cloud on AWS

Monitoring VMC – Part 1

As previously mentioned I have been working a lot with VMware Cloud on AWS and one of the questions that often crops up is around an approach to monitoring.

This is an interesting topic as VMC is technicaly “as a service” therefore the monitoring approach is a bit different. Technically AWS and VMware’s SRE teams will be monitoring all of the infrastructure components,

however you still need to monitor your own Virtual Machines. If it was me I would still want some monitoring on the Infrastructure and I see two different reasons why you would want to do this:

Firstly I want to check that the VMware Cloud on AWS service is doing what I am paying for. Secondly I still need to monitor my VM’s to ensure they are all behaving properly, the added factor is that with a good realtime view of my workload I can potential optimise the number of VMC hosts in my fleet reducing the costs.

With that in mind, I decided to look at a few options for connecting some monitoring tools to a VMC enviroment to see what worked and what didn’t.  I am expecting some things could behave differently as you don’t have true root/admin access as you would usually do.  All of the tests will be done with the cloudadmin@vmc.local account.   This is the highest level account that a service user has within VMC.

The first product that I decided to test was Veeam One.  This made sense for a few reasons:  Firstly I’m a Veeam Vanguard and am very familiar with the product. I also have access to the Beta versions of the v10 products as part of the Vanguard program.

Secondly, it’s pretty easy to spin up a test server to kick the tyres and finally, the config is incredibly quick to implement.

I could have easily added a VMC vCentre to my existing Veeam servers however I choose to deploy a new server just for this testing.  Assuming you have network access between your Veeam One server and the VMC vCentre then adding to Veeam One is straightforward. If not you will need to open up the relevant firewall’s

Once done Veeam performs an inventory operation and returns all of the objects you would expect.   This test was shortly after a VMC environment was created so it doesn’t yet have any workloads migrated to it.  However, as you can see below its correctly reporting on the hosts and VM workloads. It is correctly reporting back that the hosts are running ESXi 6.9.1

I also ran a couple of test reports to check they functioned as expected. Everything seemed to work as I would expect.

In Part two I am going to look at using  Grafana, Influxdb and Telegraf and seeing if this common opensource monitoring stack works with VMC.

Categories
Veeam

VeeamON2020

As everyone knows by now the world has changed possibly forever.  Due to Covid19 working from home has become the new normal.  We are lucky in the IT world that this has been fairly straightforward for most of us.  We are privileged in that it’s possible for us to continue indefinitely.  Organisations still need to move forward, to progress and adapt into the new normal.

In the words of Charles Darwin “It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is most adaptable to change.”

With that most (if not all IT conferences have been postponed or gone online)   Veeam’s annual conference VeeamON is no exception and now it’s here!!

As a Veeam Vanguard I was privileged to be given an early briefing on some of the announcements.  These are summarised below but for all the details make sure you sign up and view some of the great sessions

If you haven’t managed to sign up you still can here.

Headline Announcements

  • Veeam Backup for Office 365 v5

– Microsoft Teams backup

– Modern Authentication

  • Veeam Backup for AWS v2

– Snapshot Replication

– Hybrid Cloud

  • Veeam Availability Orchestrator v3

– Fast recovery using Netapp Snapshots

– DR Pack purchase options

  • Veeam Availablity Suite v11

-Continuous Data Protection.

-Object Storage Enhancements – Capacity Tier now supporting Google Cloud Object Storage

-New Archive Tier- Supporting AWS S3 Glacier

-Instant Reocovery improvements  – Instant NAS & Instant Database recovery.

Last but not least a feature that I have been asking about for over 3 years

 

Yes Veeam Backup Agent for MAC

 

Categories
AWS Veeam VMware

Monitoring VMC – Part 1

As previously mentioned I have been working a lot with VMware Cloud on AWS and one of the questions that often crops up is around an approach to monitoring.

This is an interesting topic as VMC is technicaly “as a service” therefore the monitoring approach is a bit different. Technically AWS and VMware’s SRE teams will be monitoring all of the infrastructure components,

however you still need to monitor your own Virtual Machines. If it was me I would still want some monitoring on the Infrastructure and I see two different reasons why you would want to do this:

Firstly I want to check that the VMware Cloud on AWS service is doing what I am paying for. Secondly I still need to monitor my VM’s to ensure they are all behaving properly, the added factor is that with a good realtime view of my workload I can potential optimise the number of VMC hosts in my fleet reducing the costs.

With that in mind, I decided to look at a few options for connecting some monitoring tools to a VMC enviroment to see what worked and what didn’t.  I am expecting some things could behave differently as you don’t have true root/admin access as you would usually do.  All of the tests will be done with the cloudadmin@vmc.local account.   This is the highest level account that a service user has within VMC.

The first product that I decided to test was Veeam One.  This made sense for a few reasons:  Firstly I’m a Veeam Vanguard and am very familiar with the product. I also have access to the Beta versions of the v10 products as part of the Vanguard program.

Secondly, it’s pretty easy to spin up a test server to kick the tyres and finally, the config is incredibly quick to implement.

I could have easily added a VMC vCentre to my existing Veeam servers however I choose to deploy a new server just for this testing.  Assuming you have network access between your Veeam One server and the VMC vCentre then adding to Veeam One is straightforward. If not you will need to open up the relevant firewall’s

Once done Veeam performs an inventory operation and returns all of the objects you would expect.   This test was shortly after a VMC environment was created so it doesn’t yet have any workloads migrated to it.  However, as you can see below its correctly reporting on the hosts and VM workloads. It is correctly reporting back that the hosts are running ESXi 6.9.1

I also ran a couple of test reports to check they functioned as expected. Everything seemed to work as I would expect.

 

 

In Part two I am going to look at using  Grafana, Influxdb and Telegraf and seeing if this common opensource monitoring stack works with VMC.