Windows Server 2019 Module 7 Whole Set

What is Windows Server Backup

A feature that consists of Microsoft Management Console(MMC) snap in, wbadmin command, and windows PowerShell commands

How can you use Windows Server Backup

Wizards and PowerShell cmdlets

What are the tasks Windows Server Backup can do

A full server

Individual files and folders

System State

Individual VM host on Hyper-V

Microsoft Exchange database

Cluster Shared volumes

What are some more advanced task Windows Server Backup can do

Performing a bare-metal restore - A bare-metal backup contains at least all critical volumes, and it allows you to restore without first installing an operating system. This is done by using the product media on a DVD or USB key and the Windows Recovery Environment (Windows RE). This backup type can be used together with the Windows RE to recover from a hard disk failure or to recover a whole computer image to new hardware.

Restoring system state - The backup contains all information to roll back a server to a specific time. However, you must install an operating system before system state can be recovered.

Recovering individual files and folders or volumes - The Individual files and folders option enables you to selectively back up and restore specific files, folders, or volumes. Specific files, folders, or volumes can be added to a backup even when using an option such as critical volume or system state.

Excluding selected files or file types - Unwanted files or file types, such as temporary files, can be excluded from a backup.

Storing backups in multiple storage locations - You can store backups on remote shares or non-dedicated volumes.

Performing backups to Azure - Azure Online Backup is a cloud-based backup solution for Windows Server that enables you to back up and recover files and folders offsite by using cloud services. You can use Windows Server Backup with an appropriate agent to store backups in Azure.

To backup multipule servers using Windows Server Backup you must

install and con

WBAdmin is

A command-line tool that’s built into Windows Server. The command is sured to perform backups and restores of operating systems, drive volumes, files, folders, and applications from a command-line interface

Is Windows Server Backup installed by default

No

How can Windows Server Backup be installed

Windows Admin Center

Server Manager

PowerShell cmdlet Add-WindowsFeature Windows-Server-Backup -includeAllSubfeature

What does Windows Server Backup use to perform backups

Volume Shadow Copy Service (VSS)

A consistent shadow copy is known as a

snapshot or point-in-time copy

VSS solutions have which parts

VSS Service

VSS Requester

VSS Writer

Microsoft SQL or Exchange Server

VSS Provider

VSS Service Does what

The part of the Windows OS that ensure that the other components can communicate with each other properly and able to work together

VSS Requester does what

This software requests the actual creation of Shadow Copies or other high-level operations like importing or deleting them. This is typically a backup application.

VSS Writer does what

This component guarantees that you have a consistent dataset to back up. This is typically a line-of-business application such as Microsoft SQL Server or Exchange server . The Windows Server OS includes VSS writers for carious components such as registry.

Types of backups for Active Directory

Full Server Backup

System State Backup

Critical Volumes Backup

What is a Full Server Backup

Contains all the volumes on a domain controller.

What is a System State backup

A non incremental backup that requires the same amount of space each backup

What is a critical volumes backup

an incremental backup that includes only the difference between the current backup and the previous backup.

If a backup is older than 180 days you can’t

restore from it

Exchange Native Data Protection is a concept that

relies on native Exchange features to protect mailbox data without using traditional backups

If you want to make backups of Exchange servers you can use the

Windows Server Backup plug-in that exchange has.

How does the Windows Server Backup Plug-in work

enables you to create a Exchange aware VSS backup of the exchange data.

What is the plug-in for the exchange server

WSBExchange.exe

To schedule or modify a backup you can use the

Backup Schedule Wizard

What does the Exclusions option do in Backup Schedule Wizard

You can exclude files types within specific folder and their subfolders.

What does the VSS Option option do in Backup Schedule Wizard

You can select VSS full backup or VSS Copy Backup.

What is a VSS Full backup

An update that updates the backup history and the clears the log file

What is a VSS Copy Backup

A backup that includes the VSS writer log files

What factors should be included when planning a backup strategy

Type of backups that can be made

the state of VMs

type of storage the VMs use

Data being backed up

Exchange and SQL server have different

best practices for backing them up

In Hyper-V environments you can use both

Windows Server Backup and Microsoft System Center Data Protection Manager to back them up

Methods of backing VMs up

Backup the VM from the host

Backup the VM’s VHDs

Backup inside the VM

Backup the VM from the host Backup Method

full server backup where the data in the backup includes VMs' configurations, VMs' associated checkpoints, and VMs' virtual hard disks (VHDs). When restoring data from a backup, it's not necessary to recreate VMs or reinstall Windows Server roles. However, the backup doesn't include virtual network settings, which must be recreated and reattached to the VMs. For this purpose, Windows PowerShell scripts that automate the process of creating and attaching the virtual switches might be created.

Most businesses today use this to backup VMs from the host

Backup the VM from the host method

Backup the VM’s VHDs backup method

access the storage and backup the VHDs. May be ineffective since to use the VHDs you would need to create new VMs and configure them first

Back up inside the VM backup method

This method backs up the storage within the VM from the VM. The downside is that the VM configuration isn’t backed up.

To perform backups that don’t incur VM downtime you must meeT these conditions

