BUExec15 withj HyperV - Migrated VMs, How to reflect in BUExec
I'm running Backup Exec 15 on Windows Server2012 R2, which was once a Hyper-V host, but is now only the Backup Exec 15 Host. I have two Hyper-V hosts (also Server 2012R2) that are not clustered but I have done a few live migrations and offline migrations between the two. Lets call them the following: BUE1, HVH1, HVH2 I'm still seeing the migrated VMs in their old locations. BUE1 shows 12 guests (it still has the Hyper-V components, but none of the guests), some with failures and many with successful backups from the last scheduled backup. Many of the same VMs show on HVH1, and a few on HVH2 HVH2 was added last, so nothing has been migrated from it, only to it. for instance, the VM DC1 shows thus: BUE1 = Success (2/9/2018) HVH1 = Fail (2/9/2018) HVH2 = Success (2/9/2018) - this is its actual home after being migrated from BUE1 to HVH1 then to HVH2 How do I get Backup Exec 15 to know what host a VM actually lives on now and stop indicating failed backups because guests no longer reside on that server?Solved1.7KViews0likes4CommentsSQL Backup Failing
My Backup fails everyday with this issue Backup- \MSSQLSERVERV-79-57344-863 - The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem. V-79-57344-863 - The SQL Server backup interface has reported a problem. Further details can be found in the job log. Restarting the SQL Server service or the server may correct the problem. Backup - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time. Try running the job later. No other backups are running nothing is using the VSS writers. I check wiht vssadmin list writers they are fine and I'll reboot the server run backup still have this issue. Any ideas?1.9KViews0likes4Comments