Veeam v8 Install With NetApp Config

Veeam has released v8 of it’s Backup and Replication software. As a long time Veeam user this is a release I have been waiting for. Previously, Veeam had released support for storage snapshots on HP storage arrays, but with my environments being primarily NetApp over the last few years I wasn’t able to take advantage. Now in v8, we can restore and backup directly from snapshot. This speeds up the process and limits the impact on the Virtual Machines in the environment.

This guide walks you through a brand new installation of Veeam Backup & Replication v8 on Server 2012 and how to add your NetApp storage array as an object to browse existing snapshots. This is a high-level guide and in the future I’ll do a more in-depth backup/restore from Storage. For my guide on installing Veeam v7 with Windows 2012 R2 Data Deduplication, click here.

If you’re not interested in a custom SQL Express installation as well, pick up the guide at step 15. Steps 1-15 show how to install SQL Express to the secondary drive to prevent growing databases from affecting the main OS partition.

Prerequisites:

1. Dedicated server for installing Veeam
2. License file for Veeam (copied out to the server)
3. Latest version of Veeam v8 downloaded and mounted on the server (the installer is in an .ISO)
4. A service account for running the Veeam services (Optional, but my preferred method)
5. Username/password with admin rights to vCenter
6. Username/password for NetApp array (for this post I’ll be using the ‘root’ account)

Steps:

