Protecting Hyper-V Virtual Machines on SMB using Backup Exec 20.4
Starting from Windows Server 2012, virtual machines in Hyper-V can be configured to use Server Message Block (SMB) 3.0 file shares as storage just like local volumes. By using SMB shares, storages for Hyper-V can be converged and operating costs can be reduced. Additional advantages of Scale-out file servers include continuously available file services, automatic load balancing and easy management of servers. Deploying Hyper-V over SMB shares from Scale-out file servers is an ideal solution for Hyper-V.7.8KViews2likes1CommentInstantly Available: Backup Exec™ 15 Feature Pack 5
Recover Instantly with Instant Recovery for VMware and Hyper-V Virtual Machines!Backup to Hybrid Cloud with Private, Hosted and Public Cloud Storage options!Protect Microsoft SQL Server 2016, Exchange 2016 CU2 and much more7.7KViews10likes8CommentsEnhancing resiliency for Instant Recovery
Now not just instant, but also resilient. The Enhanced Resiliency for Instant Recovery increases the data and application availability of virtual machines that are instantly recovered. This improves business continuity in case the Backup Exec server or the Hyper-V server must be restarted.6.7KViews2likes0Commentsreplication 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.2KViews0likes14CommentsFeature Pack 1 for Backup Exec 15 delivers improved performance, intelligent backups and enhanced platform support
Hot on the heels of Backup Exec 15 we are excited to announce the availability of Feature Pack 1 (FP1) for Backup Exec 15. Feature packs build on the core strengths of Backup Exec by addressing the top customer needs for hybrid environments and mark the transition away from major releases into a more continuous delivery model.3.1KViews10likes2CommentsBacking 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.7KViews0likes3CommentsBACKUP 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.6KViews0likes5Comments