I think you guys are also running into BURT 233939, sadly it's not accessable through NOW.
The key of that BURT is to make sure the mount point in the database path is exactly same as the mount point path in SnapDrive.
For us the lun was mounted with in upper case in snapdrive, while the drive letter in the sql configuration was in lower case. Windows isn't case sensitve and doesn't care about those differences, but SM SQL does...I think it'll be fixed soon.
You should check the mount paths carefully, I bet it's the same issue on your side.
________________________________
From: Milazzo Giacomo [mailto:G.Milazzo@sinergy.it] Sent: Thursday, November 06, 2008 8:03 PM To: Herring, Jason; Buerger, Andreas Subject: R: SMSQL and verification issues
It seems we'ge got a bug J
I'm in contact with some guy in NetApp US and I'll notify you any news as soon as I'll receive them,.
Regards,
Da: Herring, Jason [mailto:jherring@insightinvestments.com] Inviato: giovedì 6 novembre 2008 18.19 A: Buerger, Andreas; Milazzo Giacomo Oggetto: RE: SMSQL and verification issues
Interesting timing, I was just about to help a customer setup something very similar to this w/ a remote verification server & they are using mount points. Would you mind including me on the resolution to this trouble ticket, or, pass on the ticket # so I can open one in advance and reference it?
Thanks, Jason
-----Original Message----- From: owner-toasters@mathworks.com on behalf of Buerger, Andreas Sent: Thu 11/6/2008 4:18 AM To: Milazzo Giacomo; toasters@mathworks.com Subject: RE: SMSQL and verification issues
Hi,
We'r running into the same problem with a Clustered MS SQL installation. There is an open case, but up to now no solution for the issue. The snapshoted LUN gets mounted correctly, but SMSQL doesn't find the DB files for verification...
Whats your installed version of SnapDrive and SMSQL?
Ours is SD 5.0 and SMSQL 2.1.1.
Cheers Andreas
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Milazzo Giacomo Sent: Thursday, November 06, 2008 11:05 AM To: toasters@mathworks.com Subject: SMSQL and verification issues Importance: High
Hi all,
Up to now I've always set up SQL cluster with LUNs on drive letters and I've used a single stand alone SQL instance on the "passive" node of the cluster as verification server.
Sincerely this is my first experience of SMSQL on a MS cluster using mount point and an external verification server. The scenario so is a SQL cluster using mount point instead of drive letters and an external verification server. We have the DB files on a LUN mounted as S:\DB01, the logs on another LUN mounted as S:\LOG01 and GLINKA0 as external verification server. Here follows the log.
The backup is successfully done but when the verification starts something goes wrong: the snapshotted LUNs for DB and LOG are successfully mounted on Z: and Y: but SMSQL on verification does not find the db files a/o the log files looking for it on S:\DB01 (that is the path of the mount point!)...
I hope this has nothing to do with capital or lowercase usage of paths J (we've S:\DB01 and S:\db01 on log...).
From the verification server I can see the LUN mounted, I can browse them while are mounted and I can see the 'not found' files...
Any idea?
Thank you in advance,
[09:28:45.992] *** VERIFY DATABASE AFTER BACKUP
[09:28:45.992] Collecting verification information...
[09:28:45.992] Getting database backup information from SnapInfo file...
[09:28:45.992] Initializing SnapManager server on remote machine [GLINKA0]...
[09:28:46.602] Mounting Snapshot [sqlsnap__amen01__recent] for Virtual Disk S:\DB01\ of Computer amen01
[09:29:15.180] This Snapshot is mounted as the drive [Z:].
[09:29:15.180] Mount Snapshot succeeded.
[09:29:15.180] Mounting Snapshot [sqlsnap__amen01__recent] for Virtual Disk S:\LOG01\ of Computer amen01
[09:30:08.664] This Snapshot is mounted as the drive [Y:].
[09:30:08.664] Mount Snapshot succeeded.
[09:30:08.664] Cannot find the data file in the mounted drive:
[09:30:08.664] S:\db01\ale2.mdf
[09:30:08.664] Dismounting Virtual Disk Z of SnapShot [sqlsnap__amen01__recent]...
[09:30:25.429] Dismount Snapshot succeeded.
[09:30:25.429] Dismounting Virtual Disk Y of SnapShot [sqlsnap__amen01__recent]...
[09:30:31.476] Dismount Snapshot succeeded.
[09:30:31.492] Unable to locate the database data file on the mounted disk drive.
[09:30:31.492] Database verification information was not updated.
[09:30:31.507] There is an error during database verification.
[09:30:31.507]
[09:30:31.507] **** FULL DATABASE BACKUP RESULT SUMMARY #1 ****
[09:30:31.507] Backup Time: 11-06-2008_09.28.12
[09:30:31.507] Backup Group [#1]:
[09:30:31.507] #1 : [amen01\amen01 - ale2] : Failed with error code 0xc0040814.
[09:30:31.507] #1 : [amen01\amen01 - ale2] Error : Backup OK, but DBCC Skipped.
[09:30:31.507] #2 : [amen01\amen01 - ale3] : Failed with error code 0xc0040814.
[09:30:31.507] #2 : [amen01\amen01 - ale3] Error : Backup OK, but DBCC Skipped.
[09:30:31.507] #3 : [amen01\amen01 - db4] : Failed with error code 0xc0040814.
[09:30:31.507] #3 : [amen01\amen01 - db4] Error : Backup OK, but DBCC Skipped.
[09:30:31.507]
[09:30:31.507] *** SNAPMANAGER BACKUP JOB ENDED AT: [11-06-2008 09.30.31]
[09:30:31.507] Unable to locate the database data file on the mounted disk drive.
-- WINCOR NIXDORF International GmbH Sitz der Gesellschaft: Paderborn Registergericht Paderborn HRB 3507 Geschäftsführer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. Jürgen Wunram Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193
Diese E-Mail enthält vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet.
This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.