I was recently honored to be a guest on Vince Wood‘s IT Reality Podcast for episodes 7 and 8. In the episodes a couple of the things that came up is that while for small environments Veeam will work right out of the box for most end customers of the software there is a requirement to scale the components out correctly. One of the advantages to Veeam Backup and Replication is that it is hardware and operating system agnostic for many of its components but with choice comes complexity.

One of the other things that came up was the fact that for most Veeam Cloud Connect customers, myself included up to 5 months ago when I began working for a Service Provider, the way that side is setup is a mystery. While I won’t exactly be giving up the special sauce here I was struck with the thought that a series of posts that show you how correctly set up a Veeam Backup and Replication v10 environment both on premises and for the Cloud Connect environment would be pretty educational. Each of these will have video walk throughs of the actual installations so you can follow along as well if you like.

I total we’ll be covering the following topics:

• Episode 1: Intro and Common components
• Episode 2: On-Prem Windows Components (VBR, Windows Proxy, Windows Repo)
• Episode 3: On-Prem Linux Components (Proxy, Repo), Create Local Jobs
• Episode 4: Build Service Provider pod
• Episode 5: Create cloud jobs to both Service Provider and Copy Mode to S3
• Episode 6: Veeam Availability Console
• Episode 7: Veeam Backup for Office 365

In this episode we are mostly talking setting up your external SQL server for Veeam use. While the Veeam Backup and Replication installer includes MS SQL Server Express 2016 as part of the simple mode installation, but according to Veeam best practices you wouldn’t want to use this if you are backing up more than 500 instances, extensively using tape or want to leverage a common SQL products for other parts of the Veeam environment including Enterprise Manager or VeeamONE.

1. Intro to Lab Environment Design
2. Blog Post Steps to Come
3. Mount SQL Server 2016 ISO
4. Run Setup.exe
5. Allow for Updates check before installing
6. Rules Check and open up Windows Firewall for communication, either by disabling entirely or at least creating a port based rule for TCP 1433
7. In Feature Selections choose Database Engine Services only unless you or your SQL administrator have other needs
8. Either name your SQL Instance or leave it with the default MSSQLSERVER
9. Based on need or security practices enable or leave disabled the SQL Server Agent and SQL Server Browser services
10. In Database Engine Configuration
    1. Set your authentication mode. I prefer to leave it Windows only but there are valid use cases to choose Mixed mode and create SQL only credentials
    2. Add SQL server administrator accounts. Domain Admins for small environments but also want to add the service account you plan to run Veeam services under
    3. Set your Data Directories. For the lab I will leave default but in production you should create 3 additional volumes for your SQL Server, 1 each for databases, logs and backups
11. Hit Install

Once completed you will be ready to proceed to installing your Veeam server itself. One thing that is ommitted from the video but probably a good idea is to go ahead and install MS SQL Server Management Studio. It’s a separate download, but often when you need to call Veeam support it is database related and SSMS is the way to manage the databases. You can directly download from Microsoft but if you happen to have Chocolatey available on the server installation is a choco install sql-server-management-studio -y  away.

With that we’ll consider this step done and move on to installing the on-premises Windows components in the next post.

So one of the things that I always find interesting with each new Veeam Backup & Replication release is the additions to the PowerShell cmdlets list. PowerShell was first introduced to the VBR universe with version 7 and with each release we have got more and more commands to play with. It still hurts me to this day that they haven’t converted their Snap-In to a module yet but to quote my daughter’s teacher, you get what you get and you don’t throw a fit.

In the spirt of this curiosity I decided to do a little differential fun with 9.5 update 4 and the soon to be GA version 10 Snap-Ins. I’m not going to bore you with all the commands and stuff that led us to here but if you want to reproduce any of this consider my work shown:

asnp VeeamPSSnapin

#On 9.5u4 Server
Get-Command | where {$_.Source -eq "VeeamPSSnapin"} | select Name | Export-Csv -Path "desktop\95commands.csv"
#On 10 Server
Get-Command | where {$_.Source -eq "VeeamPSSnapin"} | select Name | export-csv -Path .\Desktop\10commands.csv"

#load the 2 csv files as reference objects in the hash table
 $objects = @{
	ReferenceObject = (Get-Content -Path '.\OneDrive\Desktop\95commands.csv')
	DifferenceObject = (Get-Content -Path '.\OneDrive\Desktop\10commands.csv')
}

#Compare the objects
$new10commands = Compare-Object @objects

#make a new variable to only give you the new items in v10, saving only the commands and export to file
$new10 = $new10commands | where {$_.SideIndicator -eq '=>'} | select InputObject
$new10 | Export-Csv -Path '.\OneDrive\Desktop\newcommandsonly.csv'

#let's see how many there are!
$new10 | Measure-Object

#finally let's get a variable with the commands and their descriptions from get-help and export that
$descriptions = foreach ($command in $new10) {get-help $command.InputObject | select name,description}
$descriptions | fl > difference.txt

So with the hard work now out of the way we are left with the question, what’s new? Quite a lot actually as there are 736 commands in 9.5 update 4 and and 920 commands in v10, leaving us with a total of 186 new or changed commands. A look at these provides a good idea of where the focus is in this release, lots of “cloudy” things, NAS items and license management. With the releases and now updates to how Veeam Universal Licensing works automated management just makes sense. I am very happy to see all kinds of new commands related to the SureBackup features as the automation capabilities for this have always been sorely lacking. From the looks of things I can now create my virtual lab, create applications groups and sure backup jobs, actually edit them some using Set commands, and start and stop jobs at will. This is going to lead to a more robust capability to script out your environment and then turn it around into a virtual lab appliance, something needed for consistency.

All that being said my end in the script above was to give a list of each new command and it’s description. So without further comment here they are.

Add-VBRAzureComputeBackupCopyJob
This cmdlet creates Azure IaaS backup copy jobs of Azure VMs that are stored on a Microsoft Azure Blob Storage repository. Azure IaaS backup copy jobs will copy the backups from Microsoft Azure Blob Storage external repositories to target repositories.
The cmdlet creates jobs in a disabled state. Run Enable-VBRJob to enable jobs.

Add-VBRAzureDataBoxRepository
This cmdlet adds Azure Data Box storage as an object storage repository to the Veeam Backup & Replication infrastructure.

Add-VBRAzureExternalRepository
This cmdlet adds Microsoft Azure Blob storage as an external repository.

Add-VBRCatalystCopyJob
This cmdlet creates backup copy jobs for HPE StoreOnce repositories.

Add-VBRComputerBackupCopyJob
This cmdlet creates Veeam Agent backup copy jobs.

Add-VBRNASBackupJob
This cmdlet creates file backup jobs.

Add-VBRNASFileServer
This cmdlet adds managed Windows or Linux file servers to the Veeam Backup & Replication infrastructure.

Add-VBRNASNFSServer
This cmdlet adds NFS network shared folders to the Veeam Backup & Replication infrastructure.

Add-VBRNASProxyServer
This cmdlet adds file backup proxy servers to the Veeam Backup & Replication infrastructure.

Add-VBRNASSMBServer
This cmdlet adds SMB network shared folders to the Veeam Backup & Replication infrastructure.

Add-VBRPluginBackupCopyJob
This cmdlet creates plug-in backup copy jobs. To create plug-in backup copy jobs, you must specify at least one source that contains the data you want to add to the copy job. Plug-in backup copy jobs use either of the following sources:
· The existing plug-in backup job created to back up Oracle RMAN or SAP HANA. Run the Get-VBRPluginJob cmdlet to get the plug-in backup job.
· Backup files that are stored in the source repositories. Run the Get-VBRBackupRepository cmdlet to get the source repository.
NOTE:
The backup copy job is created in the disabled state. Run the Enable-VBRPluginJob cmdlet to run the job manually.

Add-VBRvCloudJobObject
This cmdlet adds VMs to vCD backup jobs.

