ONTAP Discussions

SME error 0xc00402d8

oweinmann
13,444 Views

Hi,

we get this error when running verification of a Exchange 2010 database. The knowledge base mentions that this error is triggered when using the wrong verification server. This we have already verified. It is using the correct verification server. Any ideas?

Regards,

Oliver

20 REPLIES 20

arjunan
13,324 Views

is exchange2010 installed on cluster ?

oweinmann
13,324 Views

No, it is a standalone exchange server just used for archive mailboxes and public folders.

pmalar
13,324 Views

Hi,

You may get this error if Snapdrive is not able to reach out the LUN on destination filer and mount a snapshot.

Please send us the complete log details to identify the issue.

Regards,

Malar.

lmeyer_vega
13,324 Views

Hi

because Oliver is out of Office I'll answer to our SME issue.

Here you'll have the complete log:

--------------------------------

[20:30:21.740]  Database Backup job [JobID=1267] has report file : C:\Program Files\NetApp\SnapManager for Exchange\Report\Backup [ExServ06]\08-21-2011_20.30.18.txt.

[20:30:21.756]  Starting backup from server...

[20:30:21.756]  ***BACKUP JOB DESCRIPTION

[20:30:21.756]  Backup Server: ExServ06

[20:30:21.756]  Backup Storage Group/Database #1: Archive-MBX-DB-001

[20:30:21.756]  Backup Storage Group/Database #2: Archive-MBX-DB-002

[20:30:21.756]  Backup Storage Group/Database #3: Archive-MBX-DB-003

[20:30:21.756]  Backup Storage Group/Database #4: PF-DB-001

[20:30:21.756]  Archive backup to SnapVault secondary: No

[20:30:21.756]  Archive additional backup (copy based) to SnapVault secondary on remote CCR/DAG nodes if available: No

[20:30:21.756]  Backup Management Group: Daily

[20:30:21.756]  Backup will use the non unique naming convention.

[20:30:21.756]  Backup transaction logs which will be truncated by Exchange: Yes

[20:30:21.756]  The oldest snapshot in excess of 8 will be deleted.

[20:30:21.756]  The latest 0 snapshots will retain up-to-the-minute restore capability.

[20:30:21.756]  Setting up database primary backup type: Full Backup...

[20:30:21.756]  The snapshot will be verified after backup.

[20:30:21.756]  The verification will be run on computer ExServ06.

[20:30:21.756]  Verification mount point directory: C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint.

[20:30:21.756]  Use drive letter if available during mounting snapshot: No.

[20:30:21.756]  Verification throttling is not enabled or supported.

[20:30:21.756]  The backed up transaction logs will be verified.

[20:30:21.756]  Run Command after operation: No

[20:30:21.756]  No SnapMirror update after operation.

[20:30:21.756]  Job Management is enabled : YES

[20:30:21.756]  Backup Time Stamp: 08-21-2011_20.30.18

[20:30:21.771]  ***SNAPMANAGER BACKUP JOB FOR EXCHANGE SERVER [ExServ06 - 14.1.218.15] STARTED AT: [08-21-2011_20.30.21]

[20:30:21.771]  Getting current backup groups...

[20:30:21.818]  Getting backup groups based on storage system volume layout...

[20:30:21.834]  ***SUBJOB #1: BACKUP OF STORAGE GROUPS/DATABASES

[20:30:21.881]  ***SNAPMANAGER BACKUP SUBJOB STARTED AT: [08-21-2011_20.30.21]

[20:30:21.928]  Querying Exchange information...

[20:30:21.928]  Retrieving LUN information...

[20:30:21.943]  Storage group/Database [Archive-MBX-DB-001] SnapInfo directory located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.943]  Storage group/Database [Archive-MBX-DB-002] SnapInfo directory located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.943]  Storage group/Database [Archive-MBX-DB-003] SnapInfo directory located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.943]  Storage group/Database [PF-DB-001] SnapInfo directory located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.943]  Exchange Server [14.1.218.15]

[20:30:21.959]  CHECK SNAPMANAGER LICENSE ON LUN.

[20:30:21.959]  Querying LUN for storage group/database: Archive-MBX-DB-001...

[20:30:21.959]  Querying LUN for storage group/database: Archive-MBX-DB-002...

[20:30:21.959]  Querying LUN for storage group/database: Archive-MBX-DB-003...

[20:30:21.959]  Querying LUN for storage group/database: PF-DB-001...

[20:30:21.959]  SnapInfo directory ([Archive-MBX-DB-001]) located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.959]  SnapInfo directory ([Archive-MBX-DB-002]) located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.959]  SnapInfo directory ([Archive-MBX-DB-003]) located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.959]  SnapInfo directory ([PF-DB-001]) located at: [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06]

