As we continue along the Veeam v9 VMCE Study Guide its time to finish off Module 3 and have a look at Veeam ONE. For me I don’t have a lot of experience with Veeam ONE so this will be a session I try to focus on throughout this guide! Just an update, I’ve written and passed my VMCE at this point, so there’s that! Yay! Either way I’m going to try to complete any unfinished portions I have in efforts of completeness! So with that, let’s get going… Veeam ONE relies heavily on a client-server architecture to work. The architecture of Veeam ONE contains the following components.
Veeam ONE Server
- The Veeam ONE Server is responsible for gathering all of the data from our virtual environment, vCloud Director and Veeam Backup & Replication servers. It takes this data and stores it into its SQL database. Veeam ONE server has a couple of sub components that are broken out as well
- Monitoring Server
- Handles the collection of data to present to the Monitor client or web ui.
- Pulls data from both VMware and Hyper-V as well as Veeam Backup & Replication.
- Reporting Server
- Provides a set of dashboards and predefined reports.
- Verifies configuration issues
- Track implemented changes in the environment
- Adhere to best practices and optimize your environment
- Capacity Management
- Monitoring Server
Veeam ONE Monitor Client
- The Monitor client connects to the monitoring server and basically monitors your virtual environment. This allows us to choose our connections to our virtual servers, our backup infrastructure, and manage alarms and data that is being monitored.
Veeam ONE Business View
- Allows grouping of infrastructure objects into categories that better align to the business
- Groupings/categories are applied to functionality within Monitor and Reporter
- Can be synchronized with vSphere tags.
Interesting tidbits in regards to Veeam ONE
- Can be licensed either per socket or per-VM being monitored
Deployment Models
Veeam ONE provides us with a couple different deployment models
Typical Deployment
Just as VBR gives us the opportunity to consolidate all of the components and services on to one server Veeam ONE does as well. The typical deployment takes Veeam ONE server, Web UI, and Monitor client and installs them all together on the same machine, be it physical or virtual. The SQL instance can also be installed on this machine as well – by default, Veeam ONE packages with SQL 2012 Express. This is a good way to manage a small environment, or to evaluate what Veeam ONE can do for you. If you need to enable multi-user access to the real-time performance it is possible to install the Veeam ONE monitor client on separate machines.
Your typical installation requires at least 4 cores, 64 bit and 8GB of RAM, although 16 is recommended. Must be installed on Windows 7 sp1 or above, and supports SQL, both full and express, from 2005 and up.
Advanced Deployment
The advanced deployment starts to break out some of the individual components to different servers. The Veeam ONE Server, and the WEB UI components are installed on separate machines. Also, Veeam ONE Monitor client can also be installed on multiple separate machines. This deployment can still use the express installation of SQL, however since you are most likely breaking out the components in order to decrease load, you will probably want to install a remote instance of SQL server for this type of setup.
The Veeam ONE server requires at least 4 cores, 64 bit, and 8 GB of RAM, although 16 is recommended. Again, Windows 7 sp1 or above and SQL 2005 and up.
The Web UI server requires minimum 2 cores and only 64 bit OS’s (Win 7 SP1 and up). 2 GB minimum RAM
The Monitor Client requires either 32 or 64 bit OSs (7 SP1 and up) and only 1 socket, along with 1 GB of memory.
Interesting tidbits around Veeam ONE deployments
- Supports vSphere 4.1 and above
- Supports Hyper-V 2008 R2 sp1 and above
- Supports vCloud Director 5.1 and above
- Integrates with Veeam B&R 7.0 update 4 and above (standard and above)