Add-VBRViAdvancedVirtualLab
This cmdlet creates a VMware advanced virtual lab.

Add-VBRViApplicationGroup
This cmdlet creates application groups for SureBackup jobs.

Add-VBRViLinuxProxy
This cmdlet adds Linux backup proxy servers to the Veeam Backup & Replication backup infrastructure.

Add-VBRViSimpleVirtualLab
This cmdlet creates a VMware basic virtual lab.

Add-VBRViSureBackupJob
This cmdlet creates SureBackup jobs.

Apply-VBRManagedByAgentPolicy
This cmdlet assigns Veeam Agent backup policies to protected computers.

Assign-VBRInstanceWorkload
This cmdlet sets the product edition for standalone Veeam Agents to either of the following:
· Server edition
· Workstation edition

Clear-VBRManagedByAgentPolicyCache
This cmdlet removes backup cache from protected computers.

Connect-VBRAzureDataBoxService
This cmdlet connects to Azure Data Box storage.

Connect-VBRViVirtualLab
This cmdlet adds VMs created on VMware to Veeam Backup & Replication.

Copy-VBRComputerBackupJob
This cmdlet clones Veeam Agent backup jobs and Veeam Agent backup policies.

Disable-VBRCapacityExtentSealedMode
This cmdlet disables sealed mode for for extents of a scale-out backup repository.
Run the Enable-VBRRepositoryExtentSealedMode cmdlet to enable sealed mode for extents of a scale-out backup repository.

Disable-VBRCatalystCopyJob
This cmdlet disables backup copy jobs for HPE StoreOnce repositories.
Run the Enable-VBRCatalystCopyJob cmdlet to enable backup copy jobs for HPE StoreOnce repositories.

Disable-VBRComputerBackupJob
This cmdlet disables Veeam Agent backup jobs and Veeam Agent backup policies.
Run the Enable-VBRComputerBackupJob cmdlet to enable Veeam Agent backup jobs and Veeam Agent backup policies.

Disable-VBRFreeAgentInstanceConsumption
This cmdlet disables instance consumption by non-licensed Veeam Agents.
Run the Enable-VBRFreeAgentInstanceConsumption cmdlet to enable this option.

Disable-VBRLicenseAutoUpdate
This cmdlet disables the automatic license update option.
Run the Enable-VBRLicenseAutoUpdate cmdlet to enable the automatic license update option.

Disable-VBRPluginJob
This cmdlet stops plug-in backup jobs and plug-in backup copy jobs.
Run the Enable-VBRPluginJob cmdlet to start plug-in backup jobs and plug-in backup copy jobs.

Disable-VBRRepositoryExtentSealedMode
This cmdlet disables sealed mode for for extents of a scale-out backup repository.
Run the Enable-VBRRepositoryExtentSealedMode cmdlet to enable sealed mode for extents of a scale-out backup repository.

Disable-VBRSureBackupJob
This cmdlet disables running SureBackup jobs.
Run the Enable-VBRSureBackupJob cmdlet to enable SureBackup jobs.

Enable-VBRCapacityExtentSealedMode
This cmdlet enables sealed mode for object storage repositories.
Run the Disable-VBRCapacityExtentSealedMode cmdlet to disable the sealed mode for object storage that are added as extents to the scale-out backup repository.

Enable-VBRCatalystCopyJob
This cmdlet enables backup copy jobs for HPE StoreOnce repositories.
Run the Disable-VBRCatalystCopyJob cmdlet to disable backup copy jobs for HPE StoreOnce repositories

Enable-VBRComputerBackupJob
This cmdlet enables Veeam Agent backup jobs and Veeam Agent backup policies.
Run the Disable-VBRComputerBackupJob cmdlet to disable Veeam Agent backup jobs and Veeam Agent backup policies.

Enable-VBRFreeAgentInstanceConsumption
This cmdlet enables instance consumption by unlicensed Veeam Agents; this option allows Veeam Agents to create backups to Veeam Backup & Replication.
Run the Disable-VBRFreeAgentInstanceConsumption cmdlet to disable this option.

Enable-VBRLicenseAutoUpdate
This cmdlet enables the automatic license update option.
For more information on the automatic license update option, see the Updating License Automatically section of User Guide for VMware vSphere.

Enable-VBRPluginJob
This cmdlet starts plug-in backup jobs and plug-in backup copy jobs.
Run the Disable-VBRPluginJob cmdlet to stop plug-in backup jobs and plug-in backup copy jobs.

Enable-VBRRepositoryExtentSealedMode
This cmdlet enables sealed mode for extents of a scale-out backup repository.
Run the Disable-VBRRepositoryExtentSealedMode cmdlet to disable sealed mode for extents of a scale-out backup repository.

Enable-VBRSureBackupJob
This cmdlet disables running SureBackup jobs.
Run the Disable-VBRSureBackupJob cmdlet to disable SureBackup jobs.

Export-VBRAudit
This cmdlet exports report that contain information on actions performed by an administrator in Veeam Backup & Replication.

Export-VBRRestorePoint

Generate-VBRLicenseUsageReport
This cmdlet creates a report on license usage.

Get-VBRApplicationGroup
This cmdlet returns VMware and Hyper-V application groups.

Get-VBRAzureComputeBackup
This cmdlet returns an array of Azure backups.

Get-VBRAzureNetworkSecurityGroup
This cmdlet returns Microsoft Azure security groups.

Get-VBRCapacityLicenseSummary
This cmdlet returns details on capacity of licenses installed on a backup server.

Get-VBRCapacityTierSyncInterval
This cmdlet returns a time period that contains details on checkpoints in object storage.
IMPORTANT!
This cmdlet applies only for object storage that support the Immutability option.

Get-VBRCatalystCopyJob
This cmdlet returns backup copy jobs for HPE StoreOnce repositories.

Get-VBRComputerBackupCopyJob
This cmdlet returns Veeam Agent backup copy jobs.

Get-VBRComputerBackupJob
This cmdlet returns an array of Veeam Agent backup jobs and Veeam Agent backup policies.

Get-VBRComputerBackupJobSession
This cmdlet returns Veeam Agent job sessions. You can get sessions of Veeam Agent jobs that are managed by Veeam Backup & Replication and Veeam Agent backup policies.

Get-VBRComputerNetworkInfo
This cmdlet returns the VBRComputerNetworkInfo[] object that contains an array of networks connected to Veeam Agent computers. You can use this object to perform instant recovery of Veeam Agent computers.

Get-VBREC2Backup
This cmdlet returns an array of EC2 instance backups.

Get-VBRFreeAgentInstanceConsumptionStatus
This cmdlet returns a state of the instance consumption by non-licensed Veeam Agents.
· False – indicates that the instance consumption by non-licensed Veeam Agents option is disabled.
· True – indicates that the instance consumption by non-licensed Veeam Agents option is enabled.

Get-VBRHvServerConfiguration
This cmdlet returns the following settings of Microsoft Hyper-V hosts that are added to the backup infrastructure:
· EnableCBT: Specifies changed block tracking settings.
o If set to True, the changed block tracking option is enabled.
o If set to False, the changed block tracking option is disabled.
· EnableFailover: Specifies the failover option settings.
o If set to True, the failover option is enabled.
o If set to False, the failover option is disabled.
o Default: True.
· ServerId: Specifies the Microsoft Hyper-V hosts ID.
For more information on settings of Microsoft Hyper-V hosts that are added to the backup infrastructure, see the Specify Settings for Connected Volumes section in the User Guide for Microsoft
Hyper-V.

Get-VBRHvServerVolume
This cmdlet returns volume-specific settings for Microsoft Hyper-V hosts.

Get-VBRHvVssProvider
This cmdlet returns an array of VSS providers that are available on Microsoft Hyper-V hosts.