[20:30:21.974]  RENAME MOST RECENT SNAPINFO BEFORE NEW BACKUP : Archive-MBX-DB-001 - [#1]

[20:30:21.974]  Storage group/Database SnapInfo directory located at:

[20:30:21.974]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001

[20:30:22.021]  Rename recent SnapInfo folder from and to:

[20:30:22.021]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\ExServ06__recent

[20:30:22.021]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\08-20-2011_20.30.07__Daily

[20:30:22.021]  RENAME MOST RECENT SNAPINFO BEFORE NEW BACKUP : Archive-MBX-DB-002 - [#2]

[20:30:22.021]  Storage group/Database SnapInfo directory located at:

[20:30:22.021]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002

[20:30:22.037]  Rename recent SnapInfo folder from and to:

[20:30:22.037]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\ExServ06__recent

[20:30:22.037]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\08-20-2011_20.30.07__Daily

[20:30:22.037]  RENAME MOST RECENT SNAPINFO BEFORE NEW BACKUP : Archive-MBX-DB-003 - [#3]

[20:30:22.037]  Storage group/Database SnapInfo directory located at:

[20:30:22.037]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003

[20:30:22.053]  Rename recent SnapInfo folder from and to:

[20:30:22.053]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\ExServ06__recent

[20:30:22.053]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\08-20-2011_20.30.07__Daily

[20:30:22.053]  RENAME MOST RECENT SNAPINFO BEFORE NEW BACKUP : PF-DB-001 - [#4]

[20:30:22.053]  Storage group/Database SnapInfo directory located at:

[20:30:22.053]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001

[20:30:22.068]  Rename recent SnapInfo folder from and to:

[20:30:22.068]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\ExServ06__recent

[20:30:22.068]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\08-20-2011_20.30.07__Daily

[20:30:22.084]  RENAME MOST RECENT SNAPSHOT

[20:30:28.943]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-001\ from exchsnap__ExServ06__recent

[20:30:28.943]  To exchsnap__ExServ06_08-20-2011_20.30.07__daily

[20:30:29.709]  Rename snapshot successfully completed.

[20:30:29.709]  Rename Snapshot for LUN E:\Mountpoints\Logs\ from exchsnap__ExServ06__recent

[20:30:29.709]  To exchsnap__ExServ06_08-20-2011_20.30.07__daily

[20:30:30.084]  Rename snapshot successfully completed.

[20:30:30.084]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-002\ from exchsnap__ExServ06__recent

[20:30:30.084]  To exchsnap__ExServ06_08-20-2011_20.30.07__daily

[20:30:30.459]  Rename snapshot successfully completed.

[20:30:30.459]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-003\ from exchsnap__ExServ06__recent

[20:30:30.459]  To exchsnap__ExServ06_08-20-2011_20.30.07__daily

[20:30:30.959]  Rename snapshot successfully completed.

[20:30:30.959]  Rename Snapshot for LUN E:\Mountpoints\PF-DB-001\ from exchsnap__ExServ06__recent

[20:30:30.959]  To exchsnap__ExServ06_08-20-2011_20.30.07__daily

[20:30:31.318]  Rename snapshot successfully completed.

[20:30:31.334]  CREATE NEW RECENT SNAPINFO DIRECTORY : Archive-MBX-DB-001 - [#1]

[20:30:31.334]  Storage group/Database [Archive-MBX-DB-001] SnapInfo directory located at:

[20:30:31.334]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001

[20:30:31.334]  SnapInfo File Name:

[20:30:31.334]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\ExServ06__recent\SnapInfo__08-21-2011_20.30.18.sme

[20:30:31.334]  CREATE NEW RECENT SNAPINFO DIRECTORY : Archive-MBX-DB-002 - [#2]

[20:30:31.334]  Storage group/Database [Archive-MBX-DB-002] SnapInfo directory located at:

[20:30:31.334]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002

[20:30:31.350]  SnapInfo File Name:

[20:30:31.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\ExServ06__recent\SnapInfo__08-21-2011_20.30.18.sme

[20:30:31.350]  CREATE NEW RECENT SNAPINFO DIRECTORY : Archive-MBX-DB-003 - [#3]

[20:30:31.350]  Storage group/Database [Archive-MBX-DB-003] SnapInfo directory located at:

[20:30:31.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003

[20:30:31.350]  SnapInfo File Name:

[20:30:31.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\ExServ06__recent\SnapInfo__08-21-2011_20.30.18.sme

[20:30:31.350]  CREATE NEW RECENT SNAPINFO DIRECTORY : PF-DB-001 - [#4]

[20:30:31.350]  Storage group/Database [PF-DB-001] SnapInfo directory located at:

[20:30:31.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001

[20:30:31.350]  SnapInfo File Name:

[20:30:31.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\ExServ06__recent\SnapInfo__08-21-2011_20.30.18.sme

[20:30:31.350]  ***STARTING VSS ONLINE BACKUP PROCESS

[20:30:31.365]  Querying Exchange information...

[20:30:31.365]  Querying Exchange information...

[20:30:31.365]  SNAPSHOT DATABASE

[20:30:31.365]  Snapshot Name: exchsnap__ExServ06__recent

[20:30:31.396]  Getting Storage Group/Database Circular Logging Property: Archive-MBX-DB-001

[20:30:31.584]  [PowerShell Cmdlet]: get-storagegroup -identity "ExServ06\Archive-MBX-DB-001"

[20:30:31.912]  Getting Storage Group/Database Circular Logging Property: Archive-MBX-DB-002

[20:30:32.178]  [PowerShell Cmdlet]: get-storagegroup -identity "ExServ06\Archive-MBX-DB-002"

[20:30:32.178]  Getting Storage Group/Database Circular Logging Property: Archive-MBX-DB-003

[20:30:32.334]  [PowerShell Cmdlet]: get-storagegroup -identity "ExServ06\Archive-MBX-DB-003"

[20:30:32.334]  Getting Storage Group/Database Circular Logging Property: PF-DB-001

[20:30:32.490]  [PowerShell Cmdlet]: get-storagegroup -identity "ExServ06\PF-DB-001"

[20:30:32.521]  Exchange Store Writer instance will be used for the backup.

[20:30:32.537]  Backup Type is set to Full Backup.

[20:30:32.537]  ----------------- Initializing ---------------------

[20:30:32.537]  Creating backup components object...

[20:30:32.537]  Backup components object created.

[20:30:32.537]  Initializing the backup components object for backup...

[20:30:32.537]  Setting up backup context...

[20:30:32.537]  Setting up database backup type: Full Backup...

[20:30:32.537]  Backup components object initialized for backup operations.

[20:30:32.584]  ---------- Gathering writer metadata ---------------

[20:30:32.584]  Starting asynchronous GatherWriterMetadata. Please wait...

[20:30:33.600]  Operation pending, please wait...(1)

[20:30:38.600]  Operation pending, please wait...(2)

[20:30:43.600]  Operation pending, please wait...(3)

[20:30:48.600]  Operation pending, please wait...(4)

[20:30:53.600]  Operation pending, please wait...(5)

[20:30:58.600]  Operation pending, please wait...(6)

[20:31:00.600]  Asynchronous GatherWriterMetadata finished.

[20:31:00.600]  Getting the list of Writer Metadata Documents provided to VSS...

[20:31:00.600]  Number of writers that responded: 12.

[20:31:00.600]  Starting snapshot set...

[20:31:00.693]  Querying extended VSS backup components interface...

[20:31:00.693]  Identifying Exchange VSS writer...

[20:31:00.803]  Exchange writer instance [Exchange Information Store] identified.

[20:31:00.803]  Microsoft Exchange Writer identified.

[20:31:00.803]  *** WriterName = Microsoft Exchange Writer

WriterId   = {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}

InstanceId = {15a65890-7814-4aad-8723-b825c0957ec8}

UsageType  = 3 (UserData)

SourceType = 1 (TransactionDb)

[20:31:01.303]      Component 0, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06

        Name        = b37992b9-4be0-48be-8488-ee6e84ae9d41

        Caption     = Archive-MBX-DB-001

[20:31:01.303]          RestoreMetadata        = yes

        NotifyOnBackupComplete = yes

        Selectable             = yes

[20:31:01.318]  Component [Archive-MBX-DB-001] was added to the backup.

[20:31:01.318]      - b37992b9-4be0-48be-8488-ee6e84ae9d41

[20:31:01.662]      Component 1, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\b37992b9-4be0-48be-8488-ee6e84ae9d41

        Name        = File

        Caption     = File

[20:31:01.678]          FileGroupFile

          Path = E:\Mountpoints\Archive-MBX-DB-001

          Filespec = Archive-MBX-DB-001.edb

[20:31:01.975]      Component 2, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\b37992b9-4be0-48be-8488-ee6e84ae9d41

        Name        = Logs

        Caption     = Logs

[20:31:02.287]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-001\

          Filespec = E00*.log

[20:31:02.397]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-001\

          Filespec = E00.chk

[20:31:03.662]  Validating database paths from Exchange writer for storage group/database [Archive-MBX-DB-001]...

[20:31:03.693]      Component 0, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06

        Name        = de0a3422-7a59-4590-a1b2-76a6ae34f86e

        Caption     = Archive-MBX-DB-002

[20:31:03.693]          RestoreMetadata        = yes

        NotifyOnBackupComplete = yes

        Selectable             = yes

[20:31:03.693]  Component [Archive-MBX-DB-002] was added to the backup.

[20:31:03.693]      - de0a3422-7a59-4590-a1b2-76a6ae34f86e

[20:31:03.803]      Component 1, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\de0a3422-7a59-4590-a1b2-76a6ae34f86e

        Name        = File

        Caption     = File

[20:31:03.975]          FileGroupFile

          Path = E:\Mountpoints\Archive-MBX-DB-002

          Filespec = Archive-MBX-DB-002.edb

[20:31:03.990]      Component 2, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\de0a3422-7a59-4590-a1b2-76a6ae34f86e

        Name        = Logs

        Caption     = Logs

[20:31:04.350]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-002\

          Filespec = E02*.log

[20:31:04.443]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-002\

          Filespec = E02.chk

[20:31:05.334]  Validating database paths from Exchange writer for storage group/database [Archive-MBX-DB-002]...

[20:31:05.334]      Component 0, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06

        Name        = 753dbd09-6932-4c44-8569-e9f6c92f1075

        Caption     = Archive-MBX-DB-003

[20:31:05.334]          RestoreMetadata        = yes

        NotifyOnBackupComplete = yes

        Selectable             = yes

[20:31:05.334]  Component [Archive-MBX-DB-003] was added to the backup.

[20:31:05.334]      - 753dbd09-6932-4c44-8569-e9f6c92f1075

[20:31:05.693]      Component 1, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\753dbd09-6932-4c44-8569-e9f6c92f1075

        Name        = File

        Caption     = File

[20:31:05.850]          FileGroupFile

          Path = E:\Mountpoints\Archive-MBX-DB-003

          Filespec = Archive-MBX-DB-003.edb

[20:31:05.943]      Component 2, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\753dbd09-6932-4c44-8569-e9f6c92f1075

        Name        = Logs

        Caption     = Logs

[20:31:06.147]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-003\

          Filespec = E03*.log

[20:31:06.428]          FileGroupFile

          Path = E:\Mountpoints\Logs\Archive-MBX-DB-003\

          Filespec = E03.chk

[20:31:06.709]  Validating database paths from Exchange writer for storage group/database [Archive-MBX-DB-003]...

[20:31:06.787]      Component 0, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06

        Name        = 807721cb-ff29-400c-b3f1-3341e3626892

        Caption     = PF-DB-001

[20:31:06.787]          RestoreMetadata        = yes

        NotifyOnBackupComplete = yes

        Selectable             = yes

[20:31:06.787]  Component [PF-DB-001] was added to the backup.

[20:31:06.787]      - 807721cb-ff29-400c-b3f1-3341e3626892

[20:31:06.865]      Component 1, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\807721cb-ff29-400c-b3f1-3341e3626892

        Name        = File

        Caption     = File

[20:31:06.928]          FileGroupFile

          Path = E:\Mountpoints\PF-DB-001

          Filespec = PF-DB-001.edb

[20:31:06.975]      Component 2, type = 2 (FileGroup)

        LogicalPath = Microsoft Exchange Server\Microsoft Information Store\ExServ06\807721cb-ff29-400c-b3f1-3341e3626892

        Name        = Logs

        Caption     = Logs

[20:31:07.006]          FileGroupFile

          Path = E:\Mountpoints\Logs\PF-DB-001\

          Filespec = E01*.log

[20:31:07.053]          FileGroupFile

          Path = E:\Mountpoints\Logs\PF-DB-001\

          Filespec = E01.chk

[20:31:07.272]  Validating database paths from Exchange writer for storage group/database [PF-DB-001]...

[20:31:07.272]      Restore method = 2 (RestoreIfCanReplace)

    Service        = (null)

    User Procedure = (null)

    WriterRestore  = 3 (RestoreAlways)

    RebootRequired = no

[20:31:08.131]  Querying checkpoint file for log generation before shadow copy...

[20:31:08.131]  Getting log generation from checkpoint file: Archive-MBX-DB-001...

[20:31:08.209]  Current checkpoint of [Archive-MBX-DB-001]: 0x00006EF1

[20:31:08.209]  Getting log generation from checkpoint file: Archive-MBX-DB-002...

[20:31:08.365]  Current checkpoint of [Archive-MBX-DB-002]: 0x00000347

[20:31:08.365]  Getting log generation from checkpoint file: Archive-MBX-DB-003...

[20:31:08.459]  Current checkpoint of [Archive-MBX-DB-003]: 0x0000036F

[20:31:08.459]  Getting log generation from checkpoint file: PF-DB-001...

[20:31:08.584]  Current checkpoint of [PF-DB-001]: 0x00001948

[20:31:08.600]  ---------- Starting backup/snapshot ----------------

[20:31:08.600]  Adding volumes to the snapshot set:

[20:31:08.600]  Adding volume containing E:\Mountpoints\Archive-MBX-DB-001\ ...

[20:31:10.006]  Successfully add volumes to snapshot set.

[20:31:10.006]  Adding volume containing E:\Mountpoints\Logs\ ...

[20:31:10.147]  Successfully add volumes to snapshot set.

[20:31:10.147]  Adding volume containing E:\Mountpoints\Archive-MBX-DB-002\ ...

[20:31:10.319]  Successfully add volumes to snapshot set.

[20:31:10.319]  Adding volume containing E:\Mountpoints\Archive-MBX-DB-003\ ...

[20:31:10.459]  Successfully add volumes to snapshot set.

[20:31:10.459]  Adding volume containing E:\Mountpoints\PF-DB-001\ ...

[20:31:10.600]  Successfully add volumes to snapshot set.

[20:31:10.600]  ------------ Creating the snapshot -----------------

[20:31:10.600]  Starting asynchronous PrepareForBackup. Please wait...

[20:31:11.600]  Asynchronous PrepareForBackup finished.

[20:31:11.662]  Status after PrepareForBackup (12 writers)

[20:31:11.662]  Status for writer Task Scheduler Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer VSS Metadata Store Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer Performance Counters Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer System Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer IIS Config Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer ASR Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer Shadow Copy Optimization Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer Registry Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer COM+ REGDB Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer Microsoft Exchange Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer IIS Metabase Writer: STABLE(0x00000000)

[20:31:11.662]  Status for writer WMI Writer: STABLE(0x00000000)

[20:31:11.662]  Starting asynchronous DoSnapshotSet. Please wait...

[20:31:12.709]  Operation pending, please wait...(1)

[20:31:17.740]  Operation pending, please wait...(2)

[20:31:20.740]  Asynchronous DoSnapshotSet finished.

[20:31:20.772]  Status after DoSnapshotSet (12 writers)

[20:31:20.772]  Status for writer Task Scheduler Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer VSS Metadata Store Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer Performance Counters Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer System Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer IIS Config Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer ASR Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer Shadow Copy Optimization Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer Registry Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer COM+ REGDB Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer Microsoft Exchange Writer: WAIT_FOR_BACKUP_COMPLETE(0x00000000)

[20:31:20.772]  Status for writer IIS Metabase Writer: STABLE(0x00000000)

[20:31:20.772]  Status for writer WMI Writer: STABLE(0x00000000)

[20:31:20.772]  Snapshot set created

[20:31:21.397]  ------------ Saving backup metadata ---------------

[20:31:21.490]  Backup instance id matches metadata instance id.

[20:31:21.490]  Backup metadata file was saved to E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\ExServ06__recent\Vss__08-21-2011_20.30.18_{15A65890-7814-4AAD-8723-B825C0957EC8}.xml.

[20:31:21.506]  Copying backup document to:

[20:31:21.506]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\ExServ06__recent\Vss__08-21-2011_20.30.18_{15A65890-7814-4AAD-8723-B825C0957EC8}.xml

[20:31:21.522]  Copying backup document to:

[20:31:21.522]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\ExServ06__recent\Vss__08-21-2011_20.30.18_{15A65890-7814-4AAD-8723-B825C0957EC8}.xml

[20:31:21.537]  Copying backup document to:

[20:31:21.537]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\ExServ06__recent\Vss__08-21-2011_20.30.18_{15A65890-7814-4AAD-8723-B825C0957EC8}.xml

[20:31:21.537]  Getting log generation from checkpoint file: Archive-MBX-DB-001...

[20:31:21.647]  Current checkpoint of [Archive-MBX-DB-001]: 0x00006EF1

[20:31:21.647]  Getting log generation from checkpoint file: Archive-MBX-DB-002...

[20:31:21.756]  Current checkpoint of [Archive-MBX-DB-002]: 0x00000347

[20:31:21.756]  Getting log generation from checkpoint file: Archive-MBX-DB-003...

[20:31:21.865]  Current checkpoint of [Archive-MBX-DB-003]: 0x0000036F

[20:31:21.865]  Getting log generation from checkpoint file: PF-DB-001...

[20:31:21.959]  Current checkpoint of [PF-DB-001]: 0x00001948

[20:31:21.975]  Getting log generation from live log directory: Archive-MBX-DB-001...

[20:31:21.975]  The highest numbered log generation of [Archive-MBX-DB-001] from live file system: 0x00006EF9.

[20:31:21.975]  Getting log generation from live log directory: Archive-MBX-DB-002...

[20:31:21.975]  The highest numbered log generation of [Archive-MBX-DB-002] from live file system: 0x00000348.

[20:31:21.975]  Getting log generation from live log directory: Archive-MBX-DB-003...

[20:31:21.975]  The highest numbered log generation of [Archive-MBX-DB-003] from live file system: 0x00000370.

[20:31:21.975]  Getting log generation from live log directory: PF-DB-001...

[20:31:21.975]  The highest numbered log generation of [PF-DB-001] from live file system: 0x0000194A.

[20:31:23.553]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-001\ from {bea539b3-6c17-43f1-8fda-2c227396d731}

[20:31:23.553]  To exchsnap__ExServ06__recent

[20:31:23.990]  Rename snapshot successfully completed.

[20:31:23.990]  Rename Snapshot for LUN E:\Mountpoints\Logs\ from {bea539b3-6c17-43f1-8fda-2c227396d731}

[20:31:23.990]  To exchsnap__ExServ06__recent

[20:31:24.397]  Rename snapshot successfully completed.

[20:31:24.397]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-002\ from {bea539b3-6c17-43f1-8fda-2c227396d731}

[20:31:24.397]  To exchsnap__ExServ06__recent

[20:31:24.787]  Rename snapshot successfully completed.

[20:31:24.787]  Rename Snapshot for LUN E:\Mountpoints\Archive-MBX-DB-003\ from {bea539b3-6c17-43f1-8fda-2c227396d731}

[20:31:24.787]  To exchsnap__ExServ06__recent

[20:31:25.131]  Rename snapshot successfully completed.

[20:31:25.131]  Rename Snapshot for LUN E:\Mountpoints\PF-DB-001\ from {bea539b3-6c17-43f1-8fda-2c227396d731}

[20:31:25.131]  To exchsnap__ExServ06__recent

[20:31:25.537]  Rename snapshot successfully completed.

[20:31:25.553]  ***BACKUP VERIFICATION: Archive-MBX-DB-001

[20:31:25.553]  Start to verify the database in snapshot...

[20:31:25.631]  FullBackup job with JobID=1267 invoke Job Management for local integrity verification

[20:31:25.678]  SnapManager ExServ06 concurrent job status at 21.08.2011 20:31:25 :

[20:31:25.678]  =================================================================================================

[20:31:25.678]  SnapManager is creating full backup with JobID=1267.

[20:31:25.678]  SnapManager is running 0 backup integrity verification jobs.

[20:31:25.678]  This BackupVerification job with JobID=1268 is waiting in the queue at position 0.

[20:31:25.678]  =================================================================================================

[20:31:25.725]  BackupVerification Job of JobID 1268 starts to run on server ExServ06.

[20:31:25.756]  The destination volume of the source Logical Disk E:\Mountpoints\Archive-MBX-DB-001\ FlexClone State is Success and SnapMirror State is Unknown.

[20:31:32.772]  Mounting Snapshot [exchsnap__ExServ06__recent] for LUN E:\Mountpoints\Archive-MBX-DB-001\ created from Computer ExServ06

[20:31:32.772]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint]

[20:31:34.303]  Snapshot will be mounted on subdirectory [MPDisk001]

[20:31:49.913]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

(SnapDrive Error Code: 0xc00402d8)

[20:31:49.913]  SnapDrive failed to mount the snapshot.

[20:31:49.928]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:31:49.928]  Unable to mount snapshot, abort verification.

[20:31:49.928]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:31:49.928]  BackupVerification Job of JobID=1268 is finished with status Failed.

[20:31:49.944]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:31:49.959]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:31:49.959]  Setting operation result to registry...

[20:31:50.038]  ***BACKUP VERIFICATION STATUS: Archive-MBX-DB-001

[20:31:50.038]  Failed to verify physical integrity of the databases.

[20:31:50.038]  ***BACKUP VERIFICATION: Archive-MBX-DB-002

[20:31:50.038]  Start to verify the database in snapshot...

[20:31:50.038]  FullBackup job with JobID=1267 invoke Job Management for local integrity verification

[20:31:50.038]  SnapManager ExServ06 concurrent job status at 21.08.2011 20:31:50 :

[20:31:50.038]  =================================================================================================

[20:31:50.038]  SnapManager is creating full backup with JobID=1267.

[20:31:50.038]  SnapManager is running 0 backup integrity verification jobs.

[20:31:50.038]  This BackupVerification job with JobID=1269 is waiting in the queue at position 0.

[20:31:50.038]  =================================================================================================

[20:31:50.053]  BackupVerification Job of JobID 1269 starts to run on server ExServ06.

[20:31:50.053]  The destination volume of the source Logical Disk E:\Mountpoints\Archive-MBX-DB-002\ FlexClone State is Success and SnapMirror State is Unknown.

[20:31:57.053]  Mounting Snapshot [exchsnap__ExServ06__recent] for LUN E:\Mountpoints\Archive-MBX-DB-002\ created from Computer ExServ06

[20:31:57.053]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint]

[20:31:58.584]  Snapshot will be mounted on subdirectory [MPDisk001]

[20:32:13.991]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

(SnapDrive Error Code: 0xc00402d8)

[20:32:13.991]  SnapDrive failed to mount the snapshot.

[20:32:13.991]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:13.991]  Unable to mount snapshot, abort verification.

[20:32:13.991]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:13.991]  BackupVerification Job of JobID=1269 is finished with status Failed.

[20:32:13.991]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:13.991]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:13.991]  Setting operation result to registry...

[20:32:14.053]  ***BACKUP VERIFICATION STATUS: Archive-MBX-DB-002

[20:32:14.053]  Failed to verify physical integrity of the databases.

[20:32:14.053]  ***BACKUP VERIFICATION: Archive-MBX-DB-003

[20:32:14.053]  Start to verify the database in snapshot...

[20:32:14.053]  FullBackup job with JobID=1267 invoke Job Management for local integrity verification

[20:32:14.069]  SnapManager ExServ06 concurrent job status at 21.08.2011 20:32:14 :

[20:32:14.069]  =================================================================================================

[20:32:14.069]  SnapManager is creating full backup with JobID=1267.

[20:32:14.069]  SnapManager is running 0 backup integrity verification jobs.

[20:32:14.069]  This BackupVerification job with JobID=1270 is waiting in the queue at position 0.

[20:32:14.069]  =================================================================================================

[20:32:14.069]  BackupVerification Job of JobID 1270 starts to run on server ExServ06.

[20:32:14.069]  The destination volume of the source Logical Disk E:\Mountpoints\Archive-MBX-DB-003\ FlexClone State is Success and SnapMirror State is Unknown.

[20:32:21.069]  Mounting Snapshot [exchsnap__ExServ06__recent] for LUN E:\Mountpoints\Archive-MBX-DB-003\ created from Computer ExServ06

[20:32:21.069]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint]

[20:32:22.600]  Snapshot will be mounted on subdirectory [MPDisk001]

[20:32:37.600]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

(SnapDrive Error Code: 0xc00402d8)

[20:32:37.600]  SnapDrive failed to mount the snapshot.

[20:32:37.600]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:37.600]  Unable to mount snapshot, abort verification.

[20:32:37.600]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:37.600]  BackupVerification Job of JobID=1270 is finished with status Failed.

