Cannot backup SQL DB on virtual machine due to "zzzVirtApp000zzz" with GRT mode
Dear All, I'm recently experiencing an issue in my backup for one specific virtual machine. Information about my infrastructure : Media server : Windows Server 2003 Enterprise Backup exec 2010R3 SP1 with hotfixhttp://www.symantec.com/business/support/index?page=content&id=TECH167791 Virtual Machine: Windows server 2008R2 SQL server 2008R2 VMware tools installed without VSS Backup exec agent installed 3 partitions that are on the same datastore (no RDM) VMware : version 5.1 Since last week (tuesday) my backup for all VMDK is in failed status due to this error : Backup- VMVCB::\\vcenter\VCGuestVm\DATACENTER NAME\vm\VMNAME - Error. Cannot backup directory \zzzVirtApp000zzz and its subdirectories. I saw on this technote that a hotfix is available for this issue : http://www.symantec.com/business/support/index?page=content&id=TECH169958 But this hotfix is already installed since a long time on my media server + agents. Other strange thing my backup failed tuesday to thursday but successfull on friday to sunday. If I want to restore my VM via the GRT process, I'm able to see all partition the only missing thing is the SQL content. I read a lot of article for this issue and normally the previous hotfix should fix the issue but it's not the case for the moment. Anyone has an idea of what to do next ? Regards,Solved707Views3likes3CommentsExchange 2010 Differential backup runs very slow when GRT is enabled and Destination Folder is on Dedupe
Hi, We have been running through this very slow backup problem on Exchange Differential for 6 weeks already. We are using Symantec Backup Exec 2010 R3 SP2 and Hotfix 180429 & 176937 installed. Our first setup was Weekly Full (GRT enabled) + Daily Differential (GRT Disabled) and it was running smoothly, the job rate of differential backup runs at 1,500MB/min and it completes successfully at about 15 minutes only. On July 29, 2012, we decided to create new backup templates for Exchange inside a policy so that we could also enable GRT on Differential. After we have successfully enabled GRT on Differential, we ran the Differential backup on July 2, 2012 and we observed a tremendous effect in job rate, it went down from 1,500MB/min to 22MB/min. In addition to this slow job rate, we are also experiencing a failure on our Wednesday(3rd day) differential backup with the following error message: Backup- \\DMCIMAIL.dmcinet.com\Microsoft Information Store\DATABASE01 V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options. The following error was returned when opening the Exchange Database file: '-1014 The database is out of page buffers. ' Backup- \\DMCIMAIL.dmcinet.com\Microsoft Information Store\DATABASE02 V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure. This can be caused by low memory or disk resources. We have several discussions with Symantec engineers but we are still unable to fix this problem. If we look into the situation, we can easily solve the issue on job rate by just disabling the GRT feature but we would want to keep this as we are looking forward on using granular restore in the future. We are stuck in this situation are any suggestions or recommendations that would solve the issue would be greatly appreciated. We hope to solve this very soon as we are already running through this problem for 6 weeks already. Thanks in advance!1.1KViews3likes6CommentsTemporärer GRT Ordner - Fehler in BE 15??
Hallo zusammen, beim Test von Backup Exec ist mir etwas aufgefallen: Ich habe für den temporären GRT Ordner ein Verzeichnis auf der Partition F:\ auf dem Backup-Server angelegt. Dieses funktioniert auch bei den Sicherungen von VMWare Servern. Will ich aber unsere Exchange DAG sichern, so kommt immer ein Fehler: V-79-57344-4617 - Der Backup-to-Disk-Ordner oder der Pfad für die Bereitstellung temporärer Daten auf dem Backup Exec-Server muss sich auf einem NTFS-Volume befinden. Wählen sie irgendeine der folgenden Möglichkeiten und senden Sie den Auftrag dann erneut Jetzt habe ich mal auf beiden Exchange-Servern auf der Partition D:\ ein Temp-Verzeichnis für GRT angelegt und dieses in den globalen Einstellungen von Backup Exec eingetragen. Und siehe da, auch das GRT Backup vom Exchange läuft. Es werden fleissig beide Verzeichnisse gefüllt und anschließend wieder gelöscht und ich kann einzelne Mails etc. wiederherstellen und muss nicht die ganze DB zurücksichern. Jetzt sehe ich das ganze jedoch als Fehler von Backup Exec an. Es kann ja nicht sein, dass er für VMWare Server den Pfad auf dem lokalen Backup Server akzeptiert, aber bei Exchange nur einen Pfad, der auch auf dem Exchange verfügbar ist und diesen dann nutzt. Das würde ja sonst bedeuten, dass ich die Partitionen anpassen muss, sprich auf dem Backup Server F:\ in D:\ umbenennen, damit alle GRT Backups sauber durchlaufen. Hier müsste eingentlich durch ein Update der Bug beseitigt werden so wie ich das sehe. MfG jayjay0911.Solved2.5KViews2likes2CommentsBackup Exec 15 after Update no communication with vCenter - all AVVI jobs fail
After updateing our customers BEX 2014 environment (physical an virtual) all jobs defined as RAWS with transport via LAN are running smoothly. Accidently all jobs using the AVVI with vCenter are stopped and second the local Remote Agent for Windows running at the backup server is stopped at the moment tto snap the VMware VMDKs. The log said "communication error". The vCenter is reachable like before and running well. First error is V-79-57344-65304 followed by V-79-57344-3844 because the local agent is stopped. What is the cause? Creating a new trusted link betwenn backup server and vCenter does not help. We use Windows Server 2012 R2 and vSphere 5.5.4.7KViews2likes20CommentsBackup Exec 2014 Exchange 2010 -515 The Timestamp in the next log does not match the expected timestamp
I keep getting this error on my Backup to Tape on Backup Exec 2014. Cannot Extract Mailbox messages from exchange backup. Review the job log for more information. When I do I get these V-79-57344-759 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-515 The timestamp in the next log does not match the expected timestamp. & V-79-57344-915 - Unable to complete the operation. The following error was returned when opening the Exchange Database file: '-1018 There is a checksum error on a database page. ' So far I tried changing the exchange options from High Availability Server from passive to active copy. And that didn't work so I changed it back. I read around that you can disable GRT but what exactly is that? Also what do I loose disabling that versus enabling it? Here's some more info about my servers Backup Exec 2014 64bit 14.1 rev 1786 hotfix 218257 Server 2008 rs Enterprise 24GB Ram Thanks for the help in advance1KViews2likes3CommentsBE 2014 Hyper-V Differential backups of VMs with GRT enabled receive exceptions - no data backed up
I've just installed and configured Backup Exec 2014 on a Windows 2012 R2 Hyper-V server and I'm receiving the following exception when I attempt to run a differential backup of my VMs with GRT enabled: During Granular Recovery Technology (GRT) operations, the necessary boot configuration files could not be loaded. Backups that were enabled for GRT may not be available for restore. No data is available for restore for these differential backups. Full backups succeed without issue. This exact error happens on both environments that I've installed BE 2014. Guest VMs are all Gen 2 VMs and both have 2012 and 2012 R2 guest VMs.2KViews2likes12CommentsV-79-57344-6017 - Database Database was not found, or could not be accessed.
Hi, I have this error only when I try to restore mailbox items only to specific mailbox database. Mailboxes from another database backup copies restore normaly. And when I check credentials - Check Failed with only this mailboxdatabase. Any Idea?2.3KViews2likes8CommentsBackup Exec 2010 R3 restore individual mailbox Exchnage GRT
Hey mates, When I`m trying to restore exchange 2010 mailbox, I`m getting this error: Now what I've tried is, brwosing to the IMGxxx folder and renaming the VDB file to vbd.old and renaming the vbd_2012_10_28 to vbd_2012_10_28.old But I`m still getting this error. The strange thing is I've incountered this error before and I did the same workaround. I've checked the the credentials and everthing seems fine, it still give me succesfull backup. but I can reach them. thanks.Solved950Views2likes5CommentsContinue with Traditional Backups even though we are doing VMWARE Backups?
I have a file server that is virtualized. We own the VMWARE Agent for backup exec. This Virtual machine also has the Remote Agent installed on it. We have been doing two things. 1. Traditional Backups of the Files used by our users. So the files they access via network drives. We a full on Sunday, then incrementals all week, and then repeat. This is for disaster recovery but also used quite a bit to do restores for our users. 2. VMBackup - We have also been doing a VMWare Backup where it quieces the VM and gets you a copy of the VMDK and all that stuff. We run this once a week. It is quite a bit more data as it is the whole computer. So it backs everything. This is really for Disaster Recovery, more than day to day restores for users that delete a file etc... My question is with GRT and the Windows Agent can I stop doing the first item and switch to something where we do a Full VMBackup on Sunday, we then run incrementals all week using the VM Agent? Is this somethign other people are doing? Is this something you would recommend doing? I just got done finding out that Synthetic backups and Deduplication won't work together even though our sales rep said it would, so I wanted to make sure I asked this before getting too much further... but that is another story. Oh btw - We are using 2012. Yeah, been ruff.464Views2likes4Comments