VM being backup has integration services installed and enabled

Each disk that the VM uses us running NTFS file system basic disks

VSS is enables on all volumes within the VM and snapshots for each volume are stored on the same volume

Live migration allows you to do what

Move VMs while running without causing any downtime

Where can you setup live migration

In Hyper-V manager

By default the authentication protocol is

Credential Security Support Provider(CredSSP)

What is the other authentication protocol you can use

Kerberos

How can you start the live migration process

The Failover Management Console

Virtual Machine Manager Administrator console, if you use Virtual Machine Manager to manage your physical host

A windows Managements Instrumentation or Windows PowerShell Script

Migration Setup Step

When an administrator starts a VM failover, the source node creates a TCP connection with the target physical host. This connection is used to transfer VM configuration data to the target physical host. Live Migration creates a temporary VM on the target physical host and allocates memory to the destination VM. The migration preparation also checks to determine whether a VM can be migrated.

Guest Memory Transfer step

This transfers iteratively to the target host while the VM is still running on the source host. Hyper-V on the source physical host monitors the pages in the working set. As the system modifies memory pages, it tracks and marks them as being modified. During this phase of the migration, the migrating VM continues to run. Hyper-V iterates the memory copy process several times, and a smaller number of modified pages copy to the destination physical computer every time. A final memory copy process copies the remaining modified memory pages to the destination physical host. Copying stops as soon as the number of dirty pages drops below a threshold or after 10 iterations are complete.

State Transfer step

To migrate the VM to the target host, Hyper-V stops the source partition, transfers the state of the VM, including the remaining dirty memory pages, to the target host, and then begins running the VM on the target host.

Cleanup step

finishes the migration by tearing down the VM on the source host, terminating the worker threads and signaling the completion of the migration

What Server Message Block(SMB) can you use in windows to perform live migrations

SMB 3.0

What are the requirements for live migration

Support hardware virtualization

Use processers from the same manufacturer

Belong either to the same AD domain or to domains that trust each other

VMs must use VHDs or virtual fiber channel

Use an isolated network either physically or through vlans

For live migration of a cluster you also need

Windows Failover Cluster enabled and configured

A Cluster Shared Volume (CSV) storage in the cluster is enabled

For live migration using shared storage you also need

All file that make up a VM to be stored in a SMB Share

Permissions on the SMB share configured to grant access to the computer account of all server that are running Hyper-V

For non-clustered hosts to live migrate you also need

A user account with permissions to perform the various steps. Membership in the local Hyper-V Administrators group or the Administrators group on both the source and destination computers meets this requirement unless you're configuring constrained delegation. Membership in the Domain Administrators group is required to configure constrained delegation.

Source and destination computers that belong either to the same Active Directory domain or to domains that trust each other.

The Hyper-V management tools that are installed on a Windows Server or Windows 10 computer, unless the tools are installed on the source or destination server, and you'll run the tools from the server.

Where can you perform a live migration

Live Migration Wizard in Hyper-V or PowerShell cmdlets

What is the most common reason for moving a VM using live migration

to upgrade the physical storage on the hardware so the VM can have more

During a live migration the VM write files to the

source and destination drive

What are the three options the Move Wizard presents when moving a VHD to another location

Move all the VM’s data to a single location

Move the VM’s data to a different location

Move only the VM’s VHD

***Note: The Move Wizard and these options are only available if the Hyper-V VM isn't part of a failover cluster. All three of the options are achievable in Failover Cluster Manager by using the Move Virtual Machine Storage options.***

Hyper-V failover clusters are used to make virtual machines (VMs)

highly available

Hyper-V Replica can protect against

data loss from natural disasters, and it can be used to implement an affordable business continuity and disaster recovery (BCDR) solution for a virtual environment

Hyper-V Replica can have two instances of a single VM residing on different Hyper-V hosts. How do these run

one is the primary and the other is the replica.

Replication engine

This component manages the initial replication, replication configuration details, replication of delta changes, and failover and test failover operations. It also tracks VM and storage mobility events and takes appropriate actions when necessary. For example, it pauses replication and Hyper-V Replica configurations when the source or the replica Hyper-V hosts are part of a Hyper-V failover cluster.

Change tracking chapter

This component tracks changes that occur to the VM on a source Hyper-V host. The change tracking chapter tracks write operations to the virtual hard disks (VHDs) regardless of where the VHDs are stored locally—on a storage area network, on a Server Message Block version 3 or newer share, or on a Cluster Shared Volume.

Network chapter

This component provides a secure and efficient way to transfer VM data between Hyper-V hosts. By default, the network chapter minimizes traffic by compressing data. It can also encrypt data when HTTPS and certification-based authentication are used.

Hyper-V Replica Broker

This component is used only when a Hyper-V host is a node in a failover cluster. This enables the use of Hyper-V Replica with highly available VMs that can move between cluster nodes. This role queries the cluster database. It then redirects all requests to the cluster node where the VM is currently running.

Management tools

With tools such as Hyper-V Manager and Windows PowerShell, Hyper-V Replica can be configured and managed. Use Failover Cluster Manager for all VM management and Hyper-V Replica configurations when the source or the replica Hyper-V hosts are part of a Hyper-V failover cluster.

