VeeamON 2024 - Use Code "COMMUNITY10" for 10% Off!
Veeam Backup and Replication V12 have a lot of improvements and new features in it. If you are upgrading to V12 or installing Veeam Backup and Replication, there are many things that you should consider when planning your upgrade or installation.The following are a few of my thoughts to help guide you in forming your implementation and configuration decisions.If you are upgrading to VBR V12, your first step should be to consult the following documents located at helpcenter.veeam.com:What’s New Release notes VBR V12 User Guide The release notes document has a good section detailing the upgrade process.Installation/Upgrade of the VBR console serverLet’s start with the installation and process and what to expect.VBR V12 uses the same license key format as V11, so there is no need to update to a V12 on the customer portal. The installation GUI is revamped and looks slick. As it is new, you will notice that some options have been rearranged, so take your time and pay attention to what
There has been a significant focus on how to make Veeam Backup resilient to ransomware. More specifically - how to have Veeam backups available for recovery in case of an incident.In the past few months, I have had discussions with customers who have successfully recovered their production data after a ransomware attack. The common theme among these successful recoveries has been the availability of a secondary off-site copy of their backups to recover from, as their primary backup repository was compromised and destroyed outside of the Veeam software.Veeam ransomware protection should be the customers’ focus, and it is always a priority goal in my architecture designs. Secure by design is also a core design principle of the Veeam Architecture team.Off-site backup copies can provide an additional layer of data security:They are usually behind a VPN with a robust firewall deployment They are typically kept on a different network segment They often use an additional authentication metho
While helping an SE with a POC, I encountered an odd obscure error when trying to install a repository on one VM and a proxy on another VM. The error message was received after we added the VMs as managed Windows servers and during the actual repository and proxy install.The error I received was:“Installing package Transport Error: Error 1920. Service Veeam Data Mover Service (VeeamTransportSvc) failed to start. Verify that you have sufficient privileges to start system services.” I was a little panicked when I saw this as I have not encountered this error before, and the service installs work.After my initial panic, my attention immediately turned to an account permissions issue. The account being used is a domain account that was a member of the local administrators group on the servers. The account used was able to start and stop other services. A check of Google yielded little insight. It did point me to the Veeam KB 1059 – which discusses this error.The first step it mentioned
When auditors come knocking—or worse, when bad actors strike—not having accurate and complete event logs can make all the difference in how your organization survives the encounter.However, users are often understandably more focused on day-to-day operations and only think to look for this information once it’s needed (and when time is of the essence).The good news is that all the information you need—including where to find changes in Veeam server user access permissions, failed login attempts, and failed RDP connections—is available in several different locations, including:Windows Event Viewer Veeam Backup and Replication Audit logs for performed restores Veeam One Audit log The individual application log(s) Windows Event ViewerMany Veeam activities (success, warning, and failures) get logged to the Windows Event viewer by default. To see these events from within the Veeam Backup and Replication (VBR) server, open the Windows Event Viewer console and Migrate to the Veeam Backup node
One of the must-have features for providing access security for any sensitive application is the ability to implement multi-factor authentication (MFA) as part of the login process. The release of Veeam Backup and V12 added the ability to enable Multi-factor authentication for logging into the Veeam console (including the remote console). The details:Before discussing the setup and configuration of MFA, we should discuss what MFA apps are supported.Veeam Backup and Replication supports Time-Based One-Time Passwords (TOTP) as per RFC 6238 installed on a mobile device. For example, the following MFA TOTP applications are supported:Microsoft Authenticator Google Authenticator LastPass Authenticator DUO Okta Verify Many more are listed if you do a quick internet search ;)A console auto-logout time can also be set to ensure that a user gets logged out of the Veeam console after a configurable period of inactivity. Configuring MFA:Step 1:Access the Users and Groups selection on the options
Protecting DB2 servers with Veeam Backup and Replication is pretty straightforward. The IBM DB2 can be protected with the following Veeam jobs:Classic VM backup jobs Veeam Agent for Linux (VAL) jobs Enhanced NAS backup jobsTo ensure that the DB2 DBs are in a consistent state, IBM DB2 commands will need to be called to either create a native DB2 database backup or to put database(s) in a quiesced state so that a clean application backup of the database can be made. DB2 has several ways to perform backups from the CLI that make backups of the database reasonably simple.Native flat file backup can be performed against an offline or online DB. The options include using full, incremental, and differential backups A simple pause and resume of the DB2 writer that can be used to store (and VMware) snapshots that Veeam Backup and Replication can leverage. The ability to leverage storage array snapshots as restore points through a component called IBM DB2 ACS. I will not discuss this process as
An advantage of software-defined Veeam products is that they can be installed in many different ways and on any hardware your company owns and uses. They can be installed on-premises, or in any hyper-scale public cloud, you choose. To help customers architect, size, and secure the various Veeam products and features, the Veeam Solutions Architect team has created Veeam Security Blueprints (SBP) and they are publicly accessible. Veeam Security Blueprints can be found at https://www.veeam.com/security-blueprints.html Veeam Security Blueprints (SBP) are short (3 – 4 pages) scenario-based reference architectures covering common scenarios seen in the field. Types of scenarios include:On-premises environment using multiple different vendor storage targets (HPE, Cisco, Pure, Exagrid, Cloudian, Lenovo, Zadara, Hitachi Vantara). Veeam cloud backup products (Veeam Backup for Azure, GCP, AWS) VMC on AWS and hybrid environments Veeam Plugins for Enterprise Applications (Oracle and Microsoft SQL)
Veeam storage functionsIs Veeam the most significant storage company that no one knows about? One of the essential features of any Veeam Backup and Replication architecture is the storage hardware that the backup target or backup repository will sit on. The repository performance, features, and scalability are critical to ensuring that the Veeam deployment will meet customers' needs for quite a while. Unfortunately, this is the component that many customers tend to make bad decisions, usually due to VARs and storage vendors trying to make the backup decisions for the customer. This is easy for the partner and storage vendor community to do because, as we all know - we at Veeam pride ourselves on the fact that the Veeam Backup and Replication suite is a software-defined and hardware agnostic backup storage platform. The partners, storage vendors, and even customers don't realize that Veeam also has another tag ling used internally - "Veeam is the largest storage company that no one
Veeam Recovery Orchestrator (VRO) V6 can provide orchestration of recoveries to different locations (original location, a secondary site, or Azure) from backups or secondary backups. VRO The feature that I love the most about VRO (well, really one of the many features) is the ability to easily have VRO scan multiple backup restore points of a server (virtual or physical) for malware infections that may have been missed before a backup so bad backups don’t get put back in production! VRO will use a the update AV software installed on the mount server to perform iterative scans of multiple restores to find a “clean” restore point to recover from. This can be performed in a few easy steps. First, launch the orchestration plan for the server(s) you want to restore, right-click on it and select run. Step through the wizard until you reach the “Ransomware scan” page. If you want to limit the number of restore points scanned, you can set it here by checking the checkbox and entering a val
The Veeam Backup for AWS, Azure, and GCP products supplies an effortless way to protect workloads running in one of the hyperscale public clouds. Workload protection is done by taking native snapshots and copying snapshots to object storage for a defined period. A full instance recovery and file-level recoveries can be performed from the backup. But this only scratches the surface of what Veeam can do with a cloud-based backup. To use advanced storage functions like Instant VM recovery directly to an on-premises hypervisor, full instance recovery into another hyperscale cloud, or copying backup files to an on-premises harden repository will require Veeam Backup and Replication to be integrated with Veeam Backup for AWS, Azure, and GCP through what’s called an “external repository”. The Veeam Backup and Replication external repository is a read-only connection to the Veeam Backup for AWS, Azure, and GCP object-based storage repository. It allows Veeam Backup and Replication to perform
One of the many features that Veeam Backup and Replication provide to ensure an organization can successfully recover their backups every day and in case of a malware emergency is the ability to scan your backup images for latent malware before they are restored. This goes beyond the ability to scan for possible entropic encryption of a server during backup by scanning for the malware that has caused the encryption. If an infection is detected then the restore can be aborted, or the server can be restored but not get connected to a network.Secure Restore is the name of the Veeam Backup and Replication feature that does the malware scan before restoring. Secure restore can restore Windows servers fromVMs from any hypervisor Physical servers that are protected with Veeam Agent for Windows. From backups stored on immutable block storage. From backups stored on immutable object storage. From backups stored on NFS/SMB shares Secure restore can be run before recovery is performed from the
The environment described is that of a Veeam Cloud Service Provider (VCSP) infrastructure providing data protection services for a tenant/customer workload. The VCSP utilizes the Veeam Service Provider Console (VSPC) solution to provide licensing, consumption monitoring, and reporting for the Veeam platform. The tenant is described as running 1 Veeam Backup & Replication server protecting up to 1,000 VMware/Hyper-V VMs and up to 9 Veeam Backup for Public Cloud Appliances protecting up to 270 VMs, for a total up to 1,270 VMs. The tenant also protects up to 10,000 M365 Users and less than 250 Veeam Backup Agents managed by VSPC.
The environment described in this architecture consists of a main datacenter with a single Kubernetes cluster running Red Hat OpenShift Container Platform with multiple application namespaces on Azure Cloud Computing services. All local snapshots will be exported to an immutable backup repository to protect against deletion or encryption attacks. Additionally, backups are imported onto a standby cluster for disaster recovery.
Updated - V12.1The environment described in this architecture builds of the 1000 VMs “Single production datacenter to offsite datacenter” scenario. The local repositories are defined as the Performance Tier of a Scale-out Backup Repository (SOBR). The Capacity Tier is a “public-cloud” Object Store. This reference architecture covers capacity tier copy + move operations. It accounts for the potential concurrency of primary backup and offload operations by detailing additional required resources. Each VM and physical server has an average of 200 GB of used storage space (1000 VMs and 100 servers).
The environment described in this architecture is one main datacenter containing 500 TB of NAS data. The NAS environment contains 5 shares and 200 million files. All backups will be targeted to Immutable Object Storage. The general-purpose proxies and gateways will be collocated on the same server hardware.
Updated - V12.1The environment described in this architecture is one main datacenter containing 10,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of used storage space. All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Proxies are installed on physical servers and will use the secure network (NBDSSL) backup mode. The repositories are on Cisco UCS 23260 Storage Servers.
The processes described in this architecture utilize the Veeam Data Platform Premium, adding value to existing security countermeasures.An Incident Response Plan (IRP) has been developed to facilitate a quick and systematic response to a cyber-attack or a data security incident. The IRP is part of a broader Disaster Recovery Plan (DRP) and covers the following response steps: preparation, detection and analysis, containment eradication and recovery, and post-incident activity.What is described here is purposefully focused on Veeam and assumes other counter-measures and processes have been implemented, for example, clear lines of communication and assigned responsibilities in the event of a breach.
The environment described in this architecture is one main datacenter containing 1000 VMS and 100 physical servers. Each VM and physical server has an average of 200 GB of used storage space. All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method. The backup target will be a server with an attached SAN array.
Updated - V12.1The environment described in this architecture focuses on a 3 node RAC, 10 TB database instance. Most environments have multiple database instances, across multiple servers that may range from a few gigabytes (GB) in size to multiple terabytes (TB). This scenario can be used as a baseline to deploy for those multiple database environments.
Updated - V12.1The environment described in this architecture focuses on a single, 1 TB database instance. Most environments have multiple database instances, across multiple servers that may range from a few gigabytes (GB) in size to multiple terabytes (TB). This scenario can be used as a baseline to deploy for those multiple database environments.
The environment described in this architecture is a Microsoft 365 (M365) deployment with 10,000 users. Included within the protection scope is Mailboxes, Archive Mailboxes, and OneDrive for Business. Additionally, 1,000 SharePoint Online sites and 1,000 Teams. Total Space consumed in Microsoft 365 across the above applications is 100TB. All backups will be targeted to an object storage repository in Azure and copied to Azure Archive storage using a backup copy job. Veeam Backup for Microsoft 365 will be installed on Azure VMs.
Updated - 12.1The environment described in this architecture is one EPIC ODB Caché 25TB production database. Backups will be performed from a “backup host” where clones of the quiesced database production LUNs have been presented and exposed as NFS shares. Backups will be targeted to a primary backup repository and copied to a secondary offsite location. Proxies are installed on a physical server and use the network transport (NBD) method. The backup target will be Veeam Hardened Repositories set for Immutability.
Updated - V12.1The environment described in this architecture is three ROBO sites containing 100 VMs and ten physical servers. Each VM and physical server has an average of 200 GB of used storage space. All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method.
The environment described in this architecture is a Veeam Backup for Google Cloud deployment with 1000 workloads to protect. The protection scope includes Google Compute Engine(GCE) and CloudSQL. All backups will be targeted to an object storage repository in Google Cloud Storage(GCS) with Standard Storage Class and archived to GCS with Archive Storage Class.
The environment described in this architecture is a Microsoft 365 deployment with 2000 users.Veeam One will provide monitoring, alerting, and telemetry metrics for the Veeam Backup for M365 (VB365) environment installed in Microsoft Azure. The Veeam ONE database will be hosted on a Microsoft SQL Standard Server.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
