Highlighted

Initial observations from Backup Exec 16 and Windows Server 2016

We've been completing some initial testing with Backup Exec 16 and Windows Server 2016 and thought we'd share the results.

1. The upgrade of the Backup Exec to 16 and then the backup server to Windows Server 2016 went smoothly.

2. System State backups appear to run very slowly when the Windows Defender service (Antimalware Service Executable) is running real time scanning.

3. We haven't yet been able to successfully complete a backup of AD DS running on Windows Server 2016 when GRT and consistency checking is enabled.

The following errors and warnings are listed:

The consistency check of the snapshot for the Microsoft Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) transaction log ntds has failed. You should check for possible data corruption in the transaction log that is online.

VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.206\x86_installed is not present on the snapshot.

VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.0\amd64_installed is not present on the snapshot.

VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.206\amd64_installed is not present on the snapshot.

VSS Snapshot warning. File c:\windows\servicing\version\10.0.14393.0\x86_installed is not present on the snapshot.

4. Our tests of Active Directory show no problems with the consistency of the database and then are no errors or warnings logged on the AD server during the backup.

2 Replies

Re: Initial observations from Backup Exec 16 and Windows Server 2016

for the AV issue, make sure that it isn't actively scanning the BE services, or blocking access to the registry...had that with McAfee before. Thanks!

Re: Initial observations from Backup Exec 16 and Windows Server 2016

Found the fix for the missing file VSS error:

https://support.microsoft.com/en-us/help/4052556/error-the-system-writer-is-not-found-in-the-backup-...

You will need to take ownership of the C:\windows\servicing\version folder and grant full control to that user, then you will be able to copy the x86_installed and amd64_installed files from the newest version and put them in the older version folders.  I suggest resetting ownership to "System" when complete. 

Tags (2)