klises at sutterhealth
May 10, 2012, 1:34 PM
Post #4 of 4
(839 views)
Permalink
|
Guess I hit a burt.. Can’t read anything from the public side of what the burt is, and the support person said it was cryptic as well from what she saw on the internal documents..
She said there is no fix, so…
Ticket number.2003121780
Burt 205642
From: toasters-bounces [at] teaparty [mailto:toasters-bounces [at] teaparty] On Behalf Of Klise, Steve
Sent: Friday, May 04, 2012 2:04 PM
To: 'Chaim Rieger'; Mailing Lists
Subject: RE: SMSQL question
No, the luns are in production. It’s a production clinical sql server.
From: Chaim Rieger [mailto:chaim.rieger [at] gmail]
Sent: Friday, May 04, 2012 2:03 PM
To: Klise, Steve; Mailing Lists
Subject: Re: SMSQL question
Did you unmount the luns ?
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
"Klise, Steve" <klises [at] sutterhealth> wrote:
I just upgraded a SQL 2005 SQL cluster from snapdrive 5, to 6.3.1r1 and SMSQL 2.x to 5.0. I also upgraded the verification server (remote server).
Now, after upgrading, on a set of drives (G:\data and L:\logs), the backup works, but DBCC fails. What is strange is there is another set of drives (H:\data M:\logs) DBCC works..
I checked for snapshots that would still be mounted, flex clones, etc. Nothing appears to have “busy snapshots”. This is the error (names/ip’s changed to protect the innocent). Even checked for LUNS that would be not assigned to an igroup.. nothing..
This is the event from the verification server:
Event Type: Error
Event Source: SnapDrive
Event Category: Generic event
Event ID: 331
Date: 5/4/2012
Time: 1:19:32 PM
User: N/A
Computer: VERIFICATIONSRV
Description:
Failed to connect FlexClone of Snapshot copy (sqlsnap__SQL__recent) as drive C:\Program Files\NetApp\SnapManager for SQL Server\SnapMgrMountPoint\MPDisk001\ on the computer (VERIFICATIONSRV).
LUN Name = lun0.lun
Storage Path = /vol/SQLSERVER/SQLSERVER/
Protocol Type = LUN
Storage System Name = 10.10.10.10
Error code : ZAPI: An attempt to online LUN '/vol/sdw_cl_SQLSERVER_0/SQLSERVER/lun0.lun' failed on the storage system 10.10.10.10. Error description: Another LUN mapped at this number
This is the snap list.
Volume SQLSERVER
working...
%/used %/total date name
---------- ---------- ------------ --------
0% ( 0%) 0% ( 0%) May 04 13:18 sqlsnap__SQLSERVER__recent
0% ( 0%) 0% ( 0%) May 04 11:33 sqlsnap__SQLSERVER_05-04-2012_11.33.12__weekly
0% ( 0%) 0% ( 0%) May 04 10:43 sqlsnap__SQLSERVER_05-04-2012_10.42.44__weekly
0% ( 0%) 0% ( 0%) May 04 10:03 panstor2(1573990916)_SQLSERVER_snap.65 (snapmirror)
0% ( 0%) 0% ( 0%) May 04 10:03 @snapmir@{EF1F6E8C-64BA-4C23-A8F1-1566E881A373}
0% ( 0%) 0% ( 0%) May 04 10:01 sqlsnap__SQLSERVER_05-04-2012_10.00.07__daily
0% ( 0%) 0% ( 0%) May 04 07:59 sqlsnap__SQLSERVER_05-04-2012_07.58.44__weekly
0% ( 0%) 0% ( 0%) May 04 07:20 sqlsnap__SQLSERVER_05-04-2012_07.19.32__weekly
0% ( 0%) 0% ( 0%) May 04 07:12 @snapmir@{5CF5E20A-6C44-4CE9-B212-0F4BAEB90636}
0% ( 0%) 0% ( 0%) May 04 07:11 sqlsnap__SQLSERVER_05-04-2012_07.10.46__daily
0% ( 0%) 0% ( 0%) May 03 20:40 sqlsnap__SQLSERVER_05-03-2012_20.39.16__daily
0% ( 0%) 0% ( 0%) May 03 19:00 sqlsnap__SQLSERVER_05-03-2012_19.00.00__weekly
0% ( 0%) 0% ( 0%) May 03 18:30 sqlsnap__SQLSERVER_05-03-2012_18.30.00__daily
0% ( 0%) 0% ( 0%) May 03 14:30 sqlsnap__SQLSERVER_05-03-2012_14.30.00__daily
0% ( 0%) 0% ( 0%) May 03 10:30 sqlsnap__SQLSERVER_05-03-2012_10.30.00__daily
0% ( 0%) 0% ( 0%) May 02 19:00 sqlsnap__SQLSERVER_05-02-2012_19.00.00__weekly
0% ( 0%) 0% ( 0%) May 01 19:00 sqlsnap__SQLSERVER_05-01-2012_19.00.00__weekly
0% ( 0%) 0% ( 0%) Apr 30 19:00 sqlsnap__SQLSERVER_04-30-2012_19.00.00__weekly
Any help would be appreciated.
|