Get-VBRInstanceLicenseSummary
This cmdlet returns the VBRInstanceLicenseSummary object that contains details on the per-instance license usage. These details include the following information:
· LicensedInstancesNumber – specifies a total number of instances that are available in the license scope.
· UsedInstancesNumber – specifies the number of instances that have already been used.
· NewInstancesNumber – specifies the number of new instances.
· RentalInstancesNumber – specifies the number of instances that are available for the rental license.

Get-VBRLicenseAutoUpdateStatus
This cmdlet returns a state of the automatic license update option.
· False – indicates that the automatic license update option is disabled.
· True – indicates that the automatic license update option is enabled.

Get-VBRLicensedCapacityWorkload

Get-VBRLicensedInstanceWorkload
This cmdlet returns the VBRLicensedSocketWorkload object that contains details on protected workloads for the per-instance license that Veeam Backup & Replication applies to back up these
workloads.

Get-VBRLicensedSocketWorkload
This cmdlet returns the VBRLicensedSocketWorkload object that contains details on licensed hosts for the per-socket license that Veeam Backup & Replication applies to back up these hosts.

Get-VBRNASBackup
This cmdlet returns backup files created by the file backup job.

Get-VBRNASBackupFLRItem
This cmdlet returns an array of objects that contain settings of guest OS files and folders backed up by file backup jobs.

Get-VBRNASBackupFLRItemVersion
This cmdlet returns versions of objects backed-up by file backup jobs.
IMPORTANT!
This cmdlet runs only with file-level restore sessions that are created to restore all versions of backups on file shares.

Get-VBRNASBackupFLRSession
This cmdlet returns restore sessions started to recover backups created by file backup jobs.

Get-VBRNASBackupJob
This cmdlet returns file backup jobs.

Get-VBRNASBackupRestorePoint
This cmdlet returns restore points created by file backup jobs.

Get-VBRNASProxyServer
This cmdlet returns an array of file backup proxy servers added to the Veeam Backup & Replication infrastructure.

Get-VBRNASServer
This cmdlet return backup files created by the file backup job.

Get-VBRPluginJob
This cmdlet returns the VBRPluginBackupJob and VBRPluginBackupCopyJob objects that contains settings of the following types of jobs:
· A plug-in backup job that was created to back up Oracle RMAN or SAP HANA.
· A plug-in backup copy job.

Get-VBRPrivateFixes

Get-VBRPublishedBackupContentInfo
This cmdlet returns details on the mounted content of backup files.

Get-VBRPublishedBackupContentSession
This cmdlet returns an array of sessions that are running to mount the content of backup files to iSCSI target servers.

Get-VBRPublishedBackupDiskInfo

Get-VBRPublishedBackupDiskSession

Get-VBRSocketLicenseSummary
This cmdlet returns the VBRSocketLicenseSummary object that contains details on the per-socket license usage. These details include the following information:
· LicensedSocketsNumber – specifies a total number of CPU sockets on protected hosts.
· UsedSocketsNumber – specifies the number of CPU sockets that have already been used.
· RemainingSocketsNumber – specifies the number of CPU sockets that remain available.
· Workload – specifies the name of the licensed host.

Get-VBRSureBackupJob
This cmdlet returns SureBackup jobs.

Get-VBRTestQuickMigrationSession

Get-VBRVirtualLab
This cmdlet returns the VBRVirtualLab>[] object that contains an array of virtual labs and their main settings. You can use this object with the following cmdlets:
· Remove-VBRVirtualLab – to remove virtual labs from Veeam Backup & Replication infrastructure.
· Add-VBRViSureBackupJob – to create a SureBackup job.
· Set-VBRViSureBackupJob – to modify settings of a SureBackup job.

Get-VBRViVirtualDevice
This cmdlet returns details on virtual disks of VMs from backups.

Get-VBRViVirtualLabConfiguration
This cmdlet returns the VBRViVirtualLabConfiguration object that contains an array of virtual labs and all their settings. You can use this object to modify settings of virtual labs.
Run the Set-VBRViVirtualLab cmdlet to modify settings of virtual labs.

Install-VBRLicense
This cmdlet installs licenses on a backup server.

Mount-VBRObjectStorageRepository
This cmdlet mounts an object storage repository. You can use the mounted object storage to import backups from these object storage.

New-VBRAmazonEC2Tag
This cmdlet creates the VBRAmazonEC2Tag object that contains settings of AWS tags.

New-VBRBackupCacheOptions
This cmdlet creates the VBRBackupCacheOptions object. This object defines backup cache settings of backup files that are stored on the following types of repositories:
· Veeam backup repository.
· Veeam Cloud Connect repository.

New-VBRBackupCopyJobStorageOptions
This cmdlet creates the VBRBackupCopyJobStorageOptions object that contains storage optimization settings for backup copy jobs. These settings allow you to modify the following options for the storage:
· Data compression options
· Data optimization options
· Encryption options
For more information about job storage settings, see the Data Compression and Deduplication section of User Guide for VMware vSphere.

New-VBRComputerGFSMonthlyOptions
This cmdlet creates the VBRComputerGFSMonthlyOptions object that contains settings of a monthly GFS retention policy for Veeam Agent backup jobs.

New-VBRComputerGFSOptions
This cmdlet creates the VBRComputerGFSOptions object that contains settings of a GFS retention policy for Veeam Agent backup jobs.

New-VBRComputerGFSWeeklyOptions
This cmdlet creates the VBRComputerGFSWeeklyOptions object that contains settings of a weekly GFS retention policy for Veeam Agent backup jobs.

New-VBRComputerGFSYearlyOptions
This cmdlet creates the VBRComputerGFSMonthlyOptions object that contains settings of a yearly GFS retention policy for Veeam Agent backup jobs.

New-VBRMySQLProcessingOptions
This cmdlet creates the VBRMySQLProcessingOptions object that contains settings for processing MySQL database transaction logs for Veeam Agent backup jobs

New-VBRNASBackupArchivalOptions
This cmdlet defines retention policy for file versions that are kept on the long-term repository.

New-VBRNASBackupJobObject
This cmdlet creates the VBRNASBackupJobObject object. This object contains settings of files and folders that will be added to the file backup job.

New-VBRNASBackupSecondaryTarget
This cmdlet creates secondary backup repositories. These repositories will keep copies of backups that were created by file backup jobs.

New-VBRPluginCopyJobStorageOptions
This cmdlet creates the VBRPluginCopyJobStorageOptions object. This object contains storage optimization settings for plug-in backup copy jobs. These settings allow you to modify the following
options for the storage:
· Data compression options
· Data optimization options
For more information about job storage settings, see the Data Compression and Deduplication section of User Guide for VMware vSphere.

New-VBRPostgreSQLProcessingOptions
This cmdlet creates the VBRPostgreSQLProcessingOptions object that contains settings for processing PostgreSQL database transaction logs for Veeam Agent backup jobs.

New-VBRRPONotificationOptions
This cmdlet creates RPO notification options. Veeam Backup & Replication will display a warning in the backup copy job if the newly created restore point is not copied within the desired recovery
point objective.

New-VBRSureBackupJobScheduleOptions
This cmdlet creates the VBRSureBackupJobScheduleOptions object that defines a SureBackup job schedule.

New-VBRSureBackupJobVerificationOptions
This cmdlet creates the VBRSureBackupJobVerificationOptions object that defines additional settings for the SureBackup job. You can define the following types of settings:
· Backup file integrity scan
· Malware scan
· Notifications

New-VBRSureBackupLinkedJob
This cmdlet creates the VBRSureBackupLinkedJob object that defines linked jobs with VMs to verify with the SureBackup job.

New-VBRSureBackupStartupOptions
This cmdlet creates the VBRSureBackupStartupOptions object that defines startup settings for VMs that are added to application groups and to jobs that are linked to SureBackup jobs.

New-VBRSureBackupTestScript
This cmdlet creates the VBRSureBackupTestScript object that defines recovery verification scripts for VMs that are added to application groups and to jobs that are linked to SureBackup jobs.
Veeam Backup & Replication will run this script to verify that the VM that has been assigned the specific role has up and running applications for this role.

