Hyper-V VMs get hosed after backup
"Hosed" being the technical term. It seems that after either/or of 2 VMs on the host machine, after a backup, cannot start. It also appears that Backup Exec creates snapshots that don't get re-absorbed into the parent virtual disk. So I'll end up with a series of .avhdx's, and if I try to start that VM, it'll tell me there's an ID mismatch in the chain of virtual disks. Pretty much every single time after a backup. The exact error is: 'VSERVER' failed to start. Synthetic SCSI controller (Instance ID XXXXX): Failed to Power on with Error 'The chain of virtual hard disks is corrupted. There is a mismatch in the identifiers of the parent virtual hard disk and differencing disk'. There is a fix, using the Set-VHD command, but I can't keep doing that over and over again. Additionally, I'll get this error from Backup Exec itself: V-79-40960-38691 - Backup Exec cannot create a recovery checkpoint for the 'VSERVER' virtual machine. (Note: "Use snapshot technology" is checked). Any ideas where I can start looking to fix this? Backup Exec version 21.4, 1200.2536, Windows Server 2019 Thanks!BE failed to register recently-restored VM
I tried to restore a Hyper-V VM early this morning; and though the files were apparently restored, Backup Exec threw this error: Final error: 0xe0009645 - Backup Exec failed to register the virtual machine. See the job log and the Windows Event Viewer for more details. The virtual machine will not be available in the Hyper-V or Virtual Server Administration Console. The Windows Event Log shows this: An account failed to log on. Subject: Security ID: SYSTEM Account Name: SERVER$ Account Domain: DOMAIN Logon ID: 0x3E7 Logon Type: 5 Account For Which Logon Failed: Security ID: NULL SID Account Name: FE02C21F-063E-4593-831F-C10A3C52D958 Account Domain: NT VIRTUAL MACHINE Failure Information: Failure Reason: The user has not been granted the requested logon type at this machine. Status: 0xC000015B Sub Status: 0x0 I should note I had to restore a virtual machine before this one with zero problems. This 2nd one didn't want to restore properly for some reason. Using BE "Silver Perpetual" Version 21.4 on Windows Server 2019 Thanks!
Restored vhdx (Hypver-V) unable to mount
Hi all, I'm working for a small charity that has three WIndows Server 2019 hyper-v servers running a couple of VM's. I have forever incremental backup jobs running that seem to be running fine. However, after a successful restore, I've discovered that some, but not all, of the restored vhdx files have no partitions or no drive letters assigned when mounted. When right clicking on a restored vhdx file, one of three things happens depending on the vmdx. It mounts fine and assigns drive letters - that's the normal behavior that I'd expect. That does happen with many of the restored files, but not all unfortunately or Frequently I will get this error message Couldn't Mount File The disk image isn't initialized, contains partitions that aren't recognizable, or contains volumes that haven't been assigned drive letters. Please use the Disk Management snap-in to make sure that the disk, partitions, and volumes are in a usable state. then one of 2 things happens. Either 2a. In disk manager, I am asked to initialize the drive. After doing so there are no partitions on the drive, making it unusable. or 2b Sometimes I can se the partition(s) on a virtual drive in disk manager, but there's just no drive letter assigned. I still get the above "Couldn't mount file" message, but I don't need to initialize the drive, it just shows up in disk manager with no drive letters. This is pretty infrequent, it's usually 2a when I have a problem VHDX. When I can see the partitions, I can assign a drive letter, but I'm not sure what would happen if that VHDX file were used as a restoration that was to be spun up in Hyper-v Has anyone seen this before? I've not on any of the other servers I manage elsewhere with a very similar configuration. I should add that for each vm, all restored vhdx files for that vm will either all be okay, all have no partitions, or all have partitions but with no drive letters. I did create a NEW forever incremental backup for each of the 3 servers. I ran a new backup on one to test, then did a restore. 3 vm's restored fine where I could open the vhdx file, 3 gave me problem 2a above, and one gave me problem 2b. Any suggestions as to why this is happening and/or what I might be able to to stop it? No point in backing things up if the restores are unusable!! Thank you all
Choosing backup source for VMs on Hyper-V: Cluster or Node?
Greetings, all! Our site has a new 2-node Hyper-V cluster that will replace our well-aged VMware ESXi 5.5 cluster. So, I'll be using Backup Exec (v.20.5) on Hyper-V for the first time as we build new servers on and move existing servers (?) to the new system. Having pushed the Agent for Windows successfully to the two nodes, I noticed that the cluster appeared in the list as well and can be backed up along with its VMs. The VMs can be backed up by choosing the nodes, too, which makes me ask which method is the better one. I don't recall seeing a mention of the two possibilities or a recommendation in the Administrator's Guide. What can those of you with experience in such a situation recommend as a backup strategy? Thank you for sharing your collective wisdom!need help to configures hyper-v server backups
A little background infomation: I am in the process of upgrading our BackUp Exec server and backups. We were on version 2012. We are upgrading to BackUp Exec 16. I built a new Windows Server, OS 2012r2 and installed the Backup Exec 16 software without an issues. I have a few physical servers that aren't VM host. I comfigure them. All are backing up without issue. As for the VM Host and virtial machines, I'm wanting to use the new features so I can use file/folder-level Granular Recovery Technology (GRT). I'm just not sure how ro back up the VM's so I can do this and use Simple Disadter Recovery too. In otherwords, I want to be able to recover the whole VM and/or a file from that VM. What is the correct way to do this? As so, when I configure the backup, when do I need to capture the Host Components? I have included a screenshot of what I'm trying to do. Just not sure if I need to have 2 backups, one for SDR and one for GRT. Any advice or instruction on this matter would be greatly appreciated. Regards, ABBEadmin
V-79-40960-38528 received when backing up Ubuntu 16.04 Server guest on Hyper-V 2016 host
Hello- I am running a Server 2016 Hyper-V host. On the host I have multiple Windows and Linux VMs running as guests. The Linux VMs are Ubuntu 16.04 Server-based. To simplify administration, I back up the Windows VMs in one backup job and the Linux VMs in a second, separate backup job. I am receiving the following in the job log for the Linux VMs: V-79-40960-38528 - The Hyper-V subsystem has reported that the Hyper-V Integration Services (HIS) inside the virtual machine do not match the version expected by the Hyper-V host. An offline backup of this virtual machine has been performed, update the Hyper-V Integration Services to ensure online backups can be performed whenever possible. I have de-selected all GRT-related options for the job under Backup Options-->Virtual Machines-->Virtual Machine Granular Restore Technology Settings. I have Instant GRT enabled under Backup Options-->Instant GRT (the default). Also, I have installed and upgraded both linux-tools and linux-cloud-tools packages in the VMs. I still receive the error. Any help would be appreciated.
V-79-57344-5894: Issue backing up Hyper-V VM
Hiello All Trying to backup a Win 2008R2 VM with installed agent and GRT enabled from a Win 2012 Hyper-V host running the BE 20.3 server. Error message: Directory D:\Virtual Machines\ was not found, or could not be accessed. None of the files or subdirectories contained within will be backed up. V-79-57344-5894- The object was not found, or could not be accessed (Hyper-V backup). V-79-57344-38721- Failed to mount one or more virtual disk images: Any solution to this? Many Thanks
Backup Exec VSS Writer
Good day, We are running Backup Exec on Windows Server 2008 R2 Standard. The backups keep failing when running a job for the Hyper-V Host server (Windows Server 2016 Standard) with 3x VM's and generates the errors below. The backup job will run once after the Host server has been restarted but after that it keeps failing. When running the VSSADMIN LIST WRITER command, no errors are generated on the Hyper-V host or the clients. Please may this get your full attention as these are critical servers that need to be backed up. Error log found on backup Exec (Backup Server) Job Log: BEX_HEBS_08814.xml<noscript> 30 October 2018 11:20:01 AM - V-79-40960-38521 - Snapshot Technology: Initialization failure on: "VRTSRV::\\****.he.local\Hyper-V?Virtual?Machine\****". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). A virtual machine snapshot could not be created. Use the Event Viewer on the Hyper-V host to identify the cause. If the virtual machine is not properly configured, it may be necessary to use the Event Viewer in the virtual machine to identify the cause. The following volumes are dependent on resource: "C:" . The snapshot technology used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Please see Acronis VSS Doctor report below (Errors were generated on Hyper-V Host server): 2018-10-30 11:23:23 GMT+02:00 AcronisVSSDoctor-net45, 1.0.39.0, v4.0.30319 Microsoft Windows NT 6.2.9200.0, 4.0.30319.42000 =========================================================== VSS Services Configuration and Status Status: OK Description: All VSS-related services are configured correctly Services: Name: swprv Title: Microsoft Software Shadow Copy Provider Status: Running ReferenceStatus: NeedToFixStatus: False StartMode: Manual ReferenceStartMode: Manual NeedToFixStartMode: False IsOk: True ExpectationDescription: Exception: Name: VSS Title: Volume Shadow Copy Status: Running ReferenceStatus: NeedToFixStatus: False StartMode: Manual ReferenceStartMode: Manual NeedToFixStartMode: False IsOk: True ExpectationDescription: Exception: Name: EventSystem Title: COM+ Event System Status: Running ReferenceStatus: Running NeedToFixStatus: False StartMode: Auto ReferenceStartMode: Auto NeedToFixStartMode: False IsOk: True ExpectationDescription: Exception: =========================================================== VSS Providers Configuration Status: OK Description: Only known VSS provider(s) found Providers: Id: 89300202-3cec-4981-9171-19f59559e0f2 Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{89300202-3cec-4981-9171-19f59559e0f2} Name: Microsoft File Share Shadow Copy provider IsDefault: True Id: b5946137-7b9f-4925-af80-51abd60b20d5 Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5} Name: Microsoft Software Shadow Copy provider 1.0 IsDefault: True =========================================================== VSS Access Control Configuration Status: OK Description: Known VSS access control entries are configured correctly AccessControls: UserName: NT Authority\NetworkService EntryExists: True UserExists: True IsActive: True IsOk: True StatusDescription: =========================================================== VSS Components Availability Status: OK Description: VSS components are accessible =========================================================== VSS Writers Status Status: OK Description: All VSS writers are working correctly Writers: Name: Task Scheduler Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} State: [1] Stable IsOk: True Error: No error Name: VSS Metadata Store Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} State: [1] Stable IsOk: True Error: No error Name: Performance Counters Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} State: [1] Stable IsOk: True Error: No error Name: System Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} State: [1] Stable IsOk: True Error: No error Name: ASR Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} State: [1] Stable IsOk: True Error: No error Name: Shadow Copy Optimization Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} State: [5] Waiting for completion IsOk: True Error: No error Name: FRS Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} State: [1] Stable IsOk: True Error: No error Name: WMI Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} State: [1] Stable IsOk: True Error: No error Name: MSSearch Service Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2} State: [5] Waiting for completion IsOk: True Error: No error Name: Registry Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} State: [1] Stable IsOk: True Error: No error Name: NTDS Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} State: [1] Stable IsOk: True Error: No error =========================================================== VSS Shadow Storages Status Status: OK Description: All VSS shadow storages are configured correctly Storages: ForVolume: C:\ OnVolume: C:\ Used: 96 MB Allocated: 50 GB Maximum: UNBOUNDED Minimum: 320 MB VolumeSize: 3721 GB Available: 3218 GB TargetMaximum: 372 GB MaximumGreaterThenMinimum: True MaximumIsEnough: True MaximumIsNotReached: True AvailableIsEnoughForMaximum: True IsOk: True Description: =========================================================== Disk Free Space Available Status: OK Description: All disks have enough free space Volumes: Name: C:\ DeviceId: \\?\Volume{1c4947d2-e53e-e711-a993-6679abe43d90}\ Size: 3721 GB Available: 3218 GB Minimum: 320 MB IsOk: True Description: IsMounted: True Name: E:\ DeviceId: \\?\Volume{0005f107-0000-0000-0000-100000000000}\ Size: 1862 GB Available: 1520 GB Minimum: 320 MB IsOk: True Description: IsMounted: True =========================================================== Disk I/O Load Status: OK Description: All disks are currently not overloaded Disks: Name: 0 C: DiskBytesPersec: 437574 DiskReadBytesPersec: 173144 DiskReadsPersec: 9 DiskTransfersPersec: 36 DiskWriteBytesPersec: 264429 DiskWritesPersec: 27 PercentDiskReadTime: 6 PercentDiskTime: 28 PercentDiskWriteTime: 23 PercentIdleTime: 74 IsOk: True Name: 1 E: DiskBytesPersec: 0 DiskReadBytesPersec: 0 DiskReadsPersec: 0 DiskTransfersPersec: 0 DiskWriteBytesPersec: 0 DiskWritesPersec: 0 PercentDiskReadTime: 0 PercentDiskTime: 0 PercentDiskWriteTime: 0 PercentIdleTime: 97 IsOk: True =========================================================== NTFS Volume Access Control Configuration Status: OK Description: All volumes have correct access control configuration Volumes: Name: C:\ SystemHasAccess: True SystemSid: S-1-5-18 IsOk: True Description: "SYSTEM" account has "Full Control" access Name: E:\ SystemHasAccess: True SystemSid: S-1-5-18 IsOk: True Description: "SYSTEM" account has "Full Control" access =========================================================== Event Log Status: Warn Description: Some VSS-related errors or warnings occurred during the previous day Events: Timestamp: 2018/10/30 10:31:50 AM Type: Warning Source: VSS Message: A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: PrepareForSnapshot Event Context: Execution Context: Writer Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Name: Microsoft Hyper-V VSS Writer Writer Instance ID: {51b65980-2447-4878-9507-c4a25021a881} Command Line: C:\Windows\system32\vmms.exe Process ID: 4032 InstanceId: 8229 SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8229 Timestamp: 2018/10/30 10:18:48 AM Type: Warning Source: VSS Message: A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: PrepareForSnapshot Event Context: Execution Context: Writer Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Name: Microsoft Hyper-V VSS Writer Writer Instance ID: {51b65980-2447-4878-9507-c4a25021a881} Command Line: C:\Windows\system32\vmms.exe Process ID: 4032 InstanceId: 8229 SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8229 Timestamp: 2018/10/29 11:04:06 PM Type: Warning Source: VSS Message: A VSS writer has rejected an event with error 0x800423f3, The writer experienced a transient error. If the backup process is retried, the error may not reoccur. . Changes that the writer made to the writer components while handling the event will not be available to the requester. Check the event log for related events from the application hosting the VSS writer. Operation: PrepareForSnapshot Event Context: Execution Context: Writer Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Name: Microsoft Hyper-V VSS Writer Writer Instance ID: {51b65980-2447-4878-9507-c4a25021a881} Command Line: C:\Windows\system32\vmms.exe Process ID: 4032 InstanceId: 8229 SearchLink: https://www.google.com/#newwindow=1&q=VSS+event+id+8229