Exchange Catalog Job Failure - 0xe00002f7 Cannot Extract Mailbox - VFF Open Failure
Using BE 2014 and its driving me nuts. One of the Exchange Incremental Backup keeps failing! It has been fine for a while. Other databases on the same server dont seem to return this error. Completed status: Failed Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information. Final error category: Resource Errors Catalog- \\MAIL01.X.ORG\Microsoft Information Store\X Mailstore V-79-57344-759 - Unable to complete the operation for the following reason: VFF Open Failure. This can be caused by low memory or disk resources. I tried these and it did not help. Also restarted all BE Services. https://www.veritas.com/support/en_US/article.TECH128187 https://www.veritas.com/support/en_US/article.TECH180039 If you guys could please give me any kind of help, it would be appreciated. Thanks!Solved2.5KViews0likes7Commentsincremental errors 0xe00095b3 Unable to create the virtual disk. Using deduplication storage
Hi. We have strange behavior of BE 2015. Environment: 1. BE2015 server with local disks for local disk-based storage. e:\ f:\ g:\ h:\, each logical volume on one HDD. installed features: Copy Server Configurations,Virtual Tape Library Support,Deduplication Option,Agent for VMware and Hyper-V,Agent for Applications and Databases. 2. Configured disk based storages in BE2015 using local disks and named: Deduplication disk storage 0001- H:\BackupExecDeduplicationStorageFolder Disk storage Full- E:\BEData\ Disk storage inc- G:\BEData\ Duplication storage- F:\BEData\ 3. Test server being backed up on ESXi named wksmon01. It is just a regulary flat machine with win7 no additional application on it. 4. Test job which backs up virtual machine wksmon01 with options: GRT (for files) + NBD. Two templates: full -uses "Deduplication disk storage 0001", incremantal- uses"Disk storage inc". One stage: duplicate to disk immediate after full backup uses "Duplication storage". Let's start action! а. Full backup-passes with no errors. GRT provide restore individual files. b. Automatically passes duplication stage. No errors. c. First Incremental backup- passes. No errors. d. Remove duplication storage: - make "Duplication storage" to disabled state - make disk F:\ offline using disk management console e. Second incremental backup- ERROR. 0xe00095b3 - Unable to create the virtual disk. Full error text in attach. After abig series of test jobs with different options and different storage i have that: Incremental jobs start to fail only after removing "Duplication storage" which was used to duplicate baseline full backup. If i change job option tonot using GRT than all subsequent incremental jobs runs fine with no errors even after removing "Duplication storage". If i use "Deduplication disk storage 0001" for both full and incremental jobs with GRT enabled thanall subsequent incremental jobs runs fine wiht no error also. If i use "Disk storage Full" for full backup and "Disk storage inc" for incremental with GRT enabled i also have no errors with all subsequent incremental jobs even after removing "Duplication storage". SUMMARY. incremental jobs with enabledGRT optionstart to fail after removing "Duplication storage" which was used to copy baseline full backup in case when full backupuses Deduplication disk storage and incremental jobs use Disk storage.2.4KViews0likes9CommentsBE 2014 SP2 Hyper-V Backup Failed to Mount one or more virtual disk images RDX drive
Hi, We are having an issue at a number of our customers sites that backup Hyper-V VM's using Backup Exec 2014 SP1 & SP2 to RDX Cartridges. The backups complete with exceptions that the virtual disk images cannot be mounted. This stops the ability of being able to perform a GRT restore of individual items from the backup.The odd thing is that the virtual disk images can be manully mounted by windows directly from the RDX cartridge. I have attached a debug log from one of the machines for reference, and have also found the following post on the Symantec forum: http://www.symantec.com/business/support/index?page=content&id=TECH211717 http://www.symantec.com/business/support/index?page=content&id=TECH223818 The problem in the log looks to be as follows: [8664] 2014-12-20T04:28:05.666 [engidrapi] - CDiskLayoutImplementation::DisableAutoMount: Disabling AUTOMOUNT [8664] 2014-12-20T04:28:05.666 [mounter] - MSVSVirtualSystem::MountDisks() - Enter [8664] 2014-12-20T04:28:05.667 [mounter] - MSVSVirtualSystem::MountDisks: ***** This is Windows-8 or later, forcing AutoMount to be on ***** [8664] 2014-12-20T04:28:05.667 [engidrapi] - CDiskLayoutImplementation::SetAutoMount: Enabling AUTOMOUNT [8664] 2014-12-20T04:28:05.668 [mounter] - MSVSVirtualSystem::MountDisks: checking '\\.\PHYSICALDRIVE0' [8664] 2014-12-20T04:28:05.730 [mounter] - MSVSVirtualSystem::MountDisks: MBR disk signature 0x00000000 [8664] 2014-12-20T04:28:05.731 [mounter] - MSVSVirtualSystem::MountDisks: checking '\\.\PHYSICALDRIVE1' [8664] 2014-12-20T04:28:05.749 [mounter] - MSVSVirtualSystem::MountDisks: MBR disk signature 0x6f68ba71 [8664] 2014-12-20T04:28:05.749 [mounter] - MSVSVirtualSystem::MountDisks: checking '\\.\PHYSICALDRIVE2' [8664] 2014-12-20T04:28:05.755 [mounter] - MSVSVirtualSystem::MountDisks: MBR disk signature 0x90c0919b [8664] 2014-12-20T04:28:05.773 - bevs::IVhdFileUtil::load_VHD_structures: the VHD footer failed checksum verification [8664] 2014-12-20T04:28:05.775 [mounter] - MSVSVirtualSystem::MountDisks: file "M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx" Signature: 0X90C0919B Partition Count: 0 Dynamic: False GPT-Dynamic: False Storage Pool: False [8664] 2014-12-20T04:28:05.775 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.785 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.785 - Retry attempt 1 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.785 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.794 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.794 - Retry attempt 2 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.795 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.804 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.804 - Retry attempt 3 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.804 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.813 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.814 - Retry attempt 4 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.814 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.823 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.823 - Retry attempt 5 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.823 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.833 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.833 - Retry attempt 6 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.833 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.843 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.843 - Retry attempt 7 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.843 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.852 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.852 - Retry attempt 8 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.853 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.862 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.862 - Retry attempt 9 for mount of M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.862 - About to mount M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx [8664] 2014-12-20T04:28:05.871 - Failed to OpenVirtualDisk rc=1392 0x570 [8664] 2014-12-20T04:28:05.871 [mounter] - MSVSVirtualSystem::MountDisk() - mount of "M:\IMG000076\Virtual Files\E\Virtual Hard Disks\GCN-SBS.vhdx" failed with error code: 1392 [8664] 2014-12-20T04:28:05.872 [mounter] - Total Virtual Disks Mounted: 0 [8664] 2014-12-20T04:28:05.872 [mounter] - MSVSVirtualSystem::MountDisks() - Exit [8664] 2014-12-20T04:28:05.873 [engidrapi] - CDiskLayoutImplementation::SetAutoMount: Enabling AUTOMOUNT [8664] 2014-12-20T04:28:05.873 [mounter] - VDiskMounter::MountAllDisks:failed VirtualSystem::Initialize() [8664] 2014-12-20T04:28:05.873 [mounter] - Error mounting disks (0xe0009741) However as stated above, we can manually mount the vhdx file directly from the RDX cartridge and copy any files needed to be restored this way. We are not however able to restore individual mail items from and exchange store, without starting up a seperate virtual machine with the VHD attached. Does anyone else have the same issue? Any idea's on how to resolve this? So far we have 3 customers with the same issue, all using BE 2014 backing up Hyper-V VM's on Server 2012 R2. Thanks Alex1.8KViews1like11CommentsBackup 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.7KViews2likes20CommentsFailure backing up to NAS
Am running Backup Exec 2012 (SP4 + hotfix 217347)small business edition on Windows Small Business Server 2011 Standard. When attempting a full SDR backup to a 3TBHDD on a LS220D480 NAS it is getting to about 16.2GB and apparently whilst still working on the exchange information store mailbox database. It then just starts creating two 2KB files every minute whilst the backup rate dwindles down to nothing and just seems to hang there until I cancel the backup. However: a) if I run the same backup to tape or to a 1TB USB HDD(as opposed to the NAS HDD) it completes succesfuly, b) If I run the same backup but exclude the Microsoft Information Storeto the same NAS HDD it completes succesfully, c) If I run the same backup to the same NAS HDD, including the Microsoft Information Store but without enabling the GRT option it still fails. I've tried reformatting the NAS HDD but am struggling to make any sense of this. Have seen lots of chatter about 2KB files being created and possible connections to GRT ... but not found any answers for this case .... can't fathom why ok to tape and another drive but not ok to the NAS (until I exclude the information store from the backup). Thanks Rob1.2KViews1like7CommentsGRT Backup Sharepoint 2010,2013, Exchange 2007,2010
Hi All, I'm having problems with GRT backups of Exchange and Sharepoint. After major issues with BackupExec 2014, which i've been able to resolve (update with latest hotfix), this is the only issue left. What happens is that GRT jobs get stuck at Active: 0 of 4 (in case of Exchange its either 0 of 3 or 2 of 3) backup selections processed for GRT - Backgroud Process. If i disable GRT, backups run fine. The SMLog (Sharepoint backup, haven't had time yet to check Exchange) is flooded with: 5BECAT436022.7.2015 14:32:564572[5] [CatServerVSNListener::OnVSN::196] VSNType(1060), verbHint(102), flagHint(0) 6BEREMOTE396822.7.2015 14:33:005252[fsys\shared] - [memento::OpenRead] - \\?\UNC\tpqnap\backup\B2D01\IMG000020\pdi_state.txt 7BEREMOTE396822.7.2015 14:33:005252[fsys\shared] - [memento::OpenRead] - \\?\UNC\tpqnap\backup\B2D01\IMG000021\pdi_state.txt 8BEREMOTE396822.7.2015 14:33:005252[fsys\shared] - [memento::OpenRead] - \\?\UNC\tpqnap\backup\B2D01\IMG000022\pdi_state.txt 9BEREMOTE396822.7.2015 14:33:005252[fsys\shared] - [memento::OpenRead] - \\?\UNC\tpqnap\backup\B2D01\IMG000023\pdi_state.txt In the pdi_state.txt i get sPDI_RECOVERY_STATE=QUEUED and after i cancel the job i get sPDI_RECOVERY_STATE=ABORTED and iPDI_RECOVERY_RESULT=0xe0000f41:ffffffff I've already rebooted all the servers, updated agents on servers, recreated the jobs, moved job from dedup store to B2D store...nothing seems to be helping. Anyone else had this issue? BR751Views0likes4CommentsBackup Exec GRT Not Working Correctly
Hello, I'm trying to backup SQL databases on a Windows 2012 R2 server box that is running on VMware 5.1 but run into job exceptions every time. The exceptions are below. The VM itself is backed up so I can do full disk restores but none of the SQL databases are backing up. Credentials test successfully on this box so I'm not sure what else to check to resolve this issue, any help would be greatly appreciated. V-79-57344-38727 - Backup Exec was unable to collect the necessary metadata for virtual machine to restore individual application items. You cannot perform GRT-enabled restores of application data from this backup.3KViews0likes19CommentsBackup Exec 15 - GRT duplicate (Exchange issue)
I thought I would try posting on here - as Symantec Enterprise support are really poor. (in my long experience with BE 11d, 12, 12.5, 2010, 2010 R3, 2012, 2014) Brand new Dell server hardware, running Server 2012 R2 Standard, BE 15 (V-Ray)installed on RAID 1 array (new install - not upgrade), 2 x raid 0 arrays set up (1 x 3.2Tb, 1 x 13.2 Tb) configured as storage disks in BE 15. (all disks 600Gb 15K SAS). Using FC HP 1/8 G2 Autoloader LTO-6, with QLogic 8Gb FC card on x8 PCI-E (QLE2562) (both on Symantec HCL) B2D works as expected - (haven't tried backing upVMs (V-Ray functionality) yet - physical servers only - all with Windows agents deployed. All licensing for Applications and Databases and V-Ray etc. added to the BE server prior to agent deployment. As per usual with a BE release - GRT is still awful. 500Gb Exchange GRT-enabled backup duplicate to tape from one of the RAID-0 arrays got stuck - 9 hours later, have restarted the target server and the had to first restart the services (forcefully) Followed Symantec guidelines per their TECH articles on GRT. Didn't experience GRT duplicate issues with exactly the same servers with BE 2014 SP2 - had a whole host of Exchange 2013 restore issues that Symantec Enterprise support could do nothing to help with. I suspect BE version 15 is even more buggy than BE 2014 before it. Will be logging a case with Symantec Enterprise support on Monday. I thought I would see if there is any feedback on here.Solved1.9KViews1like5CommentsTemporä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.5KViews2likes2Comments