New-VBRSureBackupVM
This cmdlet creates the VBRSureBackupVM object that defines VMs that you want to add to the application group.

New-VBRViNetworkMappingRule
This cmdlet creates the VBRViVirtualLabNetworkMappingRule object that defines network mapping rules of isolated networks. Veeam Backup & Replication will map isolated networks to production networks that are specified in this rule.
You can use this object to specify network mapping rules in network settings of isolated networks.
Run the New-VBRViVirtualLabNetworkOptions cmdlet to specify network settings of isolated networks.

New-VBRViVirtualLabIPMappingRule
This cmdlet creates the VBRViVirtualLabIPMappingRule object that defines static IP address mapping rules.

New-VBRViVirtualLabNetworkOptions
This cmdlet creates the VBRViVirtualLabNetworkOption object that defines network settings of isolated networks and how to map it to production networks.

New-VBRViVirtualLabProxyAppliance
This cmdlet creates the VBRViVirtualLabProxyAppliance object that defines settings of proxy appliances that are added to the virtual lab.

Publish-VBRBackupContent
This cmdlet mounts the content of backup files using the iSCSI protocol. You can use this content to explore or get the backed-up data. You can mount the following types of backed-up data:
· VM backup
· VM disks

Publish-VBRBackupDisksNFS

Remove-VBRApplicationGroup
This cmdlet removes application groups from the Veeam Backup & Replication infrastructure.

Remove-VBRCatalystCopyJob
This cmdlet removes backup copy jobs for HPE StoreOnce repositories.

Remove-VBRComputerBackupJob
This cmdlet removes Veeam Agent backup jobs and Veeam Agent backup policies from Veeam Backup & Replication infrastructure.

Remove-VBRNASBackup
This cmdlet removes backup files created by the file backup job.

Remove-VBRNASBackupJob
This cmdlet removes file backup jobs from Veeam Backup & Replication infrastructure.

Remove-VBRNASProxyServer
This cmdlet removes file backup proxy servers from the Veeam Backup & Replication infrastructure.

Remove-VBRNASServer
This cmdlet removes file shares that are added to the Veeam Backup & Replication infrastructure.

Remove-VBRPluginJob
This cmdlet removes plug-in backup jobs and plug-in backup copy jobs from the Veeam Backup & Replication infrastructure.

Remove-VBRSureBackupJob
This cmdlet removes SureBackup jobs from the Veeam Backup & Replication infrastructure.

Remove-VBRVirtualLab
This cmdlet removes virtual labs from Veeam Backup & Replication.

Restore-VBRNASBackupFLRItem
This cmdlet restores objects that have been backed up by file backup jobs to original file shares.

Save-VBRNASBackupFLRItem
This cmdlet restores objects backed up by file backup jobs to the specified file shares.

Set-VBRAzureComputeBackupCopyJob
This cmdlet modifies Azure IaaS backup copy jobs.

Set-VBRAzureDataBoxRepository
This cmdlet modifies Azure Data Box storage that is added as an object storage repository to the Veeam Backup & Replication infrastructure.

Set-VBRAzureExternalRepository
This cmdlet modifies settings of Microsoft Azure Blob storage added as an external repository.

Set-VBRBackupCacheOptions
This cmdlet modifies backup cache settings.

Set-VBRBackupCopyJobStorageOptions
This cmdlet modifies storage optimization settings for backup copy jobs.

Set-VBRCatalystCopyJob
This cmdlet modifies backup copy jobs that are created for HPE StoreOnce repositories.

Set-VBRComputerBackupCopyJob
This cmdlet modifies Veeam Agent backup copy jobs.

Set-VBRComputerGFSMonthlyOptions
This cmdlet modifies settings of a monthly GFS retention policy for Veeam Agent backup jobs.

Set-VBRComputerGFSOptions
This cmdlet modifies settings of a GFS retention policy for Veeam Agent backup jobs.

Set-VBRComputerGFSWeeklyOptions
This cmdlet modifies settings of a weekly GFS retention policy for Veeam Agent backup jobs.

Set-VBRComputerGFSYearlyOptions
This cmdlet modifies settings of a yearly GFS retention policy for Veeam Agent backup jobs.

Set-VBRHvServerConfiguration
This cmdlet modifies settings of Microsoft Hyper-V hosts added to the backup infrastructure.

Set-VBRHvServerVolume
This cmdlet modifies volume-specific settings for Microsoft Hyper-V hosts.

Set-VBRMySQLProcessingOptions
This cmdlet modifies settings for processing MySQL database transaction logs for Veeam Agent backup jobs.

Set-VBRNASBackupArchivalOptions
his cmdlet modifies settings of retention policy for file versions that are kept on the long-term repository.

Set-VBRNASBackupJob
This cmdlet modifies settings of file backup jobs.

Set-VBRNASBackupJobObject
This cmdlet modifies settings of files and folders that will be added to the file backup job.

Set-VBRNASBackupSecondaryTarget
This cmdlet modifies settings of secondary backup repositories.

Set-VBRNASFileServer
This cmdlet modifies managed Windows or Linux file serves added to the Veeam Backup & Replication infrastructure.

Set-VBRNASNFSServer
This cmdlet modifies settings of NFS network shared folders added to the Veeam Backup & Replication infrastructure.

Set-VBRNASProxyServer
This cmdlet modifies settings of file backup proxy servers added to the Veeam Backup & Replication infrastructure.

Set-VBRNASSMBServer
This cmdlet modifies settings of SMB network shared folders added to the Veeam Backup & Replication infrastructure.

Set-VBRPluginBackupCopyJob
This example modifies plug-in backup copy jobs.

Set-VBRPluginCopyJobStorageOptions
This cmdlet modifies storage optimization settings for plug-in backup copy jobs.

Set-VBRPostgreSQLProcessingOptions
This cmdlet modifies settings for processing PostgreSQL database transaction logs.

Set-VBRSureBackupJobScheduleOptions
This cmdlet modifies settings of a SureBackup job schedule.

Set-VBRSureBackupJobVerificationOptions
This cmdlet modifies additional settings for the SureBackup job.

Set-VBRSureBackupLinkedJob
This cmdlet modifies settings of jobs linked with the SureBackup job.

Set-VBRSureBackupStartupOptions
This cmdlet modifies startup settings for VMs that are added to application groups and to jobs that are linked to SureBackup jobs.

Set-VBRSureBackupTestScript
This cmdlet modifies settings of custom recovery verification scripts for VMs that are added to application groups and to jobs that are linked to SureBackup jobs.

Set-VBRSureBackupVM
This cmdlet modifies settings of VMs to add to application groups.

Set-VBRViApplicationGroup
This cmdlet modifies settings of application groups.

Set-VBRViLinuxProxy
This cmdlet modifies settings of Linux backup proxy servers to the Veeam Backup & Replication backup infrastructure.

Set-VBRViNetworkMappingRule
This cmdlet modifies network mapping rules of isolated networks.

Set-VBRViSureBackupJob
This cmdlet modifies settings of SureBackup jobs.

Set-VBRViVirtualDevice
This cmdlet modifies settings of VM virtual disks.

Set-VBRViVirtualLab
This cmdlet modifies settings of WMware virtual labs of the following kinds:
· WMware Basic Virtual Lab
· WMware Advanced Virtual Lab

Set-VBRViVirtualLabIPMappingRule
This cmdlet modifies static IP address mapping rules.

Set-VBRViVirtualLabNetworkOptions
This cmdlet modifies network settings of isolated networks and how to map it to production
networks.

Set-VBRViVirtualLabProxyAppliance
This cmdlet modifies settings of proxy appliances.

Start-VBRCatalystCopyJob
This cmdlet starts backup copy jobs for HPE StoreOnce repositories.

Start-VBRComputerBackupJob
This cmdlet starts Veeam Agent backup jobs and Veeam Agent backup policies.