[20:32:37.600]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:37.600]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:32:37.600]  Setting operation result to registry...

[20:32:37.663]  ***BACKUP VERIFICATION STATUS: Archive-MBX-DB-003

[20:32:37.663]  Failed to verify physical integrity of the databases.

[20:32:37.663]  ***BACKUP VERIFICATION: PF-DB-001

[20:32:37.663]  Start to verify the database in snapshot...

[20:32:37.663]  FullBackup job with JobID=1267 invoke Job Management for local integrity verification

[20:32:37.678]  SnapManager ExServ06 concurrent job status at 21.08.2011 20:32:37 :

[20:32:37.678]  =================================================================================================

[20:32:37.678]  SnapManager is creating full backup with JobID=1267.

[20:32:37.678]  SnapManager is running 0 backup integrity verification jobs.

[20:32:37.678]  This BackupVerification job with JobID=1271 is waiting in the queue at position 0.

[20:32:37.678]  =================================================================================================

[20:32:37.678]  BackupVerification Job of JobID 1271 starts to run on server ExServ06.

[20:32:37.678]  The destination volume of the source Logical Disk E:\Mountpoints\PF-DB-001\ FlexClone State is Success and SnapMirror State is Unknown.

[20:32:44.679]  Mounting Snapshot [exchsnap__ExServ06__recent] for LUN E:\Mountpoints\PF-DB-001\ created from Computer ExServ06

