Shulou(Shulou.com)06/02 Report--

Backup Hyper V virtual machine | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-hyper-v-virtual-machines?view=sc-dpm-1807

Host level backup and guest level backup

DPM can perform host-level or guest-level Hyper-V virtual machine backups. "at the host level, the DPM protection agent is installed on the HYPER-V host server or cluster to protect the entire virtual machine and the data files running on that host." If the guest level is adopted, the agent is installed on each virtual machine to protect the workload on that computer.

These two methods have their own advantages and disadvantages:

Host-level backups are flexible because you do not need to consider the type of OS running on the guest computer when running the backup, and there is no need to install the DPM protection agent on each virtual machine. If you deploy a host-level backup, you can restore the entire virtual machine or files and folders (project-level recovery).

Guest-level backups are useful if you want to protect specific workloads running on virtual machines. With host-level backup, you can restore an entire virtual machine or specific files, but it cannot be restored in the context of a specific application. For example, to restore a specific SharePoint project from a backed up virtual machine, you should perform a guest-level backup of that virtual machine. Note that if you want to protect data stored on the transmittal disk, you must use guest-level backups. Delivery allows the virtual machine to access the storage device directly without storing the virtual volume data in the VHD file.

Use DPM to back up Exchange | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-exchange?view=sc-dpm-1807

Why use DPM to back up Exchange

When deciding whether to back up Exchange data using Exchange 2013 native data protection or DPM, consider the following:

Native data protection provides:

Disaster recovery

Restore items that were accidentally deleted

Long-term data storage

Point-in-time database snapshot

However, if an application error, compromise, or security and malware events occur, native protection may not be sufficient. In these cases, DPM provides many advantages:

Less DAG required-Native protection requires additional Mailbox servers to host copies of the active data. You do not need to rely on DAG for backups with DPM protection.

Restore is simple-DPM provides simple centralized data recovery from point-in-time backups.

Long retention period-DPM provides a long retention period for backed up data. Local protection is only available for 14 days.

Consistent Microsoft workload backup-DPM provides a simple centralized backup and recovery process for Microsoft workloads, including Exchange, file servers, SQL Server, Hyper-V, and SharePoint.

Use DPM to back up SharePoint | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-sharepoint?view=sc-dpm-1807

Prerequisite restrictions for DPM backup SharePoint

By default, when you protect SharePoint, all content databases (and SharePoint_Config and SharePoint_AdminContent* databases) are protected. If you want to add custom content, such as a search index, template or application service database, or a user profile service, you need to configure the protection of that content separately. Make sure that protection is enabled for features that contain these types or for all folders that contain custom files.

SharePoint databases that use AlwaysOn can be protected from DPM 2012 R2 Update 5 or later.

SharePoint databases cannot be protected as SQL Server data sources. You can restore a single database from a farm backup.

Keep in mind that because DPM runs as a local system and backs up the SQL Server database, it requires sysadmin permission to SQL Server on the account. On the SQL Server you want to back up, set NT AUTHORITY\ SYSTEM to sysadmin.

For every 10 million items in the farm, there must be at least 2 GB of volume space for the DPM folder. This space is necessary for directory generation. To ensure that specific items (site collections, sites, lists, document libraries, folders, individual documents, and list items) can be recovered using DPM, directory generation creates a URL list that is included in each content database.

In the SharePoint farm, if you have a SQL Server database configured with a SQL Server alias, install the SQL Server client component on the front-end Web server that DPM will protect.

SharePoint 2013 does not support protecting application storage items.

DPM does not support protecting remote FILESTREAM. FILESTREAM should be part of the database.

Use DPM to back up SQL Server | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-sql-server?view=sc-dpm-1807

DPM protects:

Standalone SQL Server instance

SQL Server failover Cluster instance (FCI)

SQL Server AlwaysOn availability groups with the following preferences:

Secondary copy only

Master

Any copy

Why use DPM to back up SQL Server

DPM is designed to protect the advanced configuration of SQL Server.

DPM can be set to provide SQL Server protection service every 15 minutes.

DPM reduces possible conflicts between backup tools and SQL Server protection schedules.

DPM can protect SQL Server at the instance or database level. After you enable instance-level protection, DPM detects new databases on the appropriate instance and automatically adds them to its protection group.

The price of DPM is affordable. It is ideal for organizations with small SQL Server memory footprint and can scale for organizations with large SQL Server memory footprint.

DPM has a self-service recovery tool (× × T) that extends the SQL database self-service recovery options for database administrators.

If you are upgrading to SQL Server 2014 DPM, you will continue to back up the protected database after the SQL Server upgrade is complete. You should avoid backing up jobs during SQL Server upgrades.

Prerequisite restrictions for DPM backup SQL Server

If you have a database that contains files on a remote file share, protection will fail with an error ID of 104. DPM does not support the protection of SQL Server data on remote file shares.

DPM cannot protect the database stored on the remote SMB share.

Ensure that the availability group copy is configured as read-only.