Start-VBRDownloadTenantBackup
This cmdlet downloads tenant backups from capacity tier to performance tier.

Start-VBRNASBackupFLRSession
This cmdlet starts a restore session to explore objects backed-up by file backup jobs. You can
restore files to either of the following options:
§ Restore backups to the specific restore point.
§ Restore all versions of backups that are located on the specific file share. The cmdlet will restore
all versions of backup files that are located on the short-term and long-term repositories.

Start-VBRNASBackupHealthCheck
This cmdlet performs a health check for file backup jobs.

Start-VBRNasBackupRestore
This cmdlet starts a restore of backups created by the file backup job.

Start-VBRScaleOutBackupRepositoryOffload

Start-VBRSureBackupJob
This cmdlet starts SureBackup jobs.
Run the Stop-VBRSureBackupJob cmdlet to stop SureBackup jobs.

Start-VBRViComputerInstantRecovery
This cmdlet starts an instant recovery of Veeam Agent computers to the VMware infrastructure.
You can restore the following types of computers backed up by Veeam Agent:
· MIcrosoft Windows computers
· Linux computers

Start-VBRViInstantVMDiskRecovery
This cmdlet starts restore of VM virtual disks from backups.

Stop-VBRComputerBackupJob
This cmdlet stops Veeam Agent backup jobs and Veeam Agent backup policies.

Stop-VBRNASBackupFLRSession
This cmdlet stops restore sessions started to recover backups created by file backup jobs.

Stop-VBRSureBackupJob
This cmdlet stops SureBackup jobs.
Run the Start-VBRSureBackupJob cmdlet to start SureBackup jobs.

Stop-VBRViInstantVMDiskRecovery
This cmdlet stops a restore of VM virtual disks.

Sync-VBRNASBackupMetadata
This cmdlet downloads metadata of backup files from the long-term backup repository to the
short-term repository. You can use this cmdlet to restore backup files that are located on the long-term
repository but are no longer available on the short-term repository.
IMPORTANT!
Before downloading metadata from the long-term repository, you must run the Sync-VBRBackupRepository
cmdlet to rescan this repository.

Sync-VBRSOBREntityState
This cmdlet synchronizes the state of data stored in object storage to the state of data stored
on extents in the scale-out backup repository for the specified period of time.
You can run this cmdlet when data on the extents is corrupted or you want to restore data to the
specific point-in-time. Every time when data is moved to object storage, a checkpoint is created on
object storage. The checkpoints that have been created before are not overwritten and are stored in
object storage, so multiple restore points are created. You can use these restore points to specify the
necessary point-in-time and restore data to a specific state.
When you run the Sync-VBRSOBREntityState cmdlet, Veeam Backup & Replication performs the following
actions to synchronize data:
1. Removes backups and their metadata indexes stored on the extents of scale-out backup
repositories.
2. Downloads metadata and metadata indexes of backups that are stored in the object storage to the
extents of scale-out backup repositories for the specified period of time. The backups are not
downloaded to the extents of scale-out backup repositions and are stored in object storage.
Run the Get-VBRCapacityTierSyncInterval cmdlet to get details on checkpoints available in object storage
for a specific period of time.

Test-VBRMetadata

Uninstall-VBRDiscoveredComputerAgent
This example removes Veeam Agent from a specific protected computer.

Uninstall-VBRLicense
This cmdlet removes a license from a backup server.
NOTE:
By default, details about both per-instance and per-socket objects are removed. To remove details about
either per-instance or per-socket objects, you must specify the necessary parameter.

Unmount-VBRObjectStorageRepository
This cmdlet unmounts object storage repositories.

Unpublish-VBRBackupContent
This cmdlet unmounts the content of backup files from iSCSI target servers.

Unpublish-VBRBackupDisk

Update-VBRLicense
This cmdlet updates licenses.
For more information on updating licenses, see the Updating License section of User Guide for VMware
vSphere.

Validate-VBRCloudTenantCredentials

Conclusion

In the end there’s lots of new capabilities here to work with. I’m sure there’ll be more information in the upcoming What’s New document on GA day but for the automation buffs out there maybe this will give you a jump start on how you’ll be doing things after upgrading.

As we rapidly approach release day for Veeam Backup and Replication v10 (February 18!) Many of you are going to want to do upgrades on that day or shortly after. Personally for production level servers I advocate for waiting for patch 1 to come out, usually 2 weeks to 1 month after GA if history bears out. This is especially true if you utilize any Cloud Service Providers for offsite copies as this is what Veeam refers to as a “breaking” release. That means that if the cloud side VBR you are connecting to is not also on version 10 then you will see errors both during installation and then once you open the console and your backups WILL fail.

That said if you have a testing environment or a lab GA is a great day to get at it. This post, now with video, will outline the steps necessary to do an in-place upgrade. One important thing to note before going down this road is upgrade to the RTM/GA is limited to 9.5 update 3 or later. If you happen to be running an older version you will need to upgrade to this first.

Prerequisites:

1. Go to my.veeam.com and download the ISO on or after 2/18.2020 and obtain a new v10 license file
2. Ensure that any and all jobs are not running. Usually this means Backup Copy Jobs need to be disabled as they are continuous (mostly)

Process:

1. Mount the ISO file by right click>mount
2. Run setup.exe and click upgrade
3. VBR v10 is now based on the .NET Framework v4.7.2 and you will be prompted to install that if you haven’t already. A reboot will be required before you can proceed.
4. Once the reboot has been completed (pretty quick on Windows Server 2019) we’ll need to remount our ISO and run setup.exe again
5. Accept EULAs, Next
6. Verify versions you are upgrading from, Next
7. If you’ve already downloaded your new v10 compatible license file go ahead and install it now. If not, no worries because Veeam will be granting you a 60 day grace period to get this done. Once you are installed you can import the new license via the Menu>License window in the VBR console. Hit Next
8. Next we want to verify the database configuration. It should automatically have all the information for where your  VeeamBackup database is. Before you get to this point it is a best practice to take a SQL level backup of the database prior to upgrading. Hit Next and then confirm that you do want to upgrade the existing database.
9. Finally we are at ready to install. Go ahead and check the “Update remote components automatically” as this will have Veeam launch the updater wizard upon first launch of the console to update any scaled out proxies, repositories or WAN accelerators you may have. Hit Install.
10. Once complete hit Finish and choose yes to reboot.
11. Launch and log in to the VBR console
12. Upgrade any external components that need done
13. Go to Backup Infrastructure>vSphere and rescan all your vSphere components. This may be overkill but I’ve always found a rescan after upgrade heads off many upgrade related issues.

This slideshow requires JavaScript.

If you have been around the Veeam world for very long, you know they don’t do small releases; each new version comes with literally hundreds of enhancements and bug fixes. While my last post covers many of the headliners there is still a lot of great things left to see. In this post, I’m going to discuss some of the “little things” that aren’t so little that are going to make this a great release.

Object Storage

One of the long asked for features of Veeam was greater ability to leverage public cloud capabilities for backups and data management in general. In 9.5 update 4, we got the ability to offload local storage to object as a way of extending on-prem resources through dehydrating local backup copies to S3, Azure Blob and the like. In v10 we now have what they call Copy mode which is the next step in the evolution. With Copy mode you will create a Scale Out Backup Repository containing any number of on-premises repository extents and a cloud storage provider, referred to as an External Repository. You will have the ability to have it mirror the local extent to cloud to give you a somewhat simplified method to getting your backups off-site. We’ve also already talked about the capability built in for the NFS backup capability.

While Veeam Backup and Replication is the star of this post, it is worth noting here that the recently released Veeam Backup for Office 365 version 4.0 has the ability to address object storage as a direct repository with no need for local storage at all. This totally makes sense in this case; effectively it empowers you to take a cloud workload in location/system A and place the backups in location/storage B, while all the time maintaining control in an on-prem system, if you choose.