[20:32:44.679]  Mount point directory [C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint]

[20:32:46.210]  Snapshot will be mounted on subdirectory [MPDisk001]

[20:33:01.366]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

(SnapDrive Error Code: 0xc00402d8)

[20:33:01.366]  SnapDrive failed to mount the snapshot.

[20:33:01.366]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:33:01.366]  Unable to mount snapshot, abort verification.

[20:33:01.366]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:33:01.366]  BackupVerification Job of JobID=1271 is finished with status Failed.

[20:33:01.366]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:33:01.366]  [SnapDrive Error]:The specified initiator 21:00:00:1b:32:9a:90:29 is not connected to the target storage system DS-SAN-01.

[20:33:01.366]  Setting operation result to registry...

[20:33:01.429]  ***BACKUP VERIFICATION STATUS: PF-DB-001

[20:33:01.429]  Failed to verify physical integrity of the databases.

[20:33:01.460]  BACKING UP LOGS

[20:33:01.460]  The highest log generation to be backed up for [Archive-MBX-DB-001]: 0x00006EF9, the lowest is 0x00006EF1

[20:33:01.460]  Starting the backup of log files of [Archive-MBX-DB-001]...

[20:33:01.460]  Log files will be backed up from:

[20:33:01.460]  E:\Mountpoints\Logs\Archive-MBX-DB-001\

