Self-Managed Deployment

Account and Roles LicensingAccount and RolesLog in or create your My Account login if it's your first time.My Account is a central place to access your Veeam® products, license keys, Veeam Support, technical documents and much more! You can also use this same login to access resources on Veeam.com, Veeam University and Veeam Community.Once you have access to My Account, you will be able to:Obtain your licensing: Select License Management > Production to manage and obtain your Veeam licensing (License Administrator only). The License Administrator can download the license key directly from My Account and the other users can request the license key to be sent via e-mail to the primary license administrator.Download products: Select Products to access and download your product(s). When accessing the Products tab, a list of products appears based on the licenses owned. If you cannot see a product that you are looking for on that page, you can access “All Veeam Products”.Assign a License

An assumption for this course is that you are using the latest product versions and package updates. Check for available updates manually if required. With Veeam Backup & Replication via Microsoft Azure Plug-in for centralized and unified management and monitoring of hybrid-/multi-cloud environments, which provides you with a greater portability of backups and opportunity to store data on premises as well as across any of the supported public cloud providers. Integration with Veeam Backup & Replication Deployment Guidelines and PrerequisitesBefore you start using Azure Native Backup and Recovery, make sure to:Digest an overview & sizing best practices by Veeam Solution Architects Study hardware, software, and infrastructure limitations and considerations Ensure that all required ports are open and user accounts that you plan to use have the required permissions Add custom sets of worker profiles to specify VM sizes of worker instances that will operate in different regions

  Business Considerations Deployment Considerations Deployment Scenarios ​​​​​​​Infrastructure DeploymentBusiness Considerations1. Risk Assessment:Identify potential risks and threats to the business, considering natural disasters, cyberattacks, human errors, and other possible incidents.2. Data Classification and Prioritization:Classify and prioritize data based on its importance to the business. Determine the maximum acceptable downtime for each critical function. As a part of Veeam Recovery Orchestrator configuration we will want to know what critical workloads need to be protected and recovered. We also need to know how these interdependent workloads need to be group during the recovery orchestration.3. Recovery Locations:Assess the existing technology infrastructure to which locations are best suited for restoration of this data. Select appropriate technologies, such as, hardware, networking, and cloud services.4. Recovery Time Objective (RTO) and Recovery Point Objective (RPO):De

👉 Start with the module marked in green (Saved)—this is the first step in your onboarding process.——————————————————————————————————————————Veeam® University FREE is an onboarding and training program to help you gain knowledge on basic features or advanced functionality to speed up implementation and realize the full value of Veeam as quickly as possible.Below you can see a summary of your onboarding experience for Veeam Backup for Microsoft 365:Step 1: Account, roles and licensing Step 2: Backup and infrastructure deployment Step 3: Restoration capabilities Step 4: Monitoring Step 5: Advanced featuresBeyond the mandatory modules, explore the recap of useful resources.You can contact us at any time at veeam.customersuccess.onboarding@veeam.com to answer any questions you may have during your Veeam experience.We wish you continued success! Thank you for choosing Veeam. Continue to Step 1 Account, roles and licensingReturn to Veeam University Free Home 

An assumption for this course is that you are using the latest product versions and package updates. Check for available updates manually if required. You can also configure whether Veeam Backup for Microsoft 365 will notify you when new versions appear on Veeam servers and allow Veeam Backup for Microsoft 365 to download available updates automatically.  Moving further, we’ll guide you through all the necessary steps to your best experience which are laid down at the diagram below. Step 1: Account, roles and licensingStep 2: Backup and infrastructure deploymentDeployment options Infrastructure planning & installation package Supported storage & retention policies Selecting backup scope & creating a backup job Backup job scheduling options Creating a backup copy jobStep 3: Restoration capabilitiesVeeam Explorers™ How to restore in 1-2-3Step 4: MonitoringReports Notifications Advanced monitoring with Veeam ONE™Step 5: Advanced featuresSelf-restore portal Job best practices

  Product Overview ComponentsProduct OverviewVeeam Recovery Orchestrator allows for a much larger and broader way to perform BCDR and ransomware verifications. It too lets you validate your disaster recovery environment without impacting the production infrastructure. Furthermore, it provides automation and scheduling of tests and reports.Veeam Recovery Orchestrator works with Agent Backup Jobs, Virtual Backup Jobs, Backup Copy Jobs, Replication Jobs, and SAN Integration.It's important to understand there are three core components that make up the Veeam Recovery Orchestrator solution. These can be deployed on the same server or on different servers. It may be applicable to utilize a full version of SQL server depending on size and availability. ComponentsVeeam Orchestrator Server Service is responsible for managing orchestration plans and administering user roles and permissions Veeam Orchestrator Web UI is a web-based user interface that allows users to interact with the Veeam Orchest