End of the day, the day is coming where object storage is going to become THE first-class citizen in the Veeam ecosphere. Does this mean you have to start using Amazon, Microsoft, or Google for your backup storage, either as a backup copy or even for initial backups? Heck no! Any number of Veeam Cloud Service Providers (VCSPs) including, I don’t know, OffsiteDataSync, are capable of offering these solutions themselves along with more of the hands on assistance you’ve come to know and love.

Restore Here, There and Everywhere

Over the last few releases, we’ve steadily been getting more and more places and ways to restore our data. If you think about it, that’s what it is all about, isn’t it? Backups without an easy way to restore them are just blobs of data taking up disk space. With our traditional VM-based workloads, we’ve been able to have the ability to restore to Azure and Amazon EC2 instances. That’s great, as long as you have no problem with public cloud. It can also be a time-consuming process if you are restoring there from your on-premises backup repositories. Now with v10, we have the capability to have copies of our backups in object or blob storage buckets, putting those backups much closer to their Cloud Compute counterparts. While there are still quite a few steps involved in making this viable, as my friend Anthony Spiteri demonstrated, you can perform these restores while on airplane Wi-Fi in the time it takes for a normal flight.

The restore capability that really gets me excited is a feature they call “restore anything to vSphere.” In this if Veeam is ingesting the backup as a traditional .VBK file, you now will have the capability to restore it directly to a vSphere VM. Hyper-V backups? Restore to vCenter. Physical boxes protected with Veeam Agents for Windows or Linux? Right click, restore to vCenter. For those doing mixed production workloads, this has great potential as a migration tool or powering a single Disaster Recovery Site with only a single framework to support.

On-Premises GFS

One final thing of note is Veeam and the Backup industry as a whole has long advocated for the concept of Grandfather Father Son; Where you have your normal backup that runs for a given period, but outside of that, you have sealed backups on other given time periods created from the backup runs. For example, you might have a normal run job of 30 daily backups, but from that, you seal 12 monthly and 6 yearly backups to give you historical coverage.

Traditionally with Veeam Backup and Replication, this is done as a function of the Backup Copy job, but now with version 10, we have the capability to make GFS restore points right on the primary backup job.

Conclusion

As you can see there’s a lot to like with version 10. Some of these things are answers to long term requests, other are keeping up with today’s computing landscape. Either way it exciting to see what is coming next!

Veeam Backup and Replication v10‘s release is now imminent after a loooooong wait. In fact, as of yesterday we now have a tentative release date: February 18, 2020. For the past few weeks, I’ve been able to work with the first Release Candidate in the lab, and I’ve found quite a few things to love in this release that I’d like to share here.

Linux, Linux, Linux!

Veeam Backup & Replication has long been a Windows first solution and everything else a far distant second. That worked and continues to work really well, but in 2020 the needs of larger customers require automation and management workload shrinkage that Linux-based components lends to. With this release, we now have Linux-based proxies as an option. These are not deployable appliances. You deploy them in the same way as you would a Windows Proxy: deploy the VM, add it to your backup infrastructure, then add it as a proxy, which installs the necessary software.

While many of you may have the same “what, no appliance?” reaction I did, this actually makes sense as it lets organizations develop their own templates based on their own requirements and security policies. Then they can use their automation method of choice to deploy. This will be a big hit for the VSAN crowd, which should have a proxy per host to be in line with best practices.

Further, while we have long had the ability for Linux-based proxies (especially for those wishing to mount NFS datastores as backup repositories), they were never the first-class citizen Windows or appliance-based repos were. With this release we get experimental support for fast cloning with XFS and BRFS. From what I’m hearing they are far more confident in the former. In my own tests writes to this are potentially faster than to ReFS and without the memory requirements ReFS repos need.

Finally, for the Veeam Agent for Linux crowd, there is now support for doing Application Aware Processing for Postgres and MySQL on Linux — the same as we’ve seen for Microsoft SQL in VBR. As we now live in the Veeam Universal Licensing world — even if you have some of these VMs in your environment — you can make the choice to back them up with a managed VAL install instead to a normal backup job to take advantage of this feature, all the while using the same licensing from the same VBR server.

NFS All the Things

Speaking of using Linux to front end NFS shares, that is no longer required as we can now natively address them as a repository. Over the years, many have tried to address this as common SMB shares, but this capability has always been flaky and poor performing, comparatively, so everybody had their work arounds from using it. Now we can add NFS in a server:/share/folder manner and make use of all the capabilities of NFS 3 or 4.

One of the other big features of the release is something I’m sure my friend Michael Cade would love to tell you about, the ability to directly backup NFS or other file shares as a backup job. You can now go into the Inventory portion of your Veeam UI and add file shares there that can then be targeted for File Backup Jobs that are processed in a familiar manner. What is interesting to me with this is the backups are actually written in native blob format (think Azure Blob or Amazon S3). You have the ability to send them directly to object storage archives immediately after the backup hits the on-premises repository. It is worth noting that this is a Veeam Universal Licensed only feature with each 250 GB of data consuming a license instance. I personally think that threshold per instance is too low as it wouldn’t take long with these giant filers to have the NFS share consume more licenses than the virtualization workload at that rate, but licensing is not my fight (today)!

Backup Copy Enhancements

I’ll be honest, as a shiny new architect in the VCSP space this is near and dear to my heart (and my job). Before that, I was a Cloud Connect customer, and there is quite a bit here to be happy about. Probably the most visible of these is the new Mirror Mode, which allows you to mirror any on-prem job to your backup copy job easily. This is great if you are wanting a very simplistic policy for cloud-based copies. This also FINALLY gives us the ability to ship transaction logs via backup copy, which is very nice. The old method, now referred to as Pruning Mode, is still available, allowing you to pick backups from an existing backup job on the fly to create your backup copy.

Next, within the Advanced settings of your backup copy, you’ll also now find a RPO monitor settings tab. I know from my limited time working for a provider, one of our common support concerns is customers will have a disconnect on the fact that their local jobs are failing for whatever reasons and then their off sites are silently broken because they have nothing to copy. With RPO monitor you can configure your backup copy job to send an alert if they job fails to copy any restore points for a given period of time. For me, I look forward to this being an escalation point by having it send text messages if it isn’t happening.

Finally, also in this release we’ve finally seen some real improvements in the WAN accelerator portion. Five or six years ago when this feature was initially released, you had large numbers of customers who had sub 100 Mbps bandwidth for their off-site copies, and this was a great way to maximize those links and minimize the backup copy window.

Conclusion

As you can see there’s a lot to like with version 10. Some of these things are answers to long-term requests. Others are keeping up with today’s computing landscape. Either way, it exciting to see what is coming next!

Tune in tomorrow for Part 2 of My Favorite Things about VBR v10!

This year I was honored with the ability to attend Veeam Software’s Vanguard Summit. Summit comprises a meeting of 60-70 of world’s best Veeam Engineers, Architects, and Partners along with their own Product Strategy and Management groups in Prague, Czech Republic.

Often in talking about a subject we’ll float the old cliché of the good, the bad and ugly of it and frankly there is nothing negative I can say about this event. Because of that in this series of posts I’m going to cover the good (the event itself), the awesome (the people and content), the beautiful (the city of Prague itself), and as a bonus, the technical. This post will be the second in the series, covering the awesome people and content that comprise Vanguard Summit.

Community

There are many vendor community programs out there, most of which are much bigger than the Vanguards, and while they may have some nice intrinsic benefits such as licenses or hoodies, nobody does it better than Rick Vanover and his team. This is my 5th year in the program but due to the rules of my previous employer I’ve never been able to participate in person. The addition of being able to interact with seventy of the smartest people was invigorating and enjoyable. While I was happy to meet and spend time with everyone it was great to get to catch up with community stalwarts and friends such as Matt Crape, Craig Dalrymple, Brad Jervis, Dean Lewis and Al Rasheed.