[20:33:01.460]  Log files will be backed up to:

[20:33:01.460]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\ExServ06__recent\Logs

[20:33:01.663]  The last FRP backed log of [Archive-MBX-DB-001]: [E0000006EE2.log]

[20:33:01.663]  Archiving log file: E0000006EF9.log

[20:33:01.663]  Archiving log file: E0000006EF8.log

[20:33:01.663]  Archiving log file: E0000006EF7.log

[20:33:01.663]  Archiving log file: E0000006EF6.log

[20:33:01.663]  Archiving log file: E0000006EF5.log

[20:33:01.663]  Archiving log file: E0000006EF4.log

[20:33:01.663]  Archiving log file: E0000006EF3.log

[20:33:01.663]  Archiving log file: E0000006EF2.log

[20:33:01.663]  Archiving log file: E0000006EF1.log

[20:33:01.663]  Archiving log file: E0000006EF0.log

[20:33:01.663]  Archiving log file: E0000006EEF.log

[20:33:01.663]  Archiving log file: E0000006EEE.log

[20:33:01.663]  Archiving log file: E0000006EED.log

[20:33:01.663]  Archiving log file: E0000006EEC.log

[20:33:01.663]  Archiving log file: E0000006EEB.log

[20:33:01.663]  Archiving log file: E0000006EEA.log

