replication of hyper-v server
Hello, I have 2 server that are hosting number of virtual machine using Hyper-V. I want to replicate number of this hyper-v server to a third host, so that in case of host failure I could immediately put this crucial hyper-v servers online from this third server. how do I do this using BE16? what will be the time deference between the replica? and what will be the minimum time that I could replicate? how demanding will it be on the production server I/O the replication process ? Thanks:robothappy:Solved5.2KViews0likes14CommentsBacking up Hyper-V Host and VM's BE 20.6
Hello, I am in the process of implementing Backup Exec 20.6 as our backup solution. I have all of our physical servers moved over and running good backups and I'm moving on to our Hyper-V Host and Virtual servers. I installed the agent on the host and the option to install the agent on the virtual servers was already checked so I left it that way. I added the Hyper-V Host and each individual virtual server, (I have 3 on this host), to the servers list. I went to setup the backup job for the host and this is where I get confused. The backup options for the host have drive C: (OS), Drive D: (home of the virtual servers), and also lists each virtual server under the "Microsoft Hyper-V Servers". If I wanted to restore the complete host, including all virtual servers, I'm guessing I would just leave everything checked and create the backup job. I'd rather like to be able to restore each individual server, (including just the host for the OS), with the ability to restore a virtual machine to a different host. What is the recommended way to run backups in this scenario? Thanks, JeffSolved2.8KViews0likes3CommentsBACKUP HYPER-V VM with SBS2011 and Exchange fail. V-79-57344-34070
Hi all. I do have a job in BE 15 wich backups all my VM from my Windows Hyper-v Cluster. All was working until the BE starts to give an error on one specific VM wich is a Small Business 2011 with exchenage 2010. I think the issue is related with a name change of the exchange database, on wich i had done a move malbox users from original database to a new one to clean up old stuff and problably some garbage records. The error when the job to back up all vms is: Final error: 0xe0008516 - The database specified for the snapshot was not backed up because the database was not mounted. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-34070 Errors Click an error below to locate it in the job log Backup- srvhvcl.clandeiro.localV-79-57344-34070 - Snapshot Technology: Initialization failure on: "VRTSRV::\\srvhvcl.clandeiro.local\Hyper-V?HA?VM\SRVSBS01". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). Snapshot technology error (0xE0008516): The database specified for the snapshot was not backed up because the database was not mounted. Check the Windows Event Viewer for details. If i do a test to this job it works, if i do a test credentials it also works and if i do a simple backup job only Information store database of exchange it also works. If i login to the VM and do the vssadmin list writers all of them respond with no errors. The only thing was the change of the exchange database but everyone is happy and working and also the backup exange only also works. Not the full Hyper-v VM jobs. Is there anywhere else i need to update the name of the database to recognized by the Hyper-v job????Solved2.6KViews0likes5CommentsStaging & Hyper-V restores
This article-- https://www.veritas.com/support/en_US/article.000075462 --leaves me with a few questions: "Tape backups require a staging location that is at least as large as the data that you back up." The way I read this, restore requires enough space for all data in the backup job. But to be able to do a GRT restore from any arbitrary VHDX, we need enough staging space for the largest VHDX backed up, plus 1GB for GRT metadata. Correct? A non-GRT DR restore (restoring an entire Hyper-V host) requires no staging space at all, even if the job was GRT-enabled during backup. Correct? A non-GRT VHDX restore (restoring an entire VHDX) requires no staging space at all, even if the job was GRT-enabled during backup. Correct?Solved2.1KViews0likes4CommentsVeritas16 /Backup Exec 15
Here is the Issue: I am using Backup exec 15 (14.2) V-Ray edition and using agentless methodology to take backup of my virtual infrastructure on Hyper-V platform. I am taking backup of virtual machines (11) splitting them in different in jobs with GRT enabled and agent installed on windows machine. I amusing Full backup and Increment strategy to keep 1-3 month data having full every month or every 3 months. I have SQL, SharePoint, Terminal and File Server in my environment. Issue s incremental backup I am receiving for these virtual machines are very high like for SQL 120-150 GB every incremental (Tried disabling and enabling SQL GRT no difference but if I disable file folder GT backup size reduces significantly but restore time increase due to compression but I need file folder GRT for my servers). I tried agent base backup for SQL and result was same despite checking taking SQL backup log after backup job feature enabled or not. For share point VM size is 80 GB and actual data is 40 GB but incremental is 20-30 GB (only file folder GRT enabled) and same applies to terminal servers like 10 GB incremental and File Server which is also AD is creating 40-50GB incremental. I thought may be there is some issue with tool and I upgraded it from BE 15 (14.2) to veritas 16 Trial and issue remain same. I hold backups by veritas and used another tool agent base backup and I was wondering hat backup size for full and incremental was very small like for SQL full only 70GB as compare to BE 15/Veritas 400 GB and Incremental 10GB as compare to 150 GB same applies to other servers. I am wondering should I go for upgrade or simply move away from BE/Veritas as other product is working very fine. Note: I have virtual infrastructure so I prefer to have VM base backups as it’s easy to manage and recover incase of any issue.2.1KViews0likes6CommentsRestored 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 all2KViews0likes1CommentBackup Exec 15 - FP5 - 2012 R2 Hyper-V Cluster - GRT Backups Stuck in Snapshot Processing
Hello all. We have a 2012 R2 Hyper-V Cluster, all patched to date. This cluster has 6 nodes, each one connected via FC to a 3PAR 7400c All-Flash array. Each cluster node hosts about 20 VMs and 2 or 3 CSV (so each VM role has direct access to their storage via FC as it is its own Coordinator Node). With that in mind, we installed BEX 15 FP5 in each cluster node so that we could backup the VMs directly through FC and not via Ethernet (it's way faster and we do have a lot of data). Since implementation, eveything is going smooth (with some issues sometimes) with all cluster nodes except one. Every cluster node has either a FC Tape Library or a SAS Drive (all LTO6/LTO5, all firmwares up-to-date). This cluster node, VHT06, shows erratic behavior. It starts the granular job, but hangs in a random VM in "Snapshot Processing". We can't cancel the job unless we stop the "vmms.exe" service or reboot the cluster node. If we manage to cancel the job, the VM gets stuck in "Backing up..." within Hyper-V manager and can't reboot. We thought it could be the tape library, so we changed it. Still the same issue. We even evicted and reprovisioned the cluster node two times. Backup through RAWS works fine. Marco1.9KViews0likes2CommentsBacking up Hyper-V exchange server
Hi. I have an Hyper V host on it I have my exchange server (virtual). I wont to backup it in that way that iw will be posible to restore the exchange vhd if needed and restor a specific mail from any of my exchange data bases. Is it posible? Wht is the best way to do this? thanks a lot.1.8KViews0likes9CommentsBUExec15 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.7KViews0likes4CommentsV-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.1.4KViews0likes3Comments