I have several questions I hope I can get answered here.  I have both SMVI 2.0 and BE 2010 running in my environment and am wondering if it is okay that they both run, at different times of course, on virtual machines in my infrastructure. Specifcally I am thinking about the VMware tools driver and the BE agent which installs its own driver. I have been told by Symantec to remove the sync driver/vss provider and install the BE agent instead so my BE jobs will run succsesfully.  Will this mess up my SMVI backups? Next, if an SMVI backup fails will the retention portion of the job kick off, removing any backups outside that retention, could it effectively eave you with no backups? And finally, I have consolidated all VMs into one job in SMVI.  Is there a limit to the number of datastores you can backup simultaneously in SMVI? Thank you for any help. ... View more

SnapManager for Exchange verifications failing with following error: Windows Event Log *****BACKUP DETAIL SUMMARY***** Backup group set #1: Backup SG [First Storage Group] Error: Failed to verify physical integrity of the databases. *****BACKUP RESULT SUMMARY***** Backup group set #1: Backup SG [First Storage Group]: Backup OK, verification failed Backup failed.[SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object.. SME Log [12:01:10.754]  BackupVerification Job of JobID 2654 starts to run on server Vmmail2. [12:01:10.785]  The destination volume of the source Logical Disk Q FlexClone State is Success and SnapMirror State is Unknown. [12:01:17.785]  Mounting Snapshot [exchsnap__vmmail2_08-13-2010_12.00.38] for LUN Q created from Computer VMMAIL2 [12:01:17.801]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint] [12:01:19.426]  Snapshot will be mounted on subdirectory [MPDisk013] [12:15:23.614]  [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object..  (SnapDrive Error Code: 0xc00403e3) [12:15:23.614]  SnapDrive failed to mount the snapshot. [12:15:23.614]  [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object.. [12:15:23.614]  Unable to mount snapshot, abort verification. [12:15:23.614]  [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object.. [12:15:23.614]  BackupVerification Job of JobID=2654 is finished with status Failed. [12:15:24.098]  [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object.. [12:15:24.192]  [SnapDrive Error]: Failed to create disk in virtual machine, Failed to Map virtual disk: Object reference not set to an instance of an object.. [12:15:26.926]  Error code: 0xc00403e3, LUN: Q:\ [12:15:26.926]  An autosupport message is sent on failure to the storage system of LUN [Q:\].  [12:15:26.926]  ***BACKUP VERIFICATION STATUS: First Storage Group [12:15:26.926]  Failed to verify physical integrity of the databases. Any help is appreciated as my disk is filling up as logs are not being truncated. Thanks! ... View more

Just finished first NFS deployment and am wondering how to lay out our Exchange server.  With our Exchange deployment on FC we made 3 separate volumes: mail (for OS +Queues), mail_sg1 (database), and mail_logs (logs).  Our exchange on the FC environment is backed up via Snapmanager for Exchange and I believe they require separation of volumes as such.  We do not have SME for the NFS environment and I am not sure what we are going to use just yet.  We will be using Snapmirror to replicate the volumes and one caveat I noticed with the information store and logs being on different volumes is on the destination end of Snapmirror when attempting to restore the logs and DB will be out of synch.  For example an information store from 12:00 and logs from 12:05 which I still haven't found a solution to. Anyone have thoughts as to how they laid out their Exchange on NFS? Should I bother separating the volumes or just keep them all together?  Also would appreciate feedback for Snapmirror issue as well. thanks, ... View more