There is nothing like being in a room with your peers, most of which leave me in awe with their abilities, hearing about what comes next from a company and have your feedback and thoughts sought out. In the process the attendees start collaborating on ideas that end up shaping things for years to come. I’ve said this before, but if you think the value of any program like this is measured monetarily, you are doing it wrong. The true value is the information that not only passes from the vendor to the program members but between the members itself and this group is in my mind the best of the best.

Content

I remember back when I began as a Veeam customer there was the free FastSCP product and Veeam Backup & Replication. After nine years it is amazing to see how the product line has grown and this week made that very apparent, with 2.5 days jam packed with content on current and future products. In a later post I’m going to be covering a lot of what’s coming in v10 of Veeam Backup & Replication but we were also treated to updates on Backup for O365, VeeamONE, Veeam Agents for Windows and Linux, as well as Veeam Availability Orchestrator. This doesn’t include the things we aren’t allowed to discuss but frankly are pretty exciting.

One of the ways that this content is vastly different from other vendor briefings you may have attended or seen maybe at a TechFieldDay (who Veeam will once again be attending for TFD #20) event or the like, besides the great Product Strategy staff many of these sessions were led or included the product management team for all of their products. The highlight to me of this even is the final session on Tuesday where we had Anton Gostev, Alec King, and others from the product management/development team in an “Ask Me Anything” style session where we were given the opportunity to ask all we wanted and as best I could tell were given no “BS” answers. In short the content was pretty amazingly done and consisted of far more access to information than I’ve seen from any other vendor.

Conclusion

Much like my last post rather than bore you with more of my opinions I’ll leave you with some pictures from the event.

This slideshow requires JavaScript.

This year I was honored with the ability to attend Veeam Software’s Vanguard Summit. Summit comprises a meeting of 60-70 of world’s best Veeam Engineers, Architects, and Partners along with their own Product Strategy and Management groups in Prague, Czech Republic. As one who had never been to Europe and has long been an advocate of Veeam’s products Vanguard Summit had all the makings of an awesome event and it never came close to letting me down.

Often in talking about a subject we’ll float the old cliché of the good, the bad and ugly of it and frankly there is nothing negative I can say about this event. Because of that in this series of posts I’m going to cover the good (the event itself), the awesome (the people and content), the beautiful (the city of Prague itself), and as a bonus, the technical.

The Good

As anybody who has ever been to VeeamON or even a Veeam Party at partner conferences such as VMworld will tell you, the company knows how to throw an event. That holds true especially when they do small group events such as Vanguard Summit. The Summit itself consists of two and a half days starting on Tuesday of technical content that we’ll discuss later, but the event, like the Vanguard program itself, is as much about its community as it is the content. Two full days before the first session many if not most of us arrived in Prague to allow those coming long distances to get acclimated prior to the event starting. That meant that as a group we had most of the day Sunday and Monday to hang together as a group, get reacquainted and go sightseeing.

Things got into high gear Monday night as we all gathered at a rooftop bar and restaurant for dinner and “responsible enjoyment” just as sunset was approaching. The views, the food, the people were all pretty magical. Afterwards many of us gathered back in the hotel bar for conversation before getting ready for the content portion to start the next day.

After a full day Tuesday of technical content; some current, much it forward it is a lucky thing that Tuesday was a free night. After the traditional Vanguard toast lead by Craig Dalrymple the free evening allowed us an opportunity to further gather and then get a little extra rest after all we’d processed that day.

Wednesday we got right back to it followed by Vanguard Summit’s signature evening which this year included us taking over the Starpromen Brewery Visitors Center for a good bit more “responsible enjoyment.” This event included some great local foods, a brewery tour and a photo booth all the while getting the chance to relax and get to know the people behind the products you probably use everyday for your backup and replication needs.

The final day of the even is actually just a half day of content, allowing for some final gatherings and sight seeing. In these sessions the content was extremely valuable as it included deep dives into shiny new technology coming in v10 but also included the ability for us to directly provide feedback on the event itself. If you haven’t figured it out yet my own feedback was nothing short of glowing as the event was amazingly planned by Aubrey Galen of Veeam’s events team and the Product Strategy team who among many other things are responsible for the Vanguard program itself. For all of this I owe them a hearty thank you for a wonderful time.

Conclusion

Rather than write in this space I’m just going to load you with some images from the week. Until next time!

This slideshow requires JavaScript.

Almost ten years ago I interviewed with this guy named Mike Murphy for a Senior Network Admin job at the West Virginia Housing Development Fund. I’d been laid off from my previous employer due to plant closure and had been on unemployment for a while. What was supposed to be a 1 hour interview took almost 2 hours and we hit it off pretty well. He has been one of the best managers I’ve ever had and more importantly, a friend.

For the past ten years under Mike’s leadership I’ve been allowed to do some very cool things in my role there; learn about things like VMware vSphere, Veeam Backup and Replication, and cloud computing while making the computing infrastructure for The Fund the best I could make it. I also got to get into this thing called the “tech community” and it has truly changed my career trajectory.

I’ve been extremely lucky to be included in things like vExpert and the Veeam Vanguards, learning to engage and give back as much as possible to those communities with my own viewpoints and knowledge. For what I’ve given it will never match what I’ve got back; the range of ideas, the challenges of my own beliefs, and frankly the friendships. In short it has given me the opportunity to be a better version of myself. Thanks in a very large part to that tech community after almost ten years it is finally time for me to be moving on.

I am extremely excited to say that I will soon become Senior Cloud Architect for OffsiteDataSync, now a part of J2 Global. I’ve been associated in a few ways with ODS for years but I have a great deal of thanks to fellow Vanguard Brad Jervis, who made the introduction and who I will soon be working side by side with. My tech loves have been mostly Veeam and VMware for quite some time now so it’s very exciting to take what I’ve learned and apply it at a much grander scale.

In addition to the new technical challenges in this new role I’m now going to be in a position to be much more socially active so expect to see quite a bit more content here in the future as I learn and grow into this new role. It’s already looking like it’s going to be a fun ride, I can’t wait to get on!

In the last post we talked about the more traditional models of architecting a disaster recovery plan. In those we covered icky things like tape, dark sites and split datacenters. If you’d like to catch up you can read it here. All absolutely worthwhile ways to protect your data but all of those are slow and limit you and your organizations agility in the case of a disaster.

By now we have all heard about the cloud so much we’ve either gone completely cloud native, dabbled a little or just completely loathe the word. Another great use for “somebody else’s computer” is to power your disaster recovery plans. By leveraging cloud resources we can effectively get out of the managing hardware business in regards to DR and have borderline limitless resources if needed. Let’s look at a few ways this can happen.

DRaaS (Disaster Recovery as a Service)

For now this is my personal favorite, but my needs may be and probably are different from yours. In a DRaaS model you still take local backups as you normally have, but then those backups or replicas are then shipped off to Managed Service Providers (MSPs) aligned with your particular backup software vendor.

I can’t particularly speak to any of the others from experience but CloudConnect providers in the Veeam Backup and Replication ecosphere are simple to consume and use. Essentially once you buy the amount of space you need from a partner you then use the link and credentials you are provided and add them to your backup infrastructure. Once done you create a backup copy job with that repository as the target and let it run. If you are bandwidth restrained many will even let you seed the job with an external hard drive that you ship them full of backups then all you have to transfer over the wire is your daily changes. Meanwhile all of these backups are encrypted with a key that only you and your organization knows so the data is nice and safe sitting elsewhere.

This is really great in that it is infinitely scalable (you only pay for what you use) and you don’t have to own any of the hardware or software licenses to support it. In the case that you have an event you have options; you can either scramble and try to put something together on your own or most times you can leverage the compute capabilities of the provider to power your organization until such time you can get your on-site resources available again. As these providers will have their own IT resources available you and your team will be freed up to do the work of getting staff and customers back online as they handle getting you restored and back online.

In my mind the drawbacks to this model are minimal. In the case of a disaster you are definitely going to be paying more than you would if you are running restored systems on your own hardware, but you would have had to buy that hardware and maintain it as well which is expensive. You will also be in a situation where workers and datacenter systems are not in the same geographical area as well which may cause for increased bandwidth cost as you get back up and running but still nothing compared to maintaining this consistently. Probably the only real drawback here is almost all of these types of providers require long-term agreements, 1 year or more for the backup or replication portion of what is needed. You also need to be sure if you choose this route that the provider has enough compute resources available to absorb you if needed. This can be mitigated by working with your provider to do regular backup testing at the far end. This will cost you a bit more but it is truly worth it to me.

Backup to Public Cloud

Finally we come to what all the backup vendors seems to be  going towards these days, public cloud backups. In this situation your backups are either on premises first (highly recommended) and then shipped off to the public cloud provider of your choice. AWS, Azure or GCP start messing with their storage pricing models and suddenly become cheaper? Simply just add the new provider and shift the job to the new provider, easy peasy. As with all things cloud you are in theory also infinitely scalable so you don’t have to worry about on boarding new workloads except for cost, and who cares about cost anyway?

The upside here is the ability to be agile. Start to finish you can probably be setup to consume this model within minutes and then your only limit to how fast you can be covered is how much bandwidth you make available to shipping backups. If you are doing this to cover for an external event like failure of your passive site you can simply tear it back down afterwards just as fast as you made it. Also you are only ever paying for your actual consumption, so you know how much your cost is going to be for any additional workload to be protected, you don’t ever pay for “spare space.”

As far as the drawbacks I feel like we are still in the early days of this so there are a few. While you don’t have to maintain your far end equipment for either backup storage or compute I’m not convinced that this isn’t the most expensive option for traditional virtualized workloads.

Hybrid Archive Approach

One of the biggest challenges to maintaining an on-prem, off-prem backup system is we all run out of space sometimes. The public cloud provides us an ability to only consume what we need, not paying for any fluff, as well as letting others manage the performance and availability of that storage. One trend I’m seeing more and more is the ability to supplement your on premise backup storage with public cloud resources to allow for scale out of archives for as long as necessary. There is a tradeoff between locality and performance, but if your most recent backups are on premises or well-connected to your production environment you may not ever need to access those backups that archived off to object storage so you don’t really care how fast it is to restore; you’ve just checked your policy checkbox and have that “oh no” backup out there.

Once upon a time my employer had a situation where we needed to retain every backup for about 5 years. Each year we had to buy more and more media to save these backups we would never ever restore to because they were so old, but we had them and were in compliance. If things like Veeam’s Archive Tier or similar with other vendors existed I could have said “I want to retain X backups on-prem but after that shift them to a S3 IA bucket.” In the long-term this would have saved quite a bit of money and administrative overhead and when the requirement went away all I had to do is delete the bucket and reset back to normal policy.

While this is an excellent use of cloud technology I don’t consider it a replacement for things like DRaaS or Active/* models. The hoops you need to go through to restore these backups to a functional VM are still complex and require resources. Rather I see this as an extension of your on-prem backups to allow for short-term scale issues.

Conclusion

If you’ve followed along for both posts I’ve covered about 5.5 different methods of backing up, replicating and protecting your datacenter. Which one is right for you? It might be one of these, none of these or a mash-up of two or more to be honest. The main thing is know your business’ needs, it’s regulatory requirements and

It is Disaster Recovery review season again here at This Old Datacenter and reviewing our plans sparked the idea to outline some of the modern strategies for those who are new to the game or looking to modernize. I’m continually amazed by the number of people who I talk to that are using modern compute methodologies (virtualization on premises, partner IaaS, public cloud) but are still using the same backup systems they were using in the 2000s.

In this post I’m going to talk about some basic strategies using Veeam Backup and Replication because that is primarily what I use, but all of these are capable with any of the current data backup vendors with varying levels of advantages and disadvantages per vendor. The important part is to understand the different ways about protecting your data to start with and then pick a vendor that fits your needs.

One constant that you will see here is the idea of each strategy consisting of 2 parts. A local backup first to handle basic things like a failing VM, file restore, and other things that aren’t responding to all systems down. Secondly then archiving that backup to somewhere outside of your primary location and datacenter to deal with that systems down or virus consideration. You will often hear this referred to as the 3-2-1 rule:

• 3 copies of your data
• 2 copies on different types of physical media or systems
• 1 copy (at least) in a different geographical location (offsite)

On Premises Backup/Archive to Removable Media Backup

This is essentially an evolution on your traditional backup system. Each night you take a backup of your critical systems to a local resource and then copy that to something removable so that it can be taken to somewhere offsite each evening. In the past this was probably only one step, you ran backups to tape and then you took that tape somewhere the next morning. Today I would hope the backups would land on disk somewhere local and then be copied to tape or a USB hard disk but everybody has their ways.

This method has the ability to get the job done but has a lot of drawbacks. First you must have human intervention to get your backups somewhere. Second restores may be quick if you are restoring from your primary backup method but if you have to go to your second you first have to physically locate that correct data set and then especially in the case of tape it can take some time to get that back to functional. Finally you own and have to maintain all the hardware involved in the backup system, hardware that effectively isn’t used for anything else.

Active/Passive Disaster Recovery

Historically the step up for many organizations from removable media is to maintain a set of hardware or at least a backup location somewhere else. This could be just a tape library, a NAS or an old server loaded with disks either in a remote branch or at a co-location facility. Usually you would have some dark hardware there that could allow systems to be restored if needed. In any case you still would perform backups locally and maintain a set on premises for the primary restore, then leverage the remote location for a systems down event.

This method definitely has advantages over the first in that you don’t have to dedicate a person’s time to ensuring that the backups go offsite and you might have some resources available to take over in case of a massive issue at your datacenter, but this method can get very expensive, very fast. All the hardware is owned by you and is used exclusively for you, if ever used at all. In many cases datacenter hardware is “retired” to this location and it may or may not have enough horsepower to cover your needs. Others may buy for the dark site at the same time as buying for the primary datacenter, effectively doubling the price of updating. Layer on top of this the cost of connectivity, power consumption and possibly rack space and you are talking about real money. Further you are on your own in terms of getting things going if you do have a DR event.

All that being said this is a true Disaster Recovery model, which differentiates from the first option. You have everything you need (possibly) if you experience a disaster at your primary site.

Active/Active Disaster Recovery

Does your organization have multiple sites, with datacenter capabilities in each place? If so then this model might be for you. With Active/Active you design you multisite datacenters with redundant space in mind so that in the case of an event in either location  you can run both workloads in a single location. The ability to have “hot” resources available at your DR site is attractive in that you can easily make use of not only backup operations but replication as well, significantly shortening your Restore Time Objective (RTO), usually with the ability to rollback to production when the event is over.

Think about a case where you have critical customer facing applications that cannot handle much downtime at all but you lose connectivity at your primary site. This workload could fairly easily be failed over to the replica in the far side DC, all the while your replication product (Think Veeam Backup & Replication or Zerto) is tracking the changes. When connectivity is restored you tell the application to fallback and you are running with changes intact back in your primary datacenter.

So what’s the downside? Well first off it requires you to have multiple locations to be able to support this in the first place. Beyond that you are still in a world of needing to support the load in case of having an event, so your hardware and software licensing costs will most likely go up to support this event that may never happen. Also supporting replication is a good bit more complex than backup when you include things like the need for ReIP, external DNS, etc. so you should definitely be testing this early and often, maintaining a living document that outlines the steps needed to failover and fallback.

Conclusion

This post covers what I consider the “old school” models of Disaster Recovery, where your organization owns all the hardware and such to power the system. But who wants to own physical things anymore, aren’t we living in the virtual age? In the next post we’ll look at some more “modern” approaches to the same ol’ concepts.