Windows Server File Volume Restore Solution Backup Restore Solution from Veeam

Windows Server File Volume Restore Solution Backup Restore Solution from Veeam. Veeam has an endpoint backup and restores solution for Microsoft. Veeam Agent for Microsoft Windows can take backups of servers, desktops, and laptops.

In this post, we will see Video Guide Windows Server 2016 Backup Solution from Veeam. In this post, we will see Windows Server 2016 File Volume Restore Solution from Veeam.

Following are the three posts that will cover the Windows endpoint backup solution from Veeam.

  1. Windows 10 backup and recovery Software from Veeam
  2. Video Guide Windows Server 2016 Backup Solution from Veeam
  3. Video Guide Windows Server 2016 File & Volume Recovery Solution from Veeam

Veeam Agent for Windows restores options are explained in the video tutorial.

Windows Server File Volume Restore Solution Backup Restore Solution from Veeam

Once Veeam FULL Backup of Server 2016 is completed? Then, open up VEEAM BACKUP BROWSER to restore. There are two restore options available from the backup browser, and the last one is the recovery option from Veeam recovery media.

  • File Restore
  • Volume Restore
  • Restore from Recovery Media

Veeam Agent – Restoring Files and Folders of Server 2016

Veeam Backup Browser or File Level Restore wizard should be used to recover or restore If some files and folders on your computer get lost or corrupted. For file-level restore, you can use backups of any type.

  • Volume-level backups (backups of the entire computer or specific volumes)
  • File-level backups
Windows Server 2016 File Volume Restore Solution from Veeam
Backup Browser – Windows Server

To launch the File Level Restore wizard, do either of the following: Start Menu, select All Programs > Veeam > File Level Restore. We can perform the following operations with restored files and folders from Veeam Backup Explorer.

  • Save files and folders to their initial location
  • Save files and folders to a new location
  • Open files in Microsoft Windows Explorer

Veeam BACKUP Browser is similar to file explorer. It gives two options to restore in my scenario for this video. I selected the KEEP option. This will create a copy of the restore and won’t overwrite. Restore is completed. The windows 10 ISO file got restored within 1:23 minutes, as you can see in the video tutorial here.

  • OVERWRITE
  • KEEP
Windows Server 2016 File Volume Restore Solution from Veeam
Restore – Windows Server

Veeam Agent – Volume Restore of Windows Server 2016

When we perform a volume-level restore, Veeam Agent for Microsoft Windows restores the entire content of the volume. We can’t use the File restore wizard to recover the specific volumes.

It retrieves from the backup data blocks about a particular volume and copies them to the necessary location.

The volume-level restore should be done via the Volume Level restore wizard.” We need to go through and define the following the wizard

  • Backup Location
  • Restore Point
  • Disk Mapping
  • Summary
  • Progress of the Volume Restore
Windows Server
Volume Level Restore – Windows Server

We can boot from the recovery image and use the Veeam Volume Level Restore, wizard for volume-level restore of Server 2016. Following are the three limitations of volume-level restore, which Veeam documents.

  • Cannot restore the system volume to its original location.
  • Cannot restore a volume to the volume on which the swap file is currently hosted.
  • Cannot restore a volume to the volume where the backup file used for restore is located.

Resources

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a logger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

Video Guide Windows Server 2016 Backup Solution from Veeam

Video Guide Windows Server 2016 Backup Solution from Veeam, Windows Server 2016 Backup Solution from Veeam. Veeam has a backup and restores solution for Microsoft Windows devices.

Veeam Agent for Microsoft Windows can take backups of servers, desktops, and laptops. Previously, this solution was known as “Veeam Endpoint Backup”.

In this post, we will see Video Guide Windows Server 2016 Backup Solution from Veeam.

Following are the three posts that will cover the Windows endpoint backup solution from Veeam.

  1. Windows 10 backup and recovery Software from Veeam
  2. Video Guide Windows Server 2016 Backup Solution from Veeam
  3. Video Guide Windows Server 2016 File & Volume Recovery Solution from Veeam
Video Guide Windows Server 2016 Backup Solution from Veeam 1
  • Installation of Veeam Agent on Microsoft Windows server 2016
  • Create Recovery Media
  • Taking Backup of Server 2016 as per schedule
Windows Server 2016 Backup Solution from Veeam
Veeam Agent – Windows Server 2016 Backup Solution from Veeam 2

Install Veeam Agent for Windows on Server 2016

Veeam Agent for Microsoft Windows is a data protection and disaster recovery solution for physical and virtual machines. Veeam Agent for Microsoft Windows can be used to protect different types of computers and devices: desktops, laptops, and tablets.

The solution can be installed on any computer that runs the following OSes

  • Microsoft Windows 7 SP1 or later
  • Microsoft Windows 2008 R2 SP1 or later
Windows Server 2016 Backup Solution from Veeam
Installation Status – Windows Server 2016 Backup Solution from Veeam 3

The installation of the Veeam Agent for Windows is straightforward. It will automatically take care of installing prerequisites like SQL express etc. After the installation, you will be able to see

  • Veeam Agent for Microsoft Windows Service
  • Veeam Agent Tray
  • SQL Server 2012 Express LocalDB

How to Create Recovery Media for Server 2016

Once the Veeam Agent for Windows is installed, the first step is to create a Veeam Recovery media. Veeam Agent for Microsoft Windows lets us create a Veeam Recovery Media. The recovery media is nothing but a recovery image of your computer.

