Addendum:
pay attention to the way used to
write the drive letter too!!! It’s always UPPERCASE. As stated this morning we’ve
renamed the Windows path to lowercase to respect the way that SMSQL look for
files but reconnecting the SD to the new path we’ve used s:\db01…Wrong!! J
We had to use S:\db01 for the drive letter is always upper case and the path is…the
way you choose to write it!!!
Incredible but true
Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
Per conto di Milazzo Giacomo
Inviato: venerd́ 7 novembre 2008 12.03
A: De Wit Tom (Consultant); toasters@mathworks.com; Buerger, Andreas;
Ledbetter, Charles
Oggetto: R: SMSQL and verification issues
Hi all
Tow and Andreas were right! And my premonition too J
We’ve simply renamend the Windows path from uppercase to lowercase
letters, disconnected and reconnected the LUNs in SD this mount points and
verification server works fine now!
Thank you very much to all of you
Da: De Wit Tom (Consultant)
[mailto:tom.de.wit@consultant.volvo.com]
Inviato: venerd́ 7 novembre 2008 11.23
A: Milazzo Giacomo; toasters@mathworks.com
Oggetto: RE: SMSQL and verification issues
Repost as previous post didn't seem to get through ...
From: De Wit Tom (Consultant)
Sent: vrijdag 7 november 2008 9:24
To: 'Milazzo Giacomo'; toasters@mathworks.com
Subject: RE: SMSQL and verification issues
Hi,
I think its exactly like you say yourself. The database connection
during verification is case sensitive. We had the exact same issue when
starting to use volume mount points.
The solution is to reattach the database with the exact same casing
as the filepath on the server !
Grtz,
Tom
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Milazzo Giacomo
Sent: donderdag 6 november 2008 11:05
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.