[20:33:01.663]  Archiving log file: E0000006EE9.log

[20:33:01.663]  Archiving log file: E0000006EE8.log

[20:33:01.679]  Archiving log file: E0000006EE7.log

[20:33:01.679]  Archiving log file: E0000006EE6.log

[20:33:01.679]  Archiving log file: E0000006EE5.log

[20:33:01.679]  Archiving log file: E0000006EE4.log

[20:33:01.679]  Archiving log file: E0000006EE3.log

[20:33:01.679]  Do not backup transaction log files that have already been backed up in previous FRP backup.

[20:33:01.679]  Total log file hard links created: 23

[20:33:01.757]  Updated E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\SG__Archive-MBX-DB-001_FRP.xml with log [E0000006EF9.log]

[20:33:01.757]  The highest log generation to be backed up for [Archive-MBX-DB-002]: 0x00000348, the lowest is 0x00000347

[20:33:01.772]  Starting the backup of log files of [Archive-MBX-DB-002]...

[20:33:01.772]  Log files will be backed up from:

[20:33:01.772]  E:\Mountpoints\Logs\Archive-MBX-DB-002\

[20:33:01.772]  Log files will be backed up to:

[20:33:01.772]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\ExServ06__recent\Logs

[20:33:01.804]  The last FRP backed log of [Archive-MBX-DB-002]: [E0200000343.log]

[20:33:01.804]  Archiving log file: E0200000348.log

[20:33:01.804]  Archiving log file: E0200000347.log

[20:33:01.804]  Archiving log file: E0200000346.log

[20:33:01.804]  Archiving log file: E0200000345.log

[20:33:01.804]  Archiving log file: E0200000344.log

[20:33:01.804]  Do not backup transaction log files that have already been backed up in previous FRP backup.

[20:33:01.804]  Total log file hard links created: 5

[20:33:01.882]  Updated E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\SG__Archive-MBX-DB-002_FRP.xml with log [E0200000348.log]

[20:33:01.882]  The highest log generation to be backed up for [Archive-MBX-DB-003]: 0x00000370, the lowest is 0x0000036F

[20:33:01.882]  Starting the backup of log files of [Archive-MBX-DB-003]...

[20:33:01.882]  Log files will be backed up from:

[20:33:01.882]  E:\Mountpoints\Logs\Archive-MBX-DB-003\

[20:33:01.882]  Log files will be backed up to:

[20:33:01.882]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\ExServ06__recent\Logs

[20:33:01.913]  The last FRP backed log of [Archive-MBX-DB-003]: [E030000036B.log]

[20:33:01.913]  Archiving log file: E0300000370.log

[20:33:01.913]  Archiving log file: E030000036F.log

[20:33:01.913]  Archiving log file: E030000036E.log

[20:33:01.913]  Archiving log file: E030000036D.log

[20:33:01.913]  Archiving log file: E030000036C.log

[20:33:01.913]  Do not backup transaction log files that have already been backed up in previous FRP backup.

[20:33:01.913]  Total log file hard links created: 5

[20:33:01.975]  Updated E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\SG__Archive-MBX-DB-003_FRP.xml with log [E0300000370.log]

[20:33:01.975]  The highest log generation to be backed up for [PF-DB-001]: 0x0000194A, the lowest is 0x00001948

[20:33:01.975]  Starting the backup of log files of [PF-DB-001]...

[20:33:01.975]  Log files will be backed up from:

[20:33:01.975]  E:\Mountpoints\Logs\PF-DB-001\

[20:33:01.975]  Log files will be backed up to:

[20:33:01.975]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\ExServ06__recent\Logs

[20:33:02.007]  The last FRP backed log of [PF-DB-001]: [E0100001940.log]

[20:33:02.007]  Archiving log file: E010000194A.log

[20:33:02.007]  Archiving log file: E0100001949.log

[20:33:02.007]  Archiving log file: E0100001948.log

[20:33:02.007]  Archiving log file: E0100001947.log

[20:33:02.007]  Archiving log file: E0100001946.log

[20:33:02.022]  Archiving log file: E0100001945.log

[20:33:02.022]  Archiving log file: E0100001944.log

[20:33:02.022]  Archiving log file: E0100001943.log

[20:33:02.022]  Archiving log file: E0100001942.log

[20:33:02.022]  Archiving log file: E0100001941.log

[20:33:02.054]  Do not backup transaction log files that have already been backed up in previous FRP backup.

[20:33:02.054]  Total log file hard links created: 10

[20:33:02.100]  Updated E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\SG__PF-DB-001_FRP.xml with log [E010000194A.log]

[20:33:02.100]  Backup Verification Preparation:

[20:33:02.100]  Looking for FRP backup prior to [08-21-2011_20.30.18] under [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001]

[20:33:02.163]  There are no FRP backup prior to backup [ExServ06__recent]

[20:33:02.163]  Backup Verification Preparation:

[20:33:02.163]  Looking for FRP backup prior to [08-21-2011_20.30.18] under [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002]

[20:33:02.194]  There are no FRP backup prior to backup [ExServ06__recent]

[20:33:02.194]  Backup Verification Preparation:

[20:33:02.194]  Looking for FRP backup prior to [08-21-2011_20.30.18] under [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003]

[20:33:02.225]  There are no FRP backup prior to backup [ExServ06__recent]

[20:33:02.241]  Backup Verification Preparation:

[20:33:02.241]  Looking for FRP backup prior to [08-21-2011_20.30.18] under [E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001]

