Articles

This article deals with the use of Object Storage as a primary backup repository. It can also be used to store a secondary backup copy. The goal is to use the immutability property of object storage to secure backed up data against Ransomware, etc. In practice, we will describe two variants. The first is when the object storage is S3 compatible (in our case NetApp ONTAP). And the second is Microsoft Azure Blob Storage (Storage account).

NetApp ONTAP supports a combination of file, block, and object protocols. We can operate object storage with access using the S3 API. Within an ONTAP cluster, we can configure and manage an S3 (Simple Storage Service) Object Storage Server that works with data as S3 objects. Management is traditionally possible using ONTAP System Manager or ONTAP CLI.

Object storage is the youngest type of storage. They are often offered as a cloud service, but they can also be operated on-premises (as a special appliance or software on a server). In this article, we will look at a comparison of the main features with block and file storage. We will also discuss the general features and principles of object storage. A large representative of this type of storage is Amazon S3, which defines an interface for accessing the S3 REST API. Many manufacturers support this API and their solutions are referred to as S3 Compatible Storage / S3 Object Storage.

This article is about Veeam Hardened Repository. That is, a repository that supports Immutability. It is built on a server with a Linux operating system and storage space. We will practically describe the deployment of Managed Hardened Repository and its use for storing backups. This means that we will use Veeam Hardened Repository ISO for installation. For simplicity (this is for testing) we will use a virtual machine in a VMware environment.

Secure storage of backups is crucial today. It is important to ensure that our backups are not deleted or corrupted. We will explore the possibilities of Immutable Backups. We need a Storage System that supports Immutability. This can be a cloud service, hardware device, or software (for example a Linux server acting as a Hardened Repository). In Veeam, we will create a Backup Repository from it with activated Immutability.

When we work on a computer under a domain account and access resources on the network where permissions are controlled using security groups. If our account is included in a new group (to gain new access), the change will only take effect after the computer is restarted or the user logs out and logs in. In the case of Kerberos authentication (not NTLM), we can trigger a new acquisition of tickets (with the klist command) that contain the current group membership. Under certain conditions, we will immediately gain access given by the new group. First, in the article, we will look at displaying a list of groups of which the current user is a member.

A brief description of the in-place upgrade of Veeam ONE 12 to version 12.2. The whole process is simple and hassle-free. It should work similarly for other versions as well.

How to better and more securely resolve service accounts for running services or scheduled tasks in a Microsoft Active Directory domain environment. Managed service accounts have been available for a long time. Managed Service Accounts were added with Windows Server 2008 R2. They help address service identities with greater security and reduce management overhead. The administrator doesn't have to worry about passwords because secure password management for the accounts is provided by the Windows operating system. They are used to non-interactively run applications, services, processes, or tasks that need a secure identity (credential).

The way backup files are stored has been modified in Backup & Replication 12. Primarily Per-Machine Backup with Separate Metadata Files is used. The Backup Copy Job has also changed quite a bit. In this article, we'll take a look at how the new Backup Copy Job works. And we'll practically describe copying backups to a remote location when the data is large and a complete transfer over the WAN would take too long. We will use Seeding and transfer the data (initial Full Backup) offline on an external USB drive. After that, we map the copy job to the transferred data.

We will look at backing up Oracle databases using the Veeam Plug-in for Oracle RMAN. We will describe a newer option (from VBR version 12), when backup is controlled from Veeam Backup & Replication Server. That is, centrally as common backup types. This is the managed mode (Managed Mode) of the Veeam Plug-in. Protection Groups are used to deploy and manage plug-ins (as well as agents).