You must explicitly add the system account NTAuthority\ System to the Sysadmin group on SQL Server.

When performing an alternate location recovery for partially included databases, you must ensure that the included databases feature is enabled for the target SQL instance.

SQL Server 2014 adds a new feature to create databases for local SQL Server in Windows Azure Blob storage. DPM cannot be used to protect this configuration.

There are some known problems with the backup preference "preferred secondary copy" for the SQL AlwaysOn option. DPM always backs up from the secondary copy, and if there is no secondary copy, the backup fails.

Use DPM to back up client computers | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-workstations?view=sc-dpm-1807

Conditions and restrictions for DPM backup client computers

Ensure that the client computer you want to back up is in the DPM server domain or in a domain that has a two-way trust relationship with the DPM domain.

To set up client computer protection, install the DPM protection agent on it. If Windows Firewall is configured on the client computer, the agent installation will set the required firewall exception. If you need to reset the firewall, you can reconfigure it by running SetDpmServer.exe.

DPM can perform backups on client computers that are physically or wirelessly connected to the local area network (LAN) or through × × backup. To achieve × × backup, you need to enable ICMP on the client computer.

Each DPM server can protect up to 3000 client computers. When protecting client computers on a large scale, Microsoft recommends that you create multiple protection groups and stagger the recovery point time for those protection groups. The more clients that belong to the protection group, the longer it takes to enumerate the changes in the protection group.

Backup file data using DPM | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-file-data?view=sc-dpm-1807

File server end-user recovery (EUR) is not supported if newer backup storage (MBS) is used. The file server EUR relies on the Volume Shadow copy Service (VSS), which is not used by modern backup storage.

Backup system status and bare metal | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-system-state-and-bare-metal?view=sc-dpm-1807

System status and content that can be protected by bare metal backup

System Center Data Protection Manager (DPM) can back up the system state and provide bare metal recovery (BMR) protection.

System state backup: back up operating system files so that they can be recovered if the computer is started but the system files and registry are missing. System state backups include:

Domain members: startup file, COM+ class registration database, registry

Domain controllers: Active Directory (NTDS), startup file, COM+ class registration database, registry, system volume (SYSVOL)

Computers running the cluster service: in addition, back up the cluster server metadata

Computers running certificate services: in addition, back up certificate data

Bare metal backup: back up all data except user data on operating system files and critical volumes. By definition, BMR backups include system state backups. Provide protection when the computer cannot be started and you need to restore everything.

How system state backups work

When the system state backup is running, DPM communicates with WSB to request a backup server system state. By default, DPM and WSB use the drive with the most free space and save information about the drive in the PSDataSourceConfig.XML file. This is the drive that WSB will use for backups.

You can customize the drive that DPM uses for system state backups. To do this, on the protected server, go to drive:\ Program Files\ Microsoft Data Protection Manager\ DPM\ Datasources. Open the PSDataSourceConfig.XML file for editing. Change the value of the drive letter. Save and close the file. If you have a protection group to protect the system state of your computer, run a consistency check. If the consistency check generates an alert, click the modify Protection Group link in the alert, and then step through the wizard. When finished, run the consistency check again.

Note that if the protection server is in a cluster, the cluster drive may be selected as the drive with the most free space. It is important to be aware of this, because if the drive ownership has been switched to another node and the system state backup is running, the drive will be unavailable and the backup will fail. In this case, you need to modify the PSDataSourceConfig.XML to point it to the local drive.

Windows Server backup (WSB) creates a folder called WindowsImageBackup in the root directory of the drive. When WSB creates a backup, all data is placed in this folder. When the backup is complete, this file is transferred to the DPM server. Please note:

This folder and its contents are not cleaned up after the backup or transfer is complete. The best way to think about this is to reserve space for the next backup.

This folder is created each time a backup is performed. The time / date stamp will reflect the last time you made a system status backup.

Prerequisites and limitations for BMR backup

BMR is not supported for computers running Windows Server 2003 or client operating systems.

The BMR and system state of the same computer cannot be protected in different protection groups.

The DPM server cannot protect itself with BMR.

BMR does not support short-term protection of tapes (D2T). Long-term storage to tape (D2D2T) is supported.

Windows Server Backup must be installed on the protected computer in order to implement BMR.

For BMR protection (unlike system state protection), DPM does not have any space requirements for protected computers. WSB transfers the backup directly to the DPM server. Note that the transfer job is not displayed in the DPM job view.

If you are using modern backup storage and want to increase the default copy size of BMR to more than 30 GB, use the registry key: HKLM\ Software\ Microsoft\ Microsoft Data Protection Manager\ Configuration ReplicaSizeInGBForSystemProtectionWithBMR (DWORD).

If newer backup storage is used, SystemState and BMR backups consume more storage because of ReFS clones (compared to older storage). Each SystemState or BMR backup is a complete recovery point. To alleviate this storage consumption problem, you may need to:

Plan less SystemState or BMR recovery points

Shorten the retention period of the recovery point

Increase the available storage for SystemState or BMR backups.

