Wbadmin.msc on windows server 2016 fails after one disk changed

W

WhackyWakie

Background; setup one desktop lab with 2 x SSD, 1 x HDD and 1 x USB HDD. 1st SSD for system, 2nd SSD for VMs, HDDs are for backup. Windows 2016 eval with Hyper-V.

Using Windows backup service to backup both SSD into the HDDs. I try to change the 2nd SSD (and also simulate disk failure), by power off the desktop, swap it with a harddisk, then format the harddisk with the same drive letter.

When I start the windows backup service to restore the VMs folder, the follow error appear: "A fatal error occurred during Windows Server Backup snap-in (Wbadmin.msc) operation. Error details: The server threw an exception. Close Wbadmin.msc and then restart it."

Tried that and rebooted the server, no help. Checked, the back log is in "C:\windows\logs\windowsbackupbackup", the default location. Search for a solution and found that other would reset the backup, but that would remove the backup catalog.

Questions;

1. Is this a good way to swap disk? At first I think of using Clonezilla or hyper-V storage migration, but opt to test the Windows backup & restore.

2. Shouldn't these step "just work"? If there is really a failure of the 2nd disk, what step should I have taken to restore from the backup? Is there preparation needed to prevent this from happening? Like backup the backup's configuration else where too, configured the backup differently.

3. The 2nd HDD is only used for VMs, from the look of it the Windows backup also store backup information in it? VSS stuff? I need to read more into this..

Thanks!

Continue reading...
 
Back
Top Bottom