BE 2014 won't backup VMs on Hyper-V 2012 R2
Hi all. The Backup Server is running Server 2008 R2 Standard with Backup Exec 2014 installed. All updates have been applied from live update. I'm trying to backup VMs on a server running Hyper-V 2012 R2, but I continue to receive a "Final error: 0xa0009679 - A failure occurred querying the Writer status for a Hyper-V virtual machine" error. Running VSS Admin List results in a "Retryable Error" for the Microsoft Hyper-V VSS Writer. I have tried restarting the server already and that didn't help. Any tips? Event Viewer also gives me this at the time of the backup failure: 1) Application and Service Logs > Microsoft > Windows > Hyper_V-VMMS > Admin: Failed to fix-up absolute VHD paths in configuration of virtual machine 'VM Name': Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced. (0x8007052F). (Virtual machine ID AEB2B426-05DD-4C4F-AC8F-330B0D57B8D4) 2) Windows Logs > Application: 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. Other details: The Hyper-V 2012 R2 OS has been separated from the VMs on the HD. OS is on C and the VMs are on D. VM backups continue to run perfectly fine from a Hyper-V 2008 R2 server. All servers mentioned are using the same storage device. Any help will be much appreciated. Thanks everyone.
Backup Exec Become Very slow rate job after Windows Update
This is my third thread for the same problem in the same server, everytime that i make Windows Update, The job to Backup Mailbox Databases become very Slow. I have a server with 2008 R2 with backup exec 2010 R3 installed and four Hyper-V servers, CAS-HUB server, Mailbox Server, Blackberry Server and a DC server. i have two Backup job, one for Mailboxes Databases, and othet for the four Hyper-V, Mailboxes job run in the morning, and Hyper-V job run at night. Normally Mailbox job run between 5 and 6 hours, between 2600 and 3000 MB/s job rate for 600 GB of data. The other Job run between 5 and 6 hours, Between 3000 to 4000 MB/s for 900 GB of data. Everytime that i make Windows Update on the Phisical Server, the Mailbox job become very slow between 500 and 600 MB/s and it take between 19 to 20 Hours, i search in several forums, blog, tech support guides, and there isn´t solution for my case. The Jod to Backup Hyper-V dont have any problem, run normally. is OK is this occurs one or two times, but is everytime, i decided install Windows Update in the phisical server every four month, but this isn´t a correct security police in the company, my only solution when this happend is uninstall-reinstall the Backup exec Server, but i make the windows update last week-end, and i Unnistall-Reinstall 3 times and the problema continue. This time Unnistall-Reinstall dont solve my problem, and when i did this, i have to restat the server, wich i do early in the morning when nobody is using the email service. I dont know what else to do, Symantec support dont give any solution about this topic. If any body can help, the Backup is over LTO 4 tapes, Drivers are update, Backup Exec 2010 R3 full patches. The Mailbox is exchange 2010.
Catalog error on one particular sever
Hi I'm back. After small issue to upgrade to backup exec 2012 sp1a, I have a very strange error. If I make a full backup of my virtual servers (CSV cluster), the backup to disk works just fine. But when the jobs start to make a duplication to tape, I receive an error saying 'An error was encountered writing to the on-disk catalogs'. the final error is The job failed with the following error: An error occurred while retrieving catalog information I found this article http://www.symantec.com/business/support/index?page=content&id=TECH53393 but it was no solution. The error is only generated on a particular server.
GRT backup makes Hyper-V VM unresponsive...
Hi all! So I was all excited when SP2 was released because my migration from my current backup solution to BE was on hold due to us moving towards Hyper-V 2012. So the day it was released, I installed it and thought "Alright! Let's start backing up Hyper-V VMs!" and then BAM! I had all VMs on a particular CSV become unresponsive because I was backing up one VM on that CSV. The only way out was to shut the host down completely and bring those VMs backup on the other node, not the best way to start. Here's my environment and some more of my experience: Hyper-V Environment 2x Hyper-V 2012 hosts w/ BE 2012 SP2 RAWS agent installed. Hyper-V hosts are clustered and using CSVs. Storage provided by a 6 node P4500 cluster. HP Lefthand MPIO used for multipathing. Lefthand VSS provider not installed. SCVMM 2012 SP1 is used to manage the cluster. Backup Exec Environment Backup Exec 2012 SP2 installed Deduplication Disk Storage configured and is the current destination for Hyper-V backups. Guest VM Environment Server 2012 OS w/ latest Integration Services installed BE 2012 SP2 RAWS agent installed. I started with just trying to backup one VM to see how the whole process worked before I start rolling this out to other VMs. The scenario above was what happened after performing the first GRT enabled backup of the VM. I've since moved the VM to its own CSV so I can test just this server without potentially bringing down the environment. What I'm seeing is the backing up the VM's VHDXs is fine, every time. If BE just backs up the VHDXs, the job runs successfully and the VM stays responsive the whole time. I can make the BE backup just VHDXs by unchecking "Exclude virtual machines that must be put in a saved state to back up". If I check that box, BE first performs the VHDX backup successfully and then it attempts to perform GRT pass but the VM becomes unresponsive, more than likely from being put into a saved state. I've checked everything I can possibly think of to allow for live backups for the guest VM to no avail. All disks on the VM are basic NTFS drives, each with their shadow copy storage pointed to their own drive. The correct Hyper-V Integration Services is installed and "backups" are enabled in the VMs Integration Services configuration. I just for the life of me can't figure this out. It seems like it should be pretty straight forward. Any help would be greatly appreciated! v/r, Louisexchange 2010 hyper v 2012 R2
Hallo Zusammen, ich habe ein Problem mit Backup Exe 2014 SP2: Bei der Sicherung der virtuellen Maschine mit dem OS Win 2008 R2 auf dieser der Exchange 2010 installiert ist kommt folgende Fehlermeldung: Auf diesem virtuellen Computer wurde ein vollständiges Backup durchgeführt, da die Option zum Zurückgreifen auf ein vollständiges Backup gewählt wurde. Für diesen virtuellen Computer werden die Backup-Methoden 'Inkrementell' und 'Differentiell' nicht unterstützt. V-79-57344-38769 - Der virtuelle Computer 'Buehn-Exch-Hub' wurde offline gesichert, daher sind die VHD- und VHDX-Dateien nur absturzkonsistent. Wiederherstellung auf Dateiebene kann durchgeführt werden, die Ergebnisse sind jedoch unvorhersehbar. Für diesen virtuellen Computer kann keine Wiederherstellung auf Anwendungsebene ausgeführt werden. V-79-57344-38727 - Backup Exec konnte nicht die zur Wiederherstellung individueller Anwendungsobjekte erforderlichen Metadaten für den virtuellen Computer 'Buehn-Exch-Mail' abrufen. Sie können keine GRT-Wiederherstellung von Applikationsdaten von diesem Backup erstellen.
Backup Exec 2014 and Hyper-V Incremental Backups - Always Full Backups?
tl;dr summary: Is there any way of configuring Backup Exec 2014 to perform incremental backups of Hyper-V guest operating systems that doesn't result in a full backup of the guest VM being created each time an incremental backup is run? I'm looking for some clarification / better understanding of using Backup Exec 2014 to perform incremental backups of Hyper-V virtual machines. I am running a Backup Exec 2014 Media Server on a Windows Server 2012 R2 host. This media server backs up a couple of separate virtualization host servers in our environment. The virtulization host servers are running Windows Server 2012 R2, and each host server hosts several Windows-based (2003 through 2012 R2) guest operating systems. The Backup Exec Agent for Windows is installed on the virtualization host servers, as well as the various guest operating systems. I would like to perform a full backup of the Hyper-V guest operating systems once a week, and a differential or incremental backup of the guest operating systems every other day of the week. However, it appears that every backup of the guest OSes, whether full or incremental, results in a full backup being performed (at least judging from the amount of disk space the backups are consuming.) I have reviewed the following Symantec support URLs, http://www.symantec.com/connect/forums/incremental-backup-hyper-v-vms and https://www-secure.symantec.com/connect/sites/default/files/BE%202010%20R2_%20Agent_for_ms_hyper_v_FAQ.en-us.pdf which pertain to earlier versions of Backup Exec and Windows Server, and basically state that differential or incremental backups of Hyper-V guests is not possible, because Microsoft doesn't provide any API to perform such backups of Hyper-V guest OSes. However, the Backup Exec 2014 Agent for Hyper-V documentation states "This version of Backup Exec supports the Windows Server 2012 vhdx file format and Microsoft incremental backups" (p. 884) and also describes differences between Backup Exec incremental backups for Hyper-V and Microsoft incremental backups for Hyper-V. So, my questions are: Do incremental backups of Hyper-V guests require the guest VMsto be using .VHDX format for their virtual hard disks for incremental backups to work properly? Is there any way of using Backup Exec to perform incremental backups of Hyper-V guest operating systems that don't result in a full backup being created each time an incremental backup is run? What are the best practices here? I like the idea of performing backups of the Hyper-V guests running on the host server, but with every backup essentially being a full backup, I don't have enough backup storage capacity. I could back up each Hyper-V guest OS as a "native" server, but then I lose the ability to quickly restore a full VM; I'd have to restore as if it were a physical server. Any guidance or clarification would be greatly appreciated. Thanks!