Backup and restore VMware virtual machines | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-vmware?view=sc-dpm-1807

Supported VMware featur

When backing up VMware virtual machines, DPM 1801 and later provides the following features:

Agentless backup: DPM does not need to install proxies on vCenter or ESXi servers to back up virtual machines. Instead, you only need to provide the IP address or fully qualified domain name (FQDN), as well as the login credentials used to authenticate the VMware server through DPM.

Cloud integrated backup: DPM protects workloads on disk and cloud. DPM backup and recovery workflows help you manage long-term retention and off-site backups.

Detect and protect VM:DPM managed by vCenter detect and protect VM deployed on a VMware server (vCenter or ESXi server). As the deployment size increases, use vCenter to manage the VMware environment. DPM also detects VM managed by vCenter, which protects large deployments.

Folder-level automatic protection: vCenter allows you to organize VM in VM folders. DPM detects these folders and allows you to protect folder-level VM and include all subfolders. When you protect a folder, DPM protects not only the virtual machines in the folder, but also the virtual machines that are added later. DPM detects new VM every day and automatically protects them. When you organize the VM in a recursive folder, DPM automatically detects and protects the new VM deployed in the recursive folder.

DPM protects VM stored on local disk, network file system (NFS), or cluster storage.

DPM protects VM migrated for load balancing: when VM migrates to achieve load balancing, DPM also automatically detects and continues to protect VM.

DPM can restore files / folders from Windows VM instead of the entire VM, which helps restore necessary files more quickly.

Extend protection for clustered VMware servers

In large VMware deployments, a single vCenter server can manage thousands of VM. DPM supports extended protection of VMware server clusters. The new extension removes the limitation of the one-to-one relationship between the VMware cluster and the DPM server. You can add VM to a protection group on any identified DPM server. Extended protection applies only to VM hosted on servers running Windows Server 2012. You can use multiple DPM servers to protect virtual machines managed by a single vCenter server. However, only one DPM server can protect VM or folders at a given time. VM and folders that have been protected by one DPM server cannot be selected by another DPM server. To deploy extended protection, you must have at least two DPM servers. In the following graphical example, D1 and D2 are visible to all virtual machines hosted on nodes N1, N2, N3, and N4. When you create a protection group on D1 or D2, you can add any virtual machine.

Backup and restore VMM server | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-vmm-server?view=sc-dpm-1807

Schemes for backing up VMM supported by DPM

In the following deployment scenarios, when VMM is running as a physical / virtual computer on System Center 2012 and later, DPM can use the VMM quick writer to back up the VMM database:

Stand-alone VMM host + stand-alone SQL Server (default and specified, local and remote)

Stand-alone VMM host + cluster SQL Server (default and specified, remote)

Cluster VMM host + stand-alone SQL Server (default and specified, local and remote)

Cluster VMM host + cluster SQL Server (default and specified, remote)

DPM backup VMM need to pay attention to

DPM backs up only the DPM SQL Server database. It does not back up all configuration files in the VMM library.

For VMM computers, DPM supports initial replication and fast full backups. Incremental backups are not supported.

When setting up VMM, if you specify a static IP address for SQL Server, DPM cannot back up the VMM database. If you specify "localhost" for the database, DPM cannot back up.

If you use distributed key Management (DKM) encryption (the key is stored in AD), DPM does not back up the key. It needs to be protected as part of the AD backup. If the key is stored locally, it is backed up as part of the database.

In the event of a failover, DPM continues to back up when the VMM node comes back online. In this way, you will be able to perform a planned failover without losing protection. However, if a node is lost, a backup must be configured for the new node.

For VMM hosts, DPM supports a restore to the original location. Restoring to an alternate location is not supported.

Prepare to back up general data sources | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-generic-data-source?view=sc-dpm-1807

Prepare computers in workgroups and untrusted domains for backup | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-machines-in-workgroups-and-untrusted-domains?view=sc-dpm-1807

Backup DPM server | Microsoft Docs https://docs.microsoft.com/zh-cn/system-center/dpm/back-up-the-dpm-server?view=sc-dpm-1807

There are several ways to back up a DPM server

Backup DPM server-you can back up the primary DPM server using a secondary DPM server. The secondary server protects the primary server database and the copy of the data source stored on the primary server. If the primary server fails, the secondary server can continue to protect the workload protected by the primary server until the primary server becomes available again. If you need to rebuild the primary server, you can restore the database and replica from the secondary server to the primary server. When the primary server is not available, you can also restore data directly from the secondary server to the protected computer. You can set up two servers, one as the primary server and the other as the secondary server, or you can configure each server to act as the primary server for the other. You can also configure the DPM server chain, where DPM servers protect each other in chain order.

Backup DPM server-the DPM server can be configured to back up its own database to its tape library, or non-Microsoft software can be used to back up the database to tape or removable media.

Back up DPM with third-party software-you can back up the DPM server using third-party software that supports DPM and VSS.

The solution of linking four DPM servers

Welcome to follow the Wechat official account below for more content.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.