1. Right click the DVD drive and click “Open”
veeamv8111714-step1
2. Navigate to Redistr -> x64. Locate SQLEXPRx64.exe, right click and choose “Run as administrator”
veeamv8111714-step2
3. Click “Yes” to run the installer if prompted
veeamv8111714-step3
4. Under the “Installation” section, click “New SQL Server stand-alone installation”
veeamv8111714-step4
5. Click the check box for “I accept the license terms” and decide if you want to send feature usage data to Microsoft then click “Next”
veeamv8111714-step5
6. Ensure the check box for “Include SQL Server product updates” is checked and click “Next”
veeamv8111714-step6
7. Updates and setup files will install…
veeamv8111714-step7
8. Choose the features to install (Database Engine Services is the only thing required). Choose the install directory (I always choose the secondary drive of the machine and click “Next”
veeamv8111714-step8
9. Choose a name for the instance or leave as default (SQLExpress), choose the instance root directory (secondary drive again) and click “Next”
veeamv8111714-step9
10. Enter a service account for running the SQL DB engine (or leave it as local system) and click “Next”
veeamv8111714-step10
11. Choose “Mixed mode” for the authentication type then enter a password for the “sa” account (Immediately save this password somewhere). Choose the groups/users that will be SQL Server administrators
veeamv8111714-step11a

a. Be default, only users/groups added here will have access to the Veeam console. If you don’t want to grant permissions to the SQL instance, you can grant access to these users/groups for the Veeam database after it has been created

12. Click on the “Data Directories” tab and ensure all the directories are pointing to the secondary drive and click “Next”
veeamv8111714-step12
13. Choose whether to send error reports and click “Next” and the installation will begin
veeamv8111714-step13
14. Once the installation completes, click “Close”
veeamv8111714-step14
15. Close the “SQL Server Installation Center” window. Navigate back to the root of the DVD drive. Right click on “Setup.exe” and choose “Run as administrator”
veeamv8111714-step15
16. Click “Yes” to run the installer if prompted
veeamv8111714-step16
17. Click “install” for “Veeam Backup & Replication”
veeamv8111714-step17
18. Click “Next”
veeamv8111714-step18
19. Read and accept the license terms and click “Next”
veeamv8111714-step19
20. Click “Browse” and locate your license file then click “Next”
veeamv8111714-step20
21. Choose the features to install and the install directory then click “Next”

a. To install to a different location (like a secondary drive), the folders need to be created ahead of time
veeamv8111714-step21

22. If any features are missing, click “Install”
veeamv8111714-step22
23. Once the system configuration check passes, click “Next”
veeamv8111714-step23
24. Review the default configuration and if no changes need to be made, click “Install”
veeamv8111714-step24
25. Once the install completes, click “Finish”
veeamv8111714-step25
26. Close the setup window and restart the server
27. After the server finishes rebooting, login and view the services to ensure the Veeam and SQL services that are “Automatic” have started
veeamv8111714-step27
28. Open “Veeam Backup & Replication”
veeamv8111714-step28
29. Click “Managed servers” on the left side and then click “VMware vSphere”
veeamv8111714-step29
30. Enter the name or IP of the vCenter Server and click “Next”
veeamv8111714-step30
31. Click the “Add” button and then enter the username/password of an account with permissions on the vCenter server. Click “OK” then click “Next”
veeamv8111714-step31
32. Click “Finish”
veeamv8111714-step32
33. To add your NetApp storage systems to Veeam, click on “Storage Infrastructure” and then click the “Add Storage” button
veeamv8111714-step33
34. Click “NetApp Data ONTAP”
veeamv8111714-step34
35. Enter the Name or IP of the storage system and click “Next”
veeamv8111714-step35
36. Click “Add” to add credentials to connect to the NetApp then choose the protocol and port. Click “Next”
veeamv8111714-step36
37. If the name/IP and credentials work, click finish and discovery of VMs and LUNs/Volumes will begin.
veeamv8111714-step37
38. Once storage and VMs have been discovered, click “Close”
veeamv8111714-step38
39. In the “Storage Infrastructure” view, expand “NetApp”, then the storage system. Choose a volume with virtual machines and current volume snapshots. Expand the volume, choose a snapshot and see what VMs are inside.
veeamv8111714-step39

a. From this view you can delete existing snapshots, create new storage snapshots, and rescan the volume for new snapshots. At the VM-level, you can instantly recover the VM from snapshot, restore guest-OS files, and even restore objects from Active Directory, Exchange, SQL or SharePoint.
veeamv8111714-step39a

40. Click on “Backup & Replication” then expand “Backups” and click on “Storage snapshots.” You’ll see a list of all the volumes that have snapshots, what VM’s are in those snapshots, and how many restore points are available.
veeamv8111714-step40

This is the basics of installing Veeam v8 and connecting to your vCenter Server and NetApp Storage. The process is incredibly simple and like every else from Veeam it just works. In the future I intend to add more restore scenarios such as application item recovery and VM recovery from storage snapshots.

vCenter Orchestrator Install and Config

I have wanted to get started with vCO for awhile now, but I have not had much of use for it. Justifying the time to deploy and learn a new tool when you don’t have a glaring need for it proves tricky, but recently I was able to carve out some time to learn. One of the biggest hurdles was finding step-by-step deployment guide that worked so I decided to document this process.

The following documentation is for installing the vCenter Orchestrator (vCO) Appliance v5.5.1 with an already deployed vCenter 5.5 server (vCSA in my case). The appliance allows you to run vCO without installing it on a dedicated Windows Server.

1. Search for VMware-vCO-Appliance and download the latest version (VMware-vCO-Appliance-5.5.1.0-1617225_OVF10.ova for this writing)
VCO080414-step1
2. Accept the license terms and save the file locally
3. Connect the vSphere client to your vCenter Server then choose File -> Deploy OVF Template
VCO080414-step3
4. Click the “Browse” button, locate the .OVF downloaded previously and click “Open” then click “Next”
VCO080414-step4
5. Review the template details and click “Next”
VCO080414-step5
6. Accept the license agreement and click “Next”
7. Choose a name and location for this appliance and click “Next”
VCO080414-step7
8. Choose a datastore for the appliance and click “Next”
VCO080414-step8
9. Choose the appropriate disk format (I prefer thin provisioned) and click “Next”
VCO080414-step9
10. Choose the appropriate Destination Network (VM Port Group) and click “Next”
VCO080414-step10
11. Enter passwords for both the root user of the appliance and the password for the configuration interface (‘vmware’ is the username)
VCO080414-step11

  • Enter the Hostname, gateway, DNS, IP and subnet mask for the appliance and click “Next”
    VCO080414-step11a

12. Review the details of the configuration and then click “Finish”
VCO080414-step12
13. Once the appliance has been deployed successfully, click “Close”

VCO080414-step13
14. Right click on the appliance and choose “Open Console”
VCO080414-step14
15. Click the Power button to turn on the VM
VCO080414-step15
16. Boot to “VMware vCenter Orchestrator Appliance”
VCO080414-step16
17. Note the URLs for each function
VCO080414-step17
18. Open a web browser and connect to the URL for Orchestrator Configuration (Port 8283)
19. Login with the username “vmware” and the password entered for the vCO configuration during appliance deployment
VCO080414-step19
20. Click on “Network”
VCO080414-step20
21. Change the “IP address” to the IP used to access vCO and click “Apply changes” in the bottom right corner
VCO080414-step21
22. Click the “SSL Trust Manager” tab, enter the IP or hostname of your vCenter server and click “Import”
VCO080414-step22
23. Once the cert information is displayed, click the “import” link
VCO080414-step23
24.Repeat this process again, this time importing the certificate for SSO. Enter the FQDN of the SSO server with port 7444 and click “Import” then “Import” again once the certificate details are displayed
VCO080414-step24new
25. Click on “Authentication” to configure user access

VCO080414-step24
26. For this writing we will use the SSO Authentication method, so change Authentication mode to “SSO Authentication” and click “Advanced settings”
VCO080414-step25
27. Enter the Token and Admin service URLs, the SSO admin username and passwords. Click “Register Orchestrator”

  • Token service URL: https://vCenterIPaddress:7444/ims/STSService
  • Admin service URL: https://vCenterIPaddress:7444/sso-adminserver/sdk
  • Admin user name: administrator@vsphere.local
  • Admin password: Password for admin account
    VCO080414-step26d

28. Once registration completes, choose the vCO Admin – domain and group from the list (These are populated based on your SSO config). Click “Accept Orchestrator Configuration”
VCO080414-step27
29. Click on “Startup Options”
VCO080414-step28
30. Click “Restart the vCO configuration server”
VCO080414-step29
31. Log back in once the server has finished restarting and click “Licenses”
VCO080414-step30
32. Choose “Use vCenter Server license” and enter the host name of the vCenter server, port should be 443, path is /sdk, and for username and password I used the SSO admin. Click “Apply changes” towards the bottom right of the screen
VCO080414-step31
33. Click on “vCenter Server (5.5.1)”
VCO080414-step32
34. Click “New vCenter Server Host” and enter the hostname of the vCenter server, port is 443, path is /sdk, I chose “Session per user” and the username and password for the SSO admin account. Click “Apply changes”
VCO080414-step33
35. Click on “Mail (5.5.1)”
VCO080414-step34
36. Click the check box for “define default values” and enter in the following information and click “Apply changes”

  • SMTP host: The address for your mail server
  • SMTP Port: Usually 25
  • Username and password: If your mail server requires authentication
  • From name: Name that vCO emails will appear from
  • From address: Email address that vCO emails will appear from
    VCO080414-step35e

37. Open a new browser window/tab and navigate to https://vCOIPaddress:8281/vco/client/client.jnlp to access the Java web client for vCO. Login as user that is a member of whatever group was chosen in step 27 as a vCO Admin
VCO080414-step36

  • At first this did not work and kept reporting “No vCO license available” when I attempted to login. After restarting the service and configuration server through the web interface, I ended up restarting the vCO appliance within vCenter and then I was able to login without issue

38. At this point you’re all setup and ready to start creating workflows
VCO080414-step37
 

Veeam 7.0 Install on Windows 2012

Veeam Backup & Replication is one of my favorite piece of software I get to work with. I’ve been working with B&R since 2010 (v5) and it has always been easy to install, easy to configure, and quick to start taking backups and protecting my environment. And that is just the software, the company itself is even better. Their support forums are full of employees and users that are knowledgeable and quick to help. The best way to describe Veeam is a company that is on your side as an Administrator. They listen to their community, their users, their customers and are developing solutions that make our jobs easier.

The following guide walks you through installing SQL Express, Veeam, connecting to vCenter 5.5 and configuring deduplication for a secondary drive on Windows Server 2012 R2. I have a preference for installing all software to a secondary drive instead of the OS (C:\) drive so this documentation shows how to install each component to that secondary drive in the event you have the same preference as me.

Veeam’s site contains best practices regarding backup types, sizing of your Veeam server, deduplication recommendations, and everything else that goes into the planning of your Veeam Backup & Replication deployment. This guide is more just to show how to configure the components and an example of what I’m seeing for deduplication rates.

 

Prerequisites:
1. Windows Server 2012 R2 patched, joined to domain, with 2 additional drives (one for Veeam to be installed on and the other for backup data)
2. A user or group defined for Veeam administrators (required when doing a standalone SQL Express install in order to use Veeam, the service account used to run veeam must be a member of this group or added as a SQL Administrator in step 8)
3. A domain user account with admin rights to the vCenter server
4. Mount the Veeam B&R ISO
5. Turn off User Account Control (SQL Express install will fail without this)

Install:
1. Open “This PC”, located the Veeam disc, right click and choose “Open”
veeam7061614-step1
2. Browse to “Redistr\x64”, locate and double-click on “SQLEXPR_x64_ENU.exe”
veeam7061614-step2
3. Once the “SQL Server Installation Center” windows appears, click on “New installation or add features to an existing installation”
veeam7061614-step3
4. Accept the license terms and click “Next”
veeam7061614-step4
5. After Setup Support Files are loaded the SQL Server 2008 R2 Setup window will appear. Choose the features you’ll need (just Database Engine Services usually), change the Directories to the secondary drive (D:\ for this writing) and click “Next”
veeam7061614-step5
6. Enter the name of the instance and change the root directory to the secondary drive and click “Next”
veeam7061614-step6
7. You can run the SQL database engine as Network Service, but I prefer running as a named service account. Enter the domain\username, password, and click “Next”
veeam7061614-step7
8. Choose “Mixed Mode” for authentication type. Enter the “sa” password and immediately save it somewhere.
veeam7061614-step8

  • a. For “SQL Server administrators”, only users/groups added here will be able to open and run Veeam. Add all users that will need to access Veeam or create a group.
    veeam7061614-step8a
  • b. Click “Data Directories” tab and ensure all the directories are pointing to the secondary drive and click “Next” (For organization I prefer to create folders for each file, but it isn’t necessary)
    veeam7061614-step8b

9. Choose if you want to send error reports to Microsoft and click “Next”
veeam7061614-step9

  • a. Install will now begin to run

10. Once Installation completes, click “Close”
veeam7061614-step10
11. Navigate back to the root of the disc drive then locate and run “Setup.exe”
veeam7061614-step11
12. Click on install for “Veeam Backup & Replication”
veeam7061614-step12
13. Click “Next” through the initial setup screen
veeam7061614-step13
14. Read and accept the license agreement and click “Next”
veeam7061614-step14
15. If you have a license key add it now, otherwise click “Next”
veeam7061614-step15
16. Choose the program features to install. Click “Browse” button to change the installation to the secondary drive (you will have to make a new Folder name “Veeam” followed by “Backup and Replication” inside of it). Click “OK” then click “Next”
veeam7061614-step16
veeam7061614-step16-2
17. If any of the components that are required show a status of “Failed”, click the “Install” button
veeam7061614-step17

  • a. Once the installation completes the status will change to “Passed” then click “Next”
    veeam7061614-step17a

18. Enter the domain\username and password of the account Veeam will use to access vCenter and click “Next”
veeam7061614-step18

  • a. This user should be a local administrator on the server running Veeam or you’ll receive this message
    veeam7061614-step18a

19. Choose “Use existing instance of SQL Server”, select the Server\Instance and then enter a name for the Veeam database. Click “Next”
veeam7061614-step19

  • a. If the domain\veeam account isn’t in the Veeam Admins group, you will receive the following error that the user account “lacks CREATE ANY DATABASE permission”
    veeam7061614-step19a

20. Note the ports for Backup service and Catalog service and click “Next”
veeam7061614-step20
21. Change the “vPower NFS” directory to the secondary drive by clicking “Browse”, then navigate to the D:\Program Files\Veeam\Backup and Replication” then create a new folder inside named “NfsDatastore” and click “OK”.
veeam7061614-step21

  • a. For Guest file system catalog, click Browse and create a new folder named “VBRCatalog” under the D:\ drive. Click OK then “Next”
    veeam7061614-step21a1
    veeam7061614-step21a2

22. Review the configuration and then click “Install”
veeam7061614-step22
23. Once installation completes, click “Finish”
veeam7061614-step23
24. Now that Veeam is installed, let’s upgrade it to the latest patch. On Veeam’s website, download the latest patch for the version you’re running (Patch 4 for this writing) and copy it out to the server running Veeam.
25. Run the executable for this patch
veeam7061614-step25
26. Click “Next” through the first screen of the patch wizard
veeam7061614-step26
27. Click “Install” to begin the installation
veeam7061614-step27
28. Once the patch is installed, click “Finish”
veeam7061614-step28
29. Now that Veeam is installed and fully patched, locate Veeam Backup & Replication and open
veeam7061614-step29
30. You will receive a message about components that need to be updated (vPower NFS, Transports, Installer, etc). Click the check box next to the server and click “Next”
veeam7061614-step30
31. Click “Finish” once the components have been updated
veeam7061614-step31
32. Click the menu button and then click on “Options”
veeam7061614-step32
33. Click the check box for “Enable e-mail notification” and then enter your SMTP server, from email and to email. Click “OK”
veeam7061614-step33
34. Click on “Virtual Machines” towards the lower-left of the window and click “Add Server”
veeam7061614-step34
35. Click on your Server type (VMware vSphere for this writing)
veeam7061614-step35
36. Enter the name or IP of the vCenter server and click “Next”
veeam7061614-step36
37. For credentials, click “Add” then enter the domain\username and password for the Veeam account used to connect to vCenter. Click “OK” then click “Next”
veeam7061614-step37
38. Once the server has been added, click “Finish”
39. By default, the folder all VM backups are stored in is “C:\backup”. To change this before you create any backup jobs is to click on “Backup Infrastructure” towards the lower left of the window then click on “Backup Repositories”
veeam7061614-step39
40. Click the “Add Repository” button towards the top-left
veeam7061614-step40
41. Name your Backup Repository and click “Next”
veeam7061614-step41
42. Choose the type of repository (Microsoft Windows server) and click “Next”
veeam7061614-step42
43. Click the “Populate” button then select the backup drive and click “Next”
veeam7061614-step43
44. Enter the folder name (I took the default of D:\Backups) and click the populate button to see the capacity and free space of the drive. Limit the max concurrent tasks and/or data ingestion rate and click “Next”
veeam7061614-step44
45. Ensure vPower NFS is enabled and click “Next”
veeam7061614-step45
46. Review the settings and click “Next”
veeam7061614-step46
47. Once it completes, click “Finish”
veeam7061614-step47
48. Once the new repository appears, click the Menu button in the top-left corner and then click “Configuration Backup”
veeam7061614-step48
49. Change the Backup repository to the newly created repository and click “OK”
veeam7061614-step49
50. Right click on the “Default Backup Repository” and click “Remove” and click “Yes” to confirm delete
veeam7061614-step50
51. Now that a new repository is created, we need to enable deduplication on that folder. Open Server Manager, click on “Manage” then choose “Add Roles and Features”
veeam7061614-step51
52. Click “Next” through the “Before you begin” screen
53. Choose “Role-based or feature-based installation” and click “Next”
veeam7061614-step53
54. Choose “Select a server from the server pool” and select the current server then click “Next”
veeam7061614-step54
55. Expand “File and Storage Services”, then “File and iSCSI Services” and then check the box next to “Data Deduplication” and click “Next”
veeam7061614-step55
56. Click “Next” through “Features”
57. Click “Install”
veeam7061614-step57
58. Once installation is complete, click “Close”
59. Back in “Server Manager”, click on “File and Storage Services”
veeam7061614-step59
60. Click on “Volumes”, right-click the drive that we’ll be enabling dedupe for and choose “Configure Data Deduplication”
veeam7061614-step60
61. Set data deduplication from “Disabled” to “General purpose file server”, change “Deduplicate files older than (in days)” to 0.
veeam7061614-step61

  • a. To exclude folders from being deduped on that disk, click the “Add” button, expand the “Z:\” drive, and select each folder to prevent deduplication. In our setup, only backups are going to the Z:\ drive so we’ll skip this
  • b. Click “Set Deduplication Schedule” and then check the box for “Enable throughput optimization”. You will set the schedule for when dedupe runs. This should run when your backups are NOT running. My backups run OUTSIDE business hours, so dedupe should run DURING business hours. Click “OK” when finished and “OK” again
    veeam7061614-step61b

Now that Veeam is setup and connected to vCenter and we have a backup repository created with dedupe enabled, let’s take a look and see what kind of savings we get when we take our backups. One thing to note is that you won’t see much dedupe savings on a single backup file, but on a long backup chain and multiple backup jobs is where the real savings starts to come into play.

I have configured backups of 2 of my Exchange 2013 servers to run every 6 hours and keep 28 restore points (7 days). This backup job is set to “Reverse incremental” and Veeam is performing inline dedupe, compression set to “Optimal” and optimized for “Local target”. My first full backup was 36.3GB. Over the next 3 days, I have taken 12 more backups for a total of 75.1GB.
veeam7061614-veeam1

After dedupe ran over the last 3 days, we see the size as 75.1GB, but Size on disk is only 10.5GB
veeam7061614-veeam2

This is where it gets a little interesting though. In powershell, running the command “Get-DedupStatus” only shows a savings of 14GB. I’m not sure which one is accurate, but even a savings of just 14GB in one backup job is an improvement. Since Windows Server 2012 deduplication runs across all files on a volume, you will see increased savings for every new backup file that’s created for every job that writes to that backup repository.
veeam7061614-veeam3