Backup SystemState from cml fails Windows Server 2016?

[ukidenme]

VMWare Guest running Windows Server 2016 fully patched as of 2019Sept24
Backing up from the cml fails with the msg "The filename, directory name, or volume label syntax incorrect."
I have two local drive C and D. I'm trying to backup to Drive D.
Syntax: wbadmin start systemstatebackup -backuptarget:
Using this link for the syntax - wbadmin start systemstatebackup

I've found a solution. You have to modify these registry settings.
hkey_local_machine\system\controlset001\services\vsock
hkey_local_machine\system\controlset002\services\vsock
hkey_local_machine\system\controlset\services\vsock

Original setting is \SystemRoot\system32\DRIVERS\vsock.sys
Change them to %SystemRoot%\system32\DRIVERS\vsock.sys
Restart the server.

I've added %SYSTEMROOT%\System32\Drivers to the path and restarted. The systemstatebackup still fails with the same msg.
I have to change the registry keys for the systemstatebackup to succeed.

My questions are why do I have to change the registry keys for the backup to succeed?
Is my syntax incorrect?
What am I missing or doing wrong?


Note:
I can backup the systemstatedata to Drive D using the GUI.
I can backup the C Drive to the D Drive from the command line. wbadmin start backup -backuptarget: -include:C:
I have the user account in the local admin group.
I'm running CMD elevated with admin privileges.











I

 

[ChatGPT]

It seems like you are facing issues with backing up your system state using the command line in Windows Server 2016. The error you are encountering could be due to the way the system path is being referenced in the registry keys or in your backup command. Here are some points to consider and steps to troubleshoot the issue: 1. Backup Syntax: - Your syntax for backing up the system state seems correct: wbadmin start systemstatebackup -backuptarget:D: - Verify that the drive D: is accessible and has enough space to store the backup. 2. Registry Path: - The modification you made to the vsock registry keys might not be directly related to the backup issue. - Ensure that all the registry paths have been correctly updated to %SystemRoot%\system32\DRIVERS\vsock.sys. - After making the changes, restart the server to ensure the modifications take effect. 3. User Permissions: - Since you can backup using the GUI and command line for the C Drive, it indicates that the user account has the necessary permissions for backup operations. - However, double-check that the same user account has the required permissions for system state backups. 4. Troubleshooting: - To further troubleshoot the issue, try running the system state backup command with elevated privileges. - Check the Event Viewer for any specific error messages related to the failed backup operation. This could provide more insights into the root cause of the issue. - Consider using PowerShell commands for system state backups to see if it provides a similar error. If these steps do not resolve the issue, try to isolate the problem further by capturing any specific error messages or logs related to the backup failure. This information can help in identifying the exact cause and solving the problem effectively.