By now, you have an operational backup environment, some initial backups finished, a fine‑tuning set and are successfully monitoring and reporting. Congrats! You’ve also likely tried a test restore (hopefully you haven’t needed to do a real restore, but if you have, we’re glad you had a backup). If you haven’t, or you want to dive a bit deeper, here are some resources to help explain and guide you through the restore process.You can explore your Microsoft 365 data four key ways:1. Exploring backup jobs When exploring backup jobs, Veeam Backup for Microsoft 365 loads the latest restore point that was created by the selected job.2. Exploring single organizations When exploring a single organization, Veeam Backup for Microsoft 365 merges and loads the latest restore points that have been created by each backup job of the selected organization, including objects (i.e. users) no longer protected in a job.3. Exploring all organizations When exploring all organizations, Veeam Backup for Micro

The goal of this step is to give you a high-level understanding of the core fundamental components of Veeam Backup & Replication. We will also guide you through some general backup strategy considerations and infrastructure deployment requirements. Veeam Backup and Replication is a comprehensive solution that allows you to back up and restore your data residing in hybrid and multi-cloud environments:Cloud: AWS | Azure | Google | IBM Virtual: VMware | Hyper-V | Azure Local | Nutanix AHV | Proxmox VE | HyperCore | oLVM |RHV Physical: Windows | Linux | MacOS | Unix | NAS Applications: Microsoft | Oracle | SAP Hana | PostgreSQL | MongoDB Backup JobVeeam Backup & Replication does not install agent software inside the VM guest OS to retrieve VM data. To back up VMs, it leverages VMware vSphere snapshot capabilities. When you back up a VM, Veeam Backup & Replication requests VMware vSphere to create a VM snapshot. The VM snapshot can be thought of as a point-in-time copy of a VM t

Simple deployment Advanced deploymentYour Veeam Backup & Replication deployment can run on-premises or in private, public and hybrid-cloud environments. The prerequisites and how these components work for each environment are remarkably similar. IT organizations have the flexibility to choose from distinctive designs based on their current requirements.On-premises deployments: an on-premises deployment can easily scale out from simple to additional installations. Service providers deployments: Veeam Backup & Replication is employed by service providers who offer BaaS to their customers. Cloud workload deployment: Veeam Backup & Replication can be deployed on a cloud VM and protect a wide variety of workloads.NOTE: This is different from the cloud-native appliances that we have for AWS, Microsoft Azure and Google Cloud. Simple deploymentSimple deployment includes the installation of all components onto a single all-in-one server. This machine can be either virtual or physica

Business Considerations Deployment Considerations   Infrastructure DeploymentBusiness Considerations1. Risk Assessment:Identify potential risks and threats to the business, considering natural disasters, cyberattacks, human errors, and other possible incidents.2. Data Classification and Prioritization:Classify and prioritize data based on its importance to the business. Determine the maximum acceptable downtime for each critical function. As a part of Veeam Recovery Orchestrator configuration we will want to know what critical workloads need to be protected and recovered. We also need to know how these interdependent workloads need to be group during the recovery orchestration.3. Recovery Locations:Assess the existing technology infrastructure to which locations are best suited for restoration of this data. Select appropriate technologies, such as, hardware, networking, and cloud services.4. Recovery Time Objective (RTO) and Recovery Point Objective (RPO):Define specific RTO and RPO me

Protecting AWS, Azure and GPC instances:Azure and AWS deployments In the case of Microsoft Azure, there is a certified and pre-installed application available in Azure Marketplace. Likewise, in the case of AWS, the application is certified and available from AWS Marketplace. It comes preinstalled into an AWS EC2 instance and it is a matter of choosing the instance type based upon requirements. Veeam Backup & Replication is different than native cloud backup appliances. See our dedicated public cloud modules for more information:Native AWS Backup and Recovery Native Azure Backup and Recovery Native Google Backup and Recovery Veeam ONEVeeam ONE provides complete visibility of the virtual and backup infrastructure and allows you to:Manage, view and interact with alarms and monitoring data Analyze performance of virtual and backup infrastructure objects Keep an eye on multi-tenant environments Track the efficiency of data protection in the virtual environment Generate reports and admin