[20:33:02.272]  There are no FRP backup prior to backup [ExServ06__recent]

[20:33:02.272]  Skipping transaction log verification due to the failure of the database verification.

[20:33:02.304]  ------------ Completing backup phase ---------------

[20:33:02.304]  Setting backup completion state...

[20:33:02.304]  Setting [Archive-MBX-DB-001] backup failed because backup verification failed (component name: b37992b9-4be0-48be-8488-ee6e84ae9d41)...

[20:33:02.304]  WARNING: Transaction log files will NOT be truncated by Exchange writer.

[20:33:02.304]  Transaction log LUN can run out of disk space very soon since no log files are deleted.

[20:33:02.304]  Please check backup report to resolve backup verification failure issue as soon as possible.

[20:33:02.304]  Setting [Archive-MBX-DB-002] backup failed because backup verification failed (component name: de0a3422-7a59-4590-a1b2-76a6ae34f86e)...

[20:33:02.304]  WARNING: Transaction log files will NOT be truncated by Exchange writer.

[20:33:02.304]  Transaction log LUN can run out of disk space very soon since no log files are deleted.

[20:33:02.304]  Please check backup report to resolve backup verification failure issue as soon as possible.

[20:33:02.304]  Setting [Archive-MBX-DB-003] backup failed because backup verification failed (component name: 753dbd09-6932-4c44-8569-e9f6c92f1075)...

[20:33:02.304]  WARNING: Transaction log files will NOT be truncated by Exchange writer.

[20:33:02.304]  Transaction log LUN can run out of disk space very soon since no log files are deleted.

[20:33:02.304]  Please check backup report to resolve backup verification failure issue as soon as possible.

[20:33:02.304]  Setting [PF-DB-001] backup failed because backup verification failed (component name: 807721cb-ff29-400c-b3f1-3341e3626892)...

[20:33:02.304]  WARNING: Transaction log files will NOT be truncated by Exchange writer.

[20:33:02.304]  Transaction log LUN can run out of disk space very soon since no log files are deleted.

[20:33:02.304]  Please check backup report to resolve backup verification failure issue as soon as possible.

[20:33:02.304]  Starting asynchronous BackupComplete. Please wait...

[20:33:03.304]  Asynchronous BackupComplete finished.

[20:33:03.335]  Status after BackupComplete (12 writers)

[20:33:03.335]  Status for writer Task Scheduler Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer VSS Metadata Store Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer Performance Counters Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer ASR Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer IIS Metabase Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer Registry Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer Shadow Copy Optimization Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer Microsoft Exchange Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer COM+ REGDB Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer System Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer IIS Config Writer: STABLE(0x00000000)

[20:33:03.335]  Status for writer WMI Writer: STABLE(0x00000000)

[20:33:03.335]  Backup document saved successfully in

[20:33:03.335]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\ExServ06__recent\Vss__08-21-2011_20.30.18.xml

[20:33:03.335]  Copying backup document to:

[20:33:03.335]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\ExServ06__recent\Vss__08-21-2011_20.30.18.xml

[20:33:03.350]  Copying backup document to:

