Articles

This article addresses an error for which I found no information on the internet. The error "Backup is not in user's control scope" appeared in Veeam Backup & Replication after launching a new backup using Oracle RMAN. Veeam Plug-in for Oracle RMAN is used in Standalone Mode, meaning backup management is handled on the Oracle server side. Two Oracle DB servers are configured as Oracle Real Application Cluster (RAC).

The final part of the series dedicated to managed Veeam Hardened Repository (VHR) installed from VHR ISO 2.0 and the use of Immutable Repository in Veeam Backup & Replication (VBR). In this part, we will show practical tests confirming that immutable files cannot be deleted, we will look at selected information via SSH on the server, and perform simple performance tests. At the end, we will provide a brief summary.

In the previous part, we focused on configuring the HPE ProLiant DL380 G11 server and installing the managed Veeam Hardened Repository (VHR) from VHR ISO 2.0. The goal is to obtain backup storage for Veeam Backup & Replication (VBR) that supports Immutability. In this part, we will look at adding the Hardened Backup Repository to VBR and using it for secure backup storage. We will show how to create a backup job, obtain information about immutability on backups, copy backup files, and also the option to move existing backups to the Hardened Repository.

One of the supported Immutable Storage options in Veeam Backup & Replication (VBR) is Hardened Repository (VHR). Veeam has been offering Managed VHR for some time, which is installed from the Veeam Hardened Repository ISO. We'll take a practical look at configuring an HPE ProLiant DL380 G11 server for the Hardened Repository function and installation from VHR ISO 2.0. The server is equipped with NVMe SSD drives and redundantly connected to the network using PortChannel (LACP). For installation, we'll use HPE iLO (Integrated Lights-Out) remote management.

One of the supported immutable storage options in Veeam Backup & Replication (VBR) is Hardened Repository (VHR). We will look at the properties and functions of VHR. We will focus on the variant where we install VHR from the ISO provided by Veeam, thereby obtaining a Managed VHR. We will describe how Immutability is set up and managed on backups (files), how the XFS file system is used, and what services run on the server.

The migration of an Exchange organization from version 2016 to Subscription Edition (SE) must be performed using Legacy upgrade. This means we install a new server that we add to the organization, configure it, and perform mailbox migration. In the last fifth part, we focus on completing the migration. We redirect all communications to the new servers and from them, update Exchange Hybrid, remove the original DAG, and uninstall Exchange from the old servers.

Migration of Exchange organization from version 2016 to Subscription Edition (SE) must be performed using Legacy upgrade. This means we install a new server, which we add to the organization, configure and perform mailbox migration. In the fourth part, we focus on moving mailboxes to new databases on new servers. This includes system and user mailboxes as well as public folder mailboxes. After moving all mailboxes, we can remove the original databases.

Migration of Exchange organization from version 2016 to Subscription Edition (SE) must be performed using Legacy upgrade. This means we install a new server that we add to the organization, configure, and perform mailbox migration. In the third part, we focus on mail flow using connectors, TLS certificates, mailbox databases using Database Availability Group (DAG), and logging (Exchange, SMTP, Message Tracking).

The migration of an Exchange organization from version 2016 to Subscription Edition (SE) must be performed using Legacy upgrade. This means we install a new server that we add to the organization, configure it, and perform mailbox migration. In the second part, we focus on configuring client access services (Client Access). This primarily involves the MAPI over HTTP protocol, Outlook on the web, and other Virtual Directories. We handle communication through HTTPS and do not address POP3 and IMAPS protocols.

The migration of an Exchange organization from version 2016 to Subscription Edition (SE) must be performed using a Legacy upgrade. This means we install a new server, add it to the organization, and perform the transition/move/migration. Finally, we remove the original servers. If we were running Exchange Server 2019 CU14 or CU15, we could perform a direct upgrade on the server (In-place upgrade), just like when installing a CU. In this first part, we'll look at basic information about the new Exchange Server SE version related to its deployment. And we'll describe the installation of a new Exchange server that will be integrated into the existing organization.