Hyper-V replica can be set up

no matter the domain membership(doesn’t have to be part of the same domain)

The types of Hyper-V configurations

Both Hyper-V hosts are standalone servers. This configuration isn't recommended, because it includes only disaster recovery and not high availability.

The Hyper-V host at the primary location is a node in a failover cluster, and the Hyper-V host at the secondary location is on a standalone server. Many environments use this type of implementation. A failover cluster provides high availability for running virtual machines (VMs) at the primary location. If a disaster occurs at the primary location, a replica of the VMs is still available at the secondary location.

Each Hyper-V host is a node in a different failover cluster. This enables you to perform a manual failover and continue operations from a secondary location if a disaster occurs at the primary location.

The Hyper-V host at the primary location is a standalone server, and the Hyper-V host at the secondary location is a node in a failover cluster. Although technically possible, this configuration is rare. You typically want VMs at the primary location to be highly available, while their replicas at the secondary location are turned off and aren't used until a disaster occurs at the primary location.

Because each VM is configured for individual replication you must

plan resorces for each VM and how to configure their settings

Replica Server setting

Specifies the Computer name for fully qualified domain name (FQDN) of the replica server. If the replica server is a node in a failover cluster you should enter the name or FQDN of the connection point for the Hyper-V Replica Broker

Connection Parameters setting

If the Replica server is accessible, the Enable Replication Wizard populates the authentication type and replication port fields automatically with appropriate values. If the Replica server is inaccessible, these fields can be configured manually. However, you should be aware that you won't be able to enable replication if you can't create a connection to the Replica server. On the Connection Parameters page, Hyper-V can also be configured to compress replication data before transmitting it over a network.

Replication of VHDs setting

Replication Frequency

You can set replication frequency to 30 seconds, 5 minutes, or 15 minutes based on the network link to the Replica server and the acceptable state delay between primary and replica VMs. Replication frequency controls how often data replicates to the Hyper-V host at the recovery site. If a disaster occurs at the primary site, a shorter replication frequency means less loss as fewer changes aren't replicated to the recovery site.

Additional recovery points settings

You can configure the number and types of recovery points to send to a Replica server. By default, the option to maintain only the latest point for recovery is selected, which means that only the parent VHD replicates. All changes merge into that VHD. However, you can choose to create more hourly recovery points and then set the number of additional recovery points (up to 24). The Volume Shadow Copy Service snapshot frequency can be configured to save application-consistent replicas for the VM and not just the changes in the primary VM.

Initial replication method and schedule

Ms have large virtual disks, and initial replication can take a long time and cause a lot of network traffic. While the default option is to immediately send the initial copy over the network, if you don't want immediate replication, you can schedule it to start at a specific time. If you want an initial replication but want to avoid network traffic, you can opt to send the initial copy to external media or use an existing VM on the Replica server. Use the last option if a copy of the VM is restored at the Replica server and you want to use it as the initial copy.

Extended replication setting

you can replicate a single VM to a third server. Thus, a running VM can be replicated to two independent servers. However, the replication doesn't happen from one server to the two other servers. The server that's running an active copy of the VM replicates to the Replica server, and the Replica server then replicates to the extended Replica server.

Hyper-V Replica comes implemented when you install

Hyper-V

To enable Hyper-V replica do the following steps

Replication Configuration

Configure Hyper-V server settings

Specify Replica Server name and the connection options

Select the VHDs to replicate

Replication Health Data contains the following info

Replication State. This indicates whether replication is enabled for a VM.

Replication Type. This indicates whether you're monitoring replication health on a primary VM or replica VM.

Primary and Replica server names. This indicates which Hyper-V host the primary VM is running on and which Hyper-V host is the replica.

Replication Health. This indicates replication status. Replication health can have one of three values: Normal, Warning, or Critical.

Replication statistics. This displays replication statistics since the time that the VM replication started or since resetting the statistics. Statistics include data such as maximum and average sizes of a replication, average replication latency, number of errors encountered, and the number of successful replication cycles.

Pending replication. This displays information about the size of data that still needs to replicate and when the replica was last synced with the primary VM.

Test Failover

a nondestructive tasl the enables you to test a VM on a Replica Server while the primary VM stays online. The file with be appended with TEST to the end but will be offline.

Planned failover

used to move the primary to the replica secondary. Can be used for maintenance or if a disaster is expected to happen.

Failover

an unexpected failure of the primary VM, data and processes will move over to the replica

Other replication settings

Pause Replication. This action pauses replication for the selected VM.

Resume Replication. This action resumes replication for the selected VM. It's available only if replication for the VM is paused.

View Replication Health. This action provides data about the replication events for a VM.

Extend Replication. This action is available on the replica VMs, and it extends VM replication from a Replica server to a third server (the extended Replica server).

Remove Recovery Points. This action is available only during a failover. If you select it, all recovery points (checkpoints) for a replica VM are deleted, and their differing VHDs are merged.

Remove Replication. This action stops replication for the VM.

Site Recovery is a business contingency and disaster recovery (BCDR) solution to

replicates VMs to the cloud or a 2nd site