You can boot your computer/server with recovery media and fix the OS system errors on your server 2016 or restore data from the backup. 

Microsoft Windows RE (Recovery Environment) automatically reboots after 72 hours of continuous use. All data that has not been saved before reboot will be lost.

Windows Server 2016 Backup Solution from Veeam
Windows Server 2016 Backup Solution from Veeam 4

You can launch the recovery media creation wizard from the Veeam Agent for the Windows home page. As you can see in the video tutorial here, media creation is a straightforward process.

It took nearly 9 minutes to create a recovery media on my server 2016. The wizard will prompt to format the USB during the media creation process. At the high-level following are the tasks.

  • Mounting Recovery Environment Image
  • Copy Veeam Recovery Environment files
  • Adding .NET framework
  • Adding system drivers
  • Copying boot files
  • Unmounting Recovery Image
  • Preparing USB disk
  • Copying data to USB disk
  • Recovery media has been created

Take Full Backup of Server 2016 using Veeam Agent for Windows.

Veeam Agent for Windows 3 types of backup modes are available. And those backup modes are “Entire computer,” “Volume-level backup,” and “File-Level backup.” Veeam Agent for Windows servers supports five backup options. And those options are listed down.

  • Removable storage device
  • Local computer drive
  • Network shared folder
  • A Veeam backup server manages the backup repository
  • Cloud repository managed by a Veeam Cloud Connect service provider
Windows Server 2016 Backup Solution from Veeam
Backup Mode – Windows Server 2016 Backup Solution from Veeam 5

“Configure backup” is the Veeam agent’s option to start configuring and scheduling the backup for the Windows server. Back up your entire server is the recommended option in the Veeam Agent for Windows. This helps with fast recovery on any level.

I selected the Entire Computer backup option for my server 2016. I used the external hard disk (local storage) to take the backup of server 2016. This is my Hyper-V server in my lab.

More details are available in the video tutorial here. Following are the tasks which I could see.

  • Initializing
  • Preparing for backup
  • Creating VSS snapshot
  • Calculating digests
  • Getting list of local users
  • System Reserved (disk 0) (500.0 MB) 42.0 MB read at 42 MB/s
  • (C:)(49.0 GB)42.4 GB read at 74 MB/s
  • Local Disk (E:) (188.5 GB) 37.4 GB read at 84 MB/s
  • Saving GuestMembers.xml
  • Finalizing
  • Truncating transaction logs
  • Truncating SQL server transaction logs
  • Processing finished
Windows Server 2016 Backup Solution from Veeam
Status – Windows Server 2016 Backup Solution from Veeam 6

Resources

Veeam Agent for Microsoft Windows – User Guide

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a logger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…

Server 2016 Domain Join Error Code 0x0000267C Windows Server | Troubleshooting Issues on Domain Join

Server 2016 Domain Join Error Code 0x0000267C Windows Server | Troubleshooting Issues on Domain Join? Editing a host file can be dangerous, and it can be miss leading. This is the first lesson of this post.

We will see how to perform the domain join operation for Server 2016 and How to avoid Server 2016 Domain Join Error Code 0x0000267C. I was not able to join the server to the domain.

I tried with NetBIOS name of the domain and full FQDN without success. I was confident that the DNS server was configured correctly on the newly built server. The entire troubleshooting and Domain join processes are explained in the video here.

The DC server was not reachable from the newly built server because of firewall configurations on the local server. I disabled the firewall on the server, which resolved the reachability issue.

The basic checks we need to perform before joining a server 2016 to domain are

  1. Ping DC server with IP
  2. Ping DC server with a short name
  3. Ping DC server with FQDN
  4. Remove the host file entries if there is an entry with the domain name or DC server name.
  5. Check the required Firewall ports are opened between the member server and DC server.
  6. Check the antivirus software (Symantec/MacAfee) is NOT blocking the communication.
Server 2016 Domain Join Error

I received the following is the domain join error on the server 2016 machine. An Active Directory Domain Controller (AD DC) for the domain “Intune.com” could not be contacted. Ensure that the domain name is typed correctly. If the name is correct, click details for troubleshooting information. I made sure that the domain name was correctly entered.

C:\Windows\Debug\dcdiag.txt is the log file that can provide more details when you have any issues with domain join. I checked the DCDIAG.log file, and it gave more information about the domain join issue.

Domain Join Error Details

An error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "intune.com".
The error was: "No DNS servers configured for local system." 
(error code 0x0000267C DNS_ERROR_NO_DNS_SERVERS)
The query was for the SRV record for _ldap._tcp.dc._msdcs.intune.com

Server 2016 Domain Join Error NO DNS SERVER

Resolution

The domain name was correctly mentioned during the server 2016 domain join process. Also, the server can ping the domain and DC. But when I checked the host file of the local 2016 server, then there were some entries of domain name mapping. I deleted those entries from the host file.

Also, I checked the IPCONFIG information on the server and noticed that the DNS server IP was not configured. Rather DNS server IP was configured as gateway device IP. I removed the gateway IP and correctly configure the DNS server IP in the IPCONFIG utility. More details are available in the video below.

Author

Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management with more than 20 years of experience (calculation done in 2021) in IT. He is a logger, Speaker, and Local User Group HTMD Community leader. His main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…