Received email notification of above error but there is plenty of space on volume, lun and OS. Backup is remotely verified. SME logs [06:15:21.012]  Starting asynchronous DoSnapshotSet. Please wait... [06:15:22.012]  Operation pending, please wait...(1) [06:15:27.012]  Operation pending, please wait...(2) [06:15:30.011]  Error in calling VSS API: Error code = 0x8007000e Error description: [06:15:30.136]  CLEANUP FAILED BACKUP [06:15:30.136]  Warning: Invalid SnapInfo folder renamed to: [06:15:30.136]  P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.485675_invalid [06:15:30.136]  Rename SnapInfo folder from and to: [06:15:30.136]  P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.48 [06:15:30.136]  P:\SME_SnapInfo\EXCH__VMMAIL2\SG__First Storage Group\03-30-2010_06.03.485675_invalid [06:15:30.574]  Error code: 0x8007000e [06:15:30.574]  An autosupport message is sent on failure to the storage system of LUN [Q]. Applog shows Event Type: Error Event Source: Navssprv Event Category: None Event ID: 4110 Date: 3/30/2010 Time: 6:04:47 AM User: N/A Computer: VMMAIL2 Description: Data ONTAP VSS hardware provider's AbortSnapshot method is called [SnapshotSetId={ab52eabf-1b56-4598-8cb3-ee26b52254f4}]. VSS has failed the current shadow copy session because the previous errors are not continuable. Googling brought me to this KB: http://support.microsoft.com/kb/924262 but the max snapshots are not close to being reached. I keep 7 backups. I noticed the SnapInfo folder named 03-30-2010_06.03.485675_invalid What causes an invalid Snapinfo folder? On successful backups I see a Logs folder that looks like it holds exchange logs, a couple of XML files and an SME file. Thanks for any help. ... View more

I am running SMVI 2.0 with roughly 25 jobs spanned out through the day/night.  At random it seems one or two of these jobs fail. SMVI log states the following: 2010-03-23 08:32:56,849         ERROR - VM "EVSQL" will not be backed up since VMware snapshot create operation failed. VCenter log states: Create virtual machine snapshot EVSQL Cannot create a quiesced snapshot because the snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.  VMware tools is up-to-date. hostd.log [2010-03-23 08:30:45.782 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] Tools version status: ok [2010-03-23 08:30:45.782 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] VMware Tools are current in guest: true [2010-03-23 08:30:48.279 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] Quiesced snapshot backup agent event: (vim.vm.BackupEventInfo) {    dynamicType = <unset>,    eventType = "keepAlive",    code = 0,    message = "", } It repeats the above message until two minutes later when it aborts (see message below) 001b78592710/EVSQL/EVSQL.vmx'] Notifying completion of quiesced snapshot via backup agent. [2010-03-23 08:32:39.408 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] Tools version status: ok [2010-03-23 08:32:39.408 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] VMware Tools are current in guest: true [2010-03-23 08:32:39.408 F65FC6D0 verbose 'vm:/vmfs/volumes/4aafb0e2-37936ca0-d01a-001b78592710/EVSQL/EVSQL.vmx'] Quiesced snapshot backup agent event: (vim.vm.BackupEventInfo) {    dynamicType = <unset>,    eventType = "providerAbort",    code = 3,    message = "Snapshot operation aborted", } If I run the SMVI job manually it completes successfully.  I can also create VMware snapshots at will.  This is just one example but I have 1-2 SMVI backups that fail a day with the same error. As a side note, does SMVI create a snapshot of VM memory and does it quiesce the guest file system?  Two of these are options for vmware snapshots and SMVI does not mention the options it uses. Thanks for any insight. ... View more

For SnapManager for Exchange to work it needs the exchange database and logs on separate physical RDMs.  This results in them being housed on different volumes and therefore being victim to different lags on Snapmirror.  I have attempted to restore the database and logs on the snapmirror destination side and encountered errors mounting the information store due to the time difference of the logs and the exchange database.  How can I get around this to make sure the logs and DB are timed correctly to avoid potential issues in bringing up the other side? ... View more

I am reinstalling SMBR on a virtual machine that is using the HBAs of the ESX host Emulex LPe1150 and while installing the netapp_windows_host_utilities_5.2_x86.msi I received an error. The following hotfixes are not available on the system: 1. Q945119-SP2 - storport.sys (Required: 5.2.3790.4189/Installed: 5.2.3790.4021) Please install the hotfixes listed and retry the installation. Where do I find this required version? ... View more