Hi: We have an issue with our snapshot backups in that we have a 2-node Exchange 2003 cluster that gets a snapshot of its databases using Snap Manager for Exchange 3.1. The problem manifests itself when the snaps have been performed and the verification process starts. The verification process (using eseutil) mounts a virtual drive where the verification takes place for each database. Once the verification is complete and the virtual drive dismounts, we then have a long wait by which time the dismount fails and the entire active cluster node fails over. This then causes a failed backup. Has anyone ever seen this before? Thanks -- NV
When SnapManageger for Exchange does a backup, it preserves the state of the logs by copying them to a subdirectorry of the snapinfo directory. The metadata for for the snapshot is also sored there for each snapshot. On verification, the snapinfo directory is mounted as a drive letter and eseutil is run. I can think of a few things that could go wrong with the process, primarially space on the LUN that hosts the snapinfo directory, however this is really something you should escallate through netapp product support. "NV" wrote in message news:0E79DF02-0984-4A56-9A71-AC4AAC8124B0@microsoft.com... > Hi: > > We have an issue with our snapshot backups in that we have a 2-node > Exchange > 2003 cluster that gets a snapshot of its databases using Snap Manager for > Exchange 3.1. The problem manifests itself when the snaps have been > performed > and the verification process starts. The verification process (using > eseutil) > mounts a virtual drive where the verification takes place for each > database. > Once the verification is complete and the virtual drive dismounts, we then > have a long wait by which time the dismount fails and the entire active > cluster node fails over. This then causes a failed backup. > > Has anyone ever seen this before? > > Thanks > > -- > NV