[20:33:03.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\ExServ06__recent\Vss__08-21-2011_20.30.18.xml

[20:33:03.350]  Copying backup document to:

[20:33:03.350]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\ExServ06__recent\Vss__08-21-2011_20.30.18.xml

[20:33:04.038]  Setting operation result to registry...

[20:33:04.038]  Retrieving Last Point-In-Time restored backup information ...

[20:33:04.038]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-001\SG__Archive-MBX-DB-001_PIT.xml doesn't exist.

[20:33:04.663]  Setting operation result to registry...

[20:33:04.663]  Retrieving Last Point-In-Time restored backup information ...

[20:33:04.663]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-002\SG__Archive-MBX-DB-002_PIT.xml doesn't exist.

[20:33:05.257]  Setting operation result to registry...

[20:33:05.257]  Retrieving Last Point-In-Time restored backup information ...

[20:33:05.257]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__Archive-MBX-DB-003\SG__Archive-MBX-DB-003_PIT.xml doesn't exist.

[20:33:05.851]  Setting operation result to registry...

[20:33:05.851]  Retrieving Last Point-In-Time restored backup information ...

[20:33:05.851]  E:\Mountpoints\Logs\sme_snapinfo\EXCH__ExServ06\SG__PF-DB-001\SG__PF-DB-001_PIT.xml doesn't exist.

[20:33:05.960]  ***BACKUP SNAPINFO DISK

[20:33:06.226]  UPDATE MOST RECENT LOG/SNAPINFO DRIVE SNAPSHOT NAME

[20:33:06.226]  Rename Snapshot for LUN E:\Mountpoints\Logs\ from eloginfo__ExServ06__recent

[20:33:06.226]  To eloginfo__ExServ06_08-20-2011_20.30.07__daily

[20:33:06.913]  Rename snapshot successfully completed.

[20:33:06.913]  SNAPSHOT LOG/SNAPINFO DRIVE

[20:33:06.913]  Creating Snapshot of LUN:

[20:33:06.913]  LUN [E:\Mountpoints\Logs\]

[20:33:06.913]  Snapshot Name: eloginfo__ExServ06__recent

[20:33:08.147]  Snapshot log/SnapInfo drive(s) successfully completed.

[20:33:08.179]  Failed to verify physical integrity of the databases or transaction logs.

[20:33:08.179]  Deletion of the oldest backup sets can not proceed. There is error when backuping this storage group/database.

[20:33:08.179]  Backup Result [hrBkInfo 0x0]: hr=0xc00402d8 bInfoShotOK=1, hrWarning=0x0

[20:33:08.179]  Failed to backup storage group/database set.

[20:33:08.179]  ***SNAPMANAGER BACKUP SUBJOB ENDED AT: [08-21-2011_20.33.08]

[20:33:08.194]  ***SUBJOB #1: END OF BACKUP

[20:33:08.210]  *****FULL BACKUP RESULT SUMMARY*****

[20:33:08.210]  Backup group set #1:

[20:33:08.210]  Backup SG/DB [Archive-MBX-DB-001]: Backup OK, verification failed

[20:33:08.210]  Backup SG/DB [Archive-MBX-DB-002]: Backup OK, verification failed

[20:33:08.210]  Backup SG/DB [Archive-MBX-DB-003]: Backup OK, verification failed

[20:33:08.210]  Backup SG/DB [PF-DB-001]: Backup OK, verification failed

[20:33:08.226]  *****BACKUP DETAIL SUMMARY*****

[20:33:08.226]  Backup group set #1:

[20:33:08.226]  Backup SG/DB [Archive-MBX-DB-001] Error: Failed to verify physical integrity of the databases.

[20:33:08.226]  Backup SG/DB [Archive-MBX-DB-002] Error: Failed to verify physical integrity of the databases.

[20:33:08.226]  Backup SG/DB [Archive-MBX-DB-003] Error: Failed to verify physical integrity of the databases.

[20:33:08.226]  Backup SG/DB [PF-DB-001] Error: Failed to verify physical integrity of the databases.

[20:33:08.226]  ***SNAPMANAGER BACKUP JOB ENDED AT: [08-21-2011_20.33.08]

[20:33:08.226]  Failed to backup storage groups/databases.

--------------

Regards

Lars

pmalar
13,325 Views

Hi Lars,

Please check the login status of your igroup for initiator 21:00:00:1b:32:9a:90:29. The status should be "Logged in".

If the status is not logged in and if you have any other initiator of the same host is in logged in state then snapdrive should try out mounting the LUNs through the other available initiator.

Please let us know your snapdrive version.

Regards,

Malar.

lmeyer_vega
13,325 Views

Hi Malar

you're right the initator 21:00:00:1b:32:9a:90:29 is in status logged in. And because it's a virtual machine on ESX the same problem occurs after changing the ESX host. The logged in initiator is not "connected to the target store".

The Snapdrive version is 6.3P1.

Regards

Lars

mh_sh_team
13,324 Views

You have some issue with the defined initiator connected to the system. It's either disconnected from the filer (physically or logically via zone in your san switch) or perhaps was replaced with some other hba and therefore the wwn is now different and should be reconfigured in the igroup on the filer.

lmeyer_vega
13,324 Views

Hi mh_sh_team

the initiator in question the one that is used by the system. Please see my answer to Malar.

We checked the physicall connections as well as the zones. Seems to be ok.

Regards

Lars

arjunan
13,324 Views

try to take backup only without verfication to see if the backup works fine, this is make sure the problem is only with the verification.

thanks, Prabu

lmeyer_vega
9,830 Views

Hello

Backup without verfiy works nearly fine:

*****FULL BACKUP RESULT SUMMARY*****

Backup group set #1:

Backup SG/DB [Archive-MBX-DB-001]: OK

Backup SG/DB [Archive-MBX-DB-002]: OK

Backup SG/DB [Archive-MBX-DB-003]: OK

Backup SG/DB [PF-DB-001]: OK

But I also get this:

LUN Manager Event Detail:

Computer Name: ExServ06

Event ID: 317

Type: Warning

Category: Generic event

Description: Failed to enumerate LUN.

Device path:'\\?\scsi#disk&ven_netapp&prod_lun#5&1982005&0&000600#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'

Storage path:'/vol/ExServ06_PFDB001/ExServ06_PFDB001.lun'

SCSI address:(2,0,6,0)

Error code:0xc00402fa

Error description:A LUN with device path \\?\scsi#disk&ven_netapp&prod_lun#5&1982005&0&000600#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}and SCSI address (2, 0, 6, 0) is exposed through an unsupported initiator.

Regards

Lars

arjunan
9,830 Views

then this might be problem with the verficaiton server, can you check if the verification server is been configured properly.

thanks, Prabu

lmeyer_vega
9,830 Views

Yes, the verification is configured to use the same server that does the backup.

Regards

Lars

arjunan
9,830 Views

what is the mount point directory used for mounting snapshots ? are you using th local disks for the same ???

thanks, Prabu

lmeyer_vega
9,830 Views

the verification mountpoint is standard:

C:\Program Files\NetApp\SnapManager for Exchange\SnapMgrMountPoint

The LUNs are mounted below e:\mountpoints.

Regards

Lars

pmalar
9,830 Views

Hi Lars,

I could find an existing burt related to the problem you are facing. Please send us your igroup status along with the ports details of the connected hosts and filers.

=======

BurtID:522400

Snapdrive for windows allows to connect to a LUN only if all the initiators in igroup can be connected to LUN.

If one initiator fails to connect and MPIO is not enabled, Snapdrive for Windows fails to connect to LUN instead

of trying to connect with other available initiators

=======

To verify if you are hitting the same issue, please enable MPIO and re-run the verification.

Please confirm if you are hitthing the above specified issue.

oweinmann
8,675 Views

Hi,

here is the igroup configuration. SME is installed on a virtual W2K8 Server R2.

viaRPC.21:00:00:1b:32:9a:42:de.GEDASVW06 (FCP):

        OS Type: vmware

        Member: 21:00:00:1b:32:9a:42:de (logged in on: vtic, 0c)

        ALUA: Yes

The VM is running on two clustered ESX servers:

fcp_gedaspe03 (FCP):

        OS Type: vmware

        Member: 21:00:00:1b:32:9a:90:29 (logged in on: vtic, 0c)

        Member: 21:01:00:1b:32:ba:90:29 (not logged in)

        ALUA: Yes

fcp_gedaspe04 (FCP):

        OS Type: vmware

        Member: 21:00:00:1b:32:9a:42:de (logged in on: vtic, 0c)

        Member: 21:01:00:1b:32:ba:42:de (not logged in)

        ALUA: Yes

The Exchange luns are mapped to the two ESX Servers:

/vol/GEDASVW06_ArchiveMBXDB001/GEDASVW06_ArchiveMBXDB001.lun fcp_gedaspe03           3       FCP

                                    fcp_gedaspe04           3       FCP

/vol/GEDASVW06_ArchiveMBXDB002/GEDASVW06_ArchiveMBXDB002.lun fcp_gedaspe03           5       FCP

                                    fcp_gedaspe04           5       FCP

/vol/GEDASVW06_ArchiveMBXDB003/GEDASVW06_ArchiveMBXDB003.lun fcp_gedaspe03           6       FCP

                                    fcp_gedaspe04           6       FCP

/vol/GEDASVW06_Exchange_Logs/GEDASVW06_Exchange_Logs.lun fcp_gedaspe03           2       FCP

                                    fcp_gedaspe04           2       FCP

My colleague has now enabled MPIO and will run the verify again.

Thanks for the help.

Regards,

Oli

oweinmann
8,675 Views

When installing the microsoft MPIO we see the luns twice and we still get the same error for verification of the luns.

netapphappyday
8,674 Views

Did you ever find a solution to this?  I have Exchange 2010 running on VMs with the same exact issue and can't find a solution.

-Dani

akw_white
8,674 Views

Did anyone ever find a solution for this? I have SQL Server 2008 running on VMs with almost the exact same issue:

[SnapDrive Error]: The specified initiator <ESX host initiator> is not connected to the target storage system <storage controller>

when attempting to mount the database snapshot.

thomas_glodde
6,563 Views

you guys tried snapdrive 6.4.1?

Public