Veeam Explorers SureBackupVeeam ExplorersVeeam Explorers™ are tools available within Veeam Backup & Replication that allow users to perform granular recovery of specific data within a backup. There are several types of Veeam Explorers, each designed to address specific data recovery needs.Here are the main Veeam Explorers and how they are used:Veeam Explorer for Microsoft Active DirectoryThis explorer enables users to recover individual objects from an Active Directory backup. It is useful for recovering data from Active Directory failures or accidental deletions.Veeam Explorer for Microsoft SQL ServerThis explorer enables users to recover individual databases, tables and other SQL Server objects from their backups caused by failures or accidental deletions.Veeam Explorer for OracleThis explorer is designed to help Oracle database administrators recover their Oracle databases and any related components like tablespaces, schemas and individual objects. This includes tables, stored p

Additional component and console considerations Add additional backup proxies Add additional backup repositories Creating a Backup Job Generate and review reports Understanding Veeam’s console and doing basic configurations such as email notifications and backing up Veeam’s database are important before you get started on your backup journey. Below, you’ll find a list of these configurations and a detailed video explaining how to do them.Veeam Backup & Replication configuration backup: this configuration backup takes a backup of your Veeam database. Your all-important Veeam Server configuration data is stored here, and backups let you restore to the same server or another server if that fails. Consider creating a repository that is offsite and not a part of your scale-out backup repository (SOBR) for your data destination. Configure email notifications to stay aware of your daily backup operations. Additional component and console considerationsThere are some important things you n

Using the 3-2-1 Rule with Veeam Top Veeam Considerations Define Retention Objectives Define Recovery Objectives Security ConsiderationsUsing the 3-2-1 Rule with VeeamThis is very versatile nowadays, but with Veeam, you can take it to the next level — to the 3-2-1-1-0 Rule, where each of the following implementations would count towards a successful configuration. Consider deploying one or multiple solutions into your environment:There should be (3) copies of data: Backup Copies and Scale-out Backup Repositories. On (2) different media: consider replicating Virtual Machines to another location Veeam Replication and Continuous Data Protection. With (1) copy being off site: copying or moving data offsite or into the cloud to free up your local backup repository Backup copies for longer retention. Replication to create a copy of data at another location. Scale-out Backup Repositories to copy and/or move data to tier it into the cloud. With (1) copy being offline, air-gapped or immutable:

Below is a summary of resources recommended by our experts.  Veeam Kasten User Guide: see here for our product user guide to get an overview of installing and managing Veeam Kasten  Veeam Kasten Best Practices Guide: see our best practices for deploying Veeam Kasten on single or multiple Kubernetes environment  Veeam Alliance Technical Programs: see here for a list of Veeam Kasten compatible solutions  Customized Veeam Search Engine: use this custom tool to search official Veeam content  Veeam Help Center Technical Documentation: access our directory of user guides, product overviews, release notes, what's new, etc. for all Veeam products  Community Resource Hub: grow your Veeam skills or share your knowledge or experiences, and become a Veeam Legend  Kasten Hub Page: ask questions, browse shared troubleshooting tips, share ideas, feedback, best practices and connect with other users inside and outside of Veeam.   Veeam Knowledge Base: find answers for customers' frequently asked quest

Step 7.1 Multicluster Manager Step 7.2 Kanister Blueprints Step 7.4 GitOps Deployment Strategy Step 7.5 Transforms in "Veeam Kasten for Kubernetes"Step 7.1 Multicluster ManagerThe K10 multi-cluster manager simplifies K10 operations across multiple Kubernetes clusters.Administrators define primary-secondary relationships between their K10 instances. Primary K10 instances provide a single entrypoint and dashboard for administrators to manage secondary instances. Additionally, Primary K10 instance can distribute the licenses to the secondary instances through license leasing, eventually reducing the overhead to manage licenses in multiple places.K10 resources, like Policies and Profiles, are defined in the primary instance and distributed to secondary instances. Secondary instances enact their policies and the secondaries' actions and metrics are summarized in the primary instance. There are multiple ways to bootstrap K10 instances for the multicluster setup, we will be using `k10multiclu

