Onboarding for Veeam Kasten for Kubernetes

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

Account and RolesLog in or create your My Account login if it is 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 and Veeam University.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.Assign a License Administrator: If you have lost access to the License Administrator account or would like it to be changed, please create a licensing case. The following page shows a contrast of the functions available between License Administrator and a Case Administrator: https://www.veeam.com/kb2211. Assign Case Administ