Oliver pointed me in the right direction -
After the email to check the preferred SAN address I noticed the SAN
was connected via the Data VLAN and not the iSCSI VLAN. The DBA's had
also renamed the server which meant the initiator was keeping the
drive mapped but it was possibly affecting mounting the snaps – I
disconnected and reconnected with an updated initiator name to match
the new server name & reconnected on the correct VLAN and it sorted
things out.
Cheers,
Raj.
On Fri, Jun 27, 2008 at 11:52 AM, Uddhav Regmi
<uddhav.regmi(a)worldnet.att.net> wrote:
> Raj,
> SWs looks OK and OS too.
>
> [09:22:05.681] [SnapDrive Error]: There are no initiators
>> connected to the filer "10.1.46.1".
>>
>> (SnapDrive Error Code: 0xc00402e6)
>>
>> [09:22:05.697] Error Code: 0xc00408f0
>
>
> what does this show
>
> filer> iscsi initiator show
> No initiators connected === something like this ?
>
> is this turn on ?
>
>
>
>
>
> Its little tricky to make it work inside the ESX....
>
> We use the tool esxcfg-swiscsi to configure it. The software iSCSI initiator
> in the VMkernel has a dependency upon the service console, therefore both
> the service console and VMkernel must have an IP route to the iSCSI target.
> 1. Add a VMkernel port to a vSwitch that has an uplink and route to iSCSI
> target
> 2. Ensure service console IP interface has a route to the same iSCSI target
> 3. Using either the VI Client security profile or the esxcfg-firewall, open
> a port in the service console firewall for iSCSI (TCP:3260)
> 4. In the command line, enable iSCSI with esxcfg-swiscsi -e command
> 5. In the command line, run
> 6. At the service console command line, run esxcfg-swiscsi -s
> 7. In the VI Client your iSCSI target should become visible.
> Open the iSCSI tab in your ESX Server configuration and add the dynamic
> address of you filer, probably the same IP as your gateway.
>
> are these all done
>
> Can you access the resources from ESX box ( SQL ) to filer ? Even before
> heading for backup
>
> this is interesting, let me know. Please put me in loop
>
> -----Original Message-----
> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On
> Behalf Of Raj Patel
> Sent: Thursday, June 26, 2008 4:28 PM
> To: Uddhav Regmi
> Cc: NetApp Toasters List
> Subject: Re: SnapManager SQL Errors
>
> Hi,
>
> Its a Windows 2003 sp 2 VM server (running on ESX 3.5) using SnapDrive
> 4.2.1 and SMSQL 2.1.1 and SQL 2005
>
> Three luns f:/g:/h: for database, logs & tmpdb
>
> Verification server is the same as the SQL server (ie it does its own
> dbcc check)
>
> The SAN connection is via IP address - what needs to be able to
> resolve to what ? The SQL server can resolve the SAN and vice versa.
>
> Cheers,
> Raj.
>
>
>
> On Thu, Jun 26, 2008 at 10:44 PM, Uddhav Regmi
> <uddhav.regmi(a)worldnet.att.net> wrote:
>> Raj,
>> Can you elaborate more here.....
>>
>> a) platform infrastructure
>> b) SME, Snapdrie, SQL versions
>> c) is verification Server and SQL server where you installed SME are same
>> server or different server
>> d) does the nslookup resolve all the names correctly from all three
>> locations
>> e) any Dual/multi path involved here....
>> this is interesting error
>>
>> ~uddhav
>>
>> -----Original Message-----
>> From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com]
> On
>> Behalf Of Raj Patel
>> Sent: Wednesday, June 25, 2008 6:49 PM
>> To: NetApp Toasters List
>> Subject: SnapManager SQL Errors
>>
>> Hi,
>>
>> We're just setting up a new SQL server with a SMSQL backup job and
>> we're seeing the following DBCC errors. The SM SQL job has been
>> re-installed and the job setup again as per other servers (ie its the
>> first time we've seen the error). There is also an initiator error but
>> we're not sure why thats listed as an issue - it through the initiator
>> and that IP that the SAN lun's are connected in the first place -
>>
>> [09:22:04.916] *** VERIFY DATABASE AFTER BACKUP
>>
>>
>> 09:22:04.916] Collecting verification information...
>> [09:22:04.916] Getting database backup information from SnapInfo
> file...
>> [09:22:04.916] Running verification from local server....
>> [09:22:04.931] Mounting Snapshot [sqlsnap__server-sql1__recent]
>> for Virtual Disk F of Computer server-sql1
>> [09:22:05.322] WARNING: Unable to get default mount point directory
>> [09:22:05.322] Snapshot will be mounted on subdirectory [MPDisk001]
>> [09:22:05.681] [SnapDrive Error]: There are no initiators
>> connected to the filer "10.1.46.1".
>>
>> (SnapDrive Error Code: 0xc00402e6)
>>
>> [09:22:05.697] Error Code: 0xc00408f0
>> There are no initiators connected to the filer from verification
>> server. Please check SnapManager report and Event logs for details.
>>
>> Any ideas ?
>>
>> Thanks in advance,
>> Raj.
>>
>>
>