Always upgrade; we are constantly fixing bugs and adding important features (Kasten releases every 2 weeks), so do not stay on an outdated version for comfort.K10 needs at least 50% free space in Catalog Storage for upgrades. Check the K10 dashboard under Settings → System Information → Upgrade status for details on the current version, latest version, and catalog storage space. For additional details on the K10 upgrade, refer to the K10 user guide.Currently, upgrades are only supported across a maximum of four versions (e.g., 6.0.2 -> 6.5.6). If your K10 version is further behind the latest, a step upgrade process is recommended where you can use the --version flag with helm upgrade to control the version jumps.  Get ready for Step 7 of your onboarding journey. At the next step, we will explore advanced features of Veeam Kasten like multicluster manager, blueprints, Openshift virtualization backups and GitOps based deployment strategy.If you need more help getting started, you can

Step 5.1 MonitoringK10 enables centralized monitoring of all its activity by integrating with Prometheus. In particular, it exposes a Prometheus endpoint from which a central system can extract data.K10 can be installed with Grafana in the same namespace. This instance of Grafana is setup to automatically query metrics from K10's Prometheus instance. It also comes with a pre created dashboard that helps visualize the status of K10's operations such as backup, restore, export and import of applications.Using K10's Prometheus EndpointBy default, Prometheus is configured with persistent storage size 8GiB and retention period of 30d. That can be changed with:--set prometheus.server.persistentVolume.size=<size>and --set prometheus.server.retention=<days>.Prometheus requires Kubernetes API access to discover K10 pods to scrape their metrics. Thus, by default Role and RoleBinding entries are created in K10 namespace. However, if you set prometheus.rbac.create=true, global ClusterR

Step 4.1 Policy Presets Step 4.2 Profiles Step 4.3 Restoring Applications Step 4.4 Application Mobility Step 4.5 K10 Disaster RecoveryStep 4.1 Policy PresetsA PolicyPreset custom resource (CR) in K10 is used to save and reuse configurations of K10 Policies. PolicyPresets specify schedule, retention, location, and infrastructure information, while Policies specify application-specific details. Users can find detailed information about schedule settings in the Policy Scheduling section.Create a PolicyPresetThe example in the demo illustrates creating a preset for policies that execute daily, retain 1 daily and 1 weekly snapshot, and export every daily snapshot with a different retention schedule.Step 4.2 ProfilesLocation ProfilesK10 can usually invoke protection operations such as snapshots within a cluster without requiring additional credentials. While this might be sufficient if K10 is running in some of (but not all) the major public clouds and if actions are limited to a single clus

Step 3.1 Installing Veeam Kasten for Kubernetes on Microsoft Azure Kubernetes Service (AKS) Step 3.2 Preparing for an Air-Gapped Installation of Veeam Kasten for Kubernetes (Optional) Step 3.3 Veeam Kasten for Kubernetes License management Step 3.4 Veeam Kasten for Kubernetes RBAC (Authorization) Step 3.5 Operator based Installation Step 3.6 OpenShift Authentication Setup for Veeam Kasten for KubernetesStep 3.1 Installing Veeam Kasten for Kubernetes on Microsoft Azure Kubernetes Service (AKS)This guide helps you install Veeam Kasten for Kubernetes. Veeam Kasten for Kubernetes helps backup, restore, and disaster recovery for your Kubernetes applications. Two of the most common install methods are Helm installations and Operator-based installations. The steps in this section will show examples of a Helm installation using Azure AKS. For Operator-based installations, see the demo in Step 3.4 for an example using Red Hat OpenShift. Other environment-specific examples can be found in our of

Step 2.1 Primary and Target storage Selection Step 2.2 Business continuity and DR (Disaster Recovery) planning   Step 2.3 Preparing for Air-gapped Installation of K10 (Optional)   Step 2.4 Security RequirementsStep 2.1 Primary and Target storage SelectionPrimary Storage For Kubernetes platforms that offer both Container Storage Interface CSI and in-tree storage provisioner options, always choose the CSI provisioner. CSI drivers represent the future of storage operations in K8s as the legacy in-tree plugin-based provisioners have already been deprecated and will be removed in subsequent versions of K8s. The PVCs (Persistent Volume Claim) (Persistent Volume Claim) provisioned by these legacy in-tree provisioners are being migrated to CSI drivers. Verify that any CSI storage provisioners support VolumeSnapshots. This may be indicated in the documentation from the storage provider, but it can also be validated using K10 Tools. K10 strongly recommends using a CSI storage provisioner as a pr