Video Guide Windows Server 2016 Backup Solution from Veeam 1

Video Guide Windows Server 2016 Backup Solution from Veeam

Let’s discuss the Video Guide Windows Server 2016 Backup Solution from Veeam. Veeam offers a backup and restore solution for Microsoft Windows devices.

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

This post will show a Video Guide on Veeam’s Windows Server 2016 Backup Solution. The next three posts will cover Veeam’s Windows endpoint backup solution.

Under the post-Veeam Backup for the O365 v4 Community Version Upgrade Guide, you will find all the details of Veeam Backup for the O365 v4 Community Version. Veeam released the latest version of Veeam Backup for Microsoft Office 365 with many enhancements.

  1. Windows 10 backup and recovery Software from Veeam
  2. Video Guide Windows Server 2016 Backup Solution from Veeam

Video Guide Windows Server 2016 File & Volume Recovery Solution from Veeam

Veeam has a free backup and restore 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“.

Video Guide Windows Server 2016 Backup Solution from Veeam – Video 1

Video Guide Windows Server 2016 Backup Solution from Veeam

Veeam Vanguard is a community program by Veeam, and I’m honoured and privileged to be part of this exciting tech community.

Video Guide Windows Server 2016 Backup Solution from Veeam
Installation of Veeam Agent on Microsoft Windows Server 2016
Create Recovery Media
Taking Backup of Server 2016 as per schedule
Video Guide Windows Server 2016 Backup Solution from Veeam – Table 1
Video Guide Windows Server 2016 Backup Solution from Veeam - Fig.1
Video Guide Windows Server 2016 Backup Solution from Veeam – Fig.1

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. It can protect different types of computers and devices, including desktops, laptops, and tablets. The solution can be installed on any computer that runs the following OS.

  • Microsoft Windows 7 SP1 or later
  • Microsoft Windows 2008 R2 SP1 or later
Video Guide Windows Server 2016 Backup Solution from Veeam - Fig.2
Video Guide Windows Server 2016 Backup Solution from Veeam – Fig.2

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, which is nothing but a recovery image of your computer.

You can boot your computer or server with recovery media, 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.

Video Guide Windows Server 2016 Backup Solution from Veeam - Fig.3
Video Guide Windows Server 2016 Backup Solution from Veeam – Fig.3

You can launch the recovery media creation wizard from the Veeam Agent for the Windows home page. As the video tutorial shows, media creation is straightforward.

It took nearly 9 minutes to create a recovery media on my server 2016. The wizard will prompt you to format the USB during the media creation. At the high level, the 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 offers three backup modes: “Entire computer,” “Volume-level backup,” and “File-Level backup.” Veeam Agent for Windows servers supports five backup options listed below.

  • 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
Video Guide Windows Server 2016 Backup Solution from Veeam - Fig.4
Video Guide Windows Server 2016 Backup Solution from Veeam – Fig.4

“Configure backup” is the Veeam agent’s option to start configuring and scheduling the backup for the Windows server. The recommended option in the Veeam Agent for Windows is backing up your entire server. 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 back up the server in 2016. This is my Hyper-V server in my lab. The video tutorial here provides more details. The following are the tasks that I could see.

  • Initializing
  • Preparing for backup
  • Creating VSS snapshot
  • Calculating digests
  • Getting a 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
Video Guide Windows Server 2016 Backup Solution from Veeam - Fig.5
Video Guide Windows Server 2016 Backup Solution from Veeam – Fig.5

Resources

Veeam Agent for Microsoft Windows – User Guide

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, 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 2

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

Let’s discuss the 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 misleading. 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 using the domain’s NetBIOS name to complete FQDN without success. However, I was confident that the DNS server was configured correctly on the newly built server. The troubleshooting and domain join processes are explained in the video here.

The DC server was unreachable from the newly built server because of firewall configurations on the local server. Disabling the firewall on the server 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 that the required Firewall ports are opened between the member and DC servers.
  6. Check the antivirus software (Symantec/MacAfee) is NOT blocking the communication.

How to Domain Join Server 2016 Error Code 0x0000267C

This video provides a comprehensive guide on resolving the Domain Join error code 0x0000267C on Windows Server 2016. This error typically indicates issues with DNS configuration or network connectivity, which are crucial for successfully joining a server to a domain.

Server 2016 Domain Join Error Code 0x0000267C Windows Server Troubleshooting Issues on Domain Join – Video 1

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

I received the following 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.

Server 2016 Domain Join Error Code 0x0000267C Windows Server Troubleshooting Issues on Domain Join - Fig.1
Server 2016 Domain Join Error Code 0x0000267C Windows Server Troubleshooting Issues on Domain Join – Fig.1

Domain Join Error Details

Let’s discuss the details of the Domain Join Error. The screenshot below will provide more information to help you understand the issue better. This error typically occurs when there are problems with DNS configuration or network connectivity, which are essential for successfully joining a Windows Server 2016 to a domain.

  • The screenshot will highlight the specific error messages and details that can guide us in troubleshooting and effectively resolving the problem.
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. However, when I checked the host file of the local 2016 server, I found some domain name mapping entries. 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, it was configured as a gateway device IP. I removed the gateway IP and correctly configured the DNS server IP in the IPCONFIG utility.

We are on WhatsApp now. To get the latest step-by-step guides, news, and updates, Join our Channel. Click here. HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, 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.