phigmov at gmail
Jan 6, 2010, 5:07 PM
Post #5 of 5
(3220 views)
Permalink
|
Ah well, turned out the hotfix doesn't apply (must have been rolled
into Windows 2008 sp 2).
Guess we'll log a call to NetApp.
It may just be the new version of SM SQL or SnapDrive that is causing
us grief - from memory we didn't have so many niggly issues with the
previous version. Regardless we've got a couple of DBA's with decades
of accumulated experiance on SQL, Oracle & Sybase and while they have
embraced Snapshots they don't particular enjoy troubleshooting
something that just appears to get in the way of something they're
already pretty familiar with (ie traditional DB Backup/Restore).
I'll let you know how the call proceeds.
Cheers,
Raj.
On 1/6/10, Page, Jeremy <jeremy.page [at] gilbarco> wrote:
> "Our DBA's are starting to wonder if the aggravation of troubleshooting
> SM SQL / SD issues is worth the convenience of instant snapshots. At
> least with traditional backups they know where they stand."
>
>
>
> How often do they verify that their backups don't have problems? I'm
> not arguing really, but there are better reasons to make a big change
> one way or the other.
>
> We do traditional backups and then let the backup files get in our
> snapvault, Databases are the one place that I want the system to verify
> it's quienced any outstanding writes while the snapshots are created. I
> think that SQL 2008 may be able to with VSS alone but I don't have the
> bandwidth to test it enough to be comfortable.
>
> ________________________________
>
> From: owner-toasters [at] mathworks [mailto:owner-toasters [at] mathworks]
> On Behalf Of Raj Patel
> Sent: Tuesday, January 05, 2010 6:30 PM
> To: Bill Holland
> Cc: toasters [at] mathworks
> Subject: Re: Issues mounting snapshot
>
>
>
> Hi Bill,
>
> I'm in as a Domain Administrator - UAC is off. Checking the service
> account Snapdrive runs under UAC is also off.
>
> Looking through the event logs I do see some prior events - not sure if
> they're related:
>
> The flush and hold writes operation on volume F: timed out while waiting
> for a release writes command.
>
> This is at 1am in the morning for each iSCSI attached LUN on the box.
>
> Its been suggested I try this hotfix -
>
> http://support.microsoft.com/kb/955656
>
> I'll give it a go and let you know how I get along.
>
> Cheers,
> Raj.
>
> On Wed, Jan 6, 2010 at 11:28 AM, Bill Holland <hollandwl [at] gmail>
> wrote:
>
> Is the Admin Authentication Mode of the UAC enabled? It can prevent
> access to the files in the LUN
>
> On Jan 5, 2010 5:17 PM, "Raj Patel" <phigmov [at] gmail> wrote:
>
> Hi,
>
> Simple problem - I have a SQL server (Windows 2008, 64 bit, SQL
> 2008,
> Snapdrive 6.1 & snapmanager sql 5.0.0.38 (both 64bit)
>
> Snapshots work fine - however the dbcc check fails when it
> attempts to
> mount the snapshot for a verification.
>
> Now - I am able to mount the snapshot on a Windows 2003, 32 bit
> box
> running Snapdrive 6.1 so I'm fairly certain its not a volume
> space
> issue.
>
> The actual error I get is 'A timeout of 120 secs elapsed while
> waiting
> for volume arrival notification from the operating system' -
> this
> happens when I use the SD GUI to manually mount the snapshot.
> The
> console shows pretty much the same sort of error if I watch it
> while
> running the GUI mount.
>
> We have this working fine on other SQL servers and its just
> started
> happening on this box.
>
> Any ideas ?
>
> Our DBA's are starting to wonder if the aggravation of
> troubleshooting
> SM SQL / SD issues is worth the convenience of instant
> snapshots. At
> least with traditional backups they know where they stand.
>
> Thanks in advance,
> Raj.
>
>
>
>
>
> Please be advised that this email may contain confidential information.
> If you are not the intended recipient, please do not read, copy or
> re-transmit this email. If you have received this email in error,
> please notify us by email by replying to the sender and by telephone
> (call us collect at +1 202-828-0850) and delete this message and any
> attachments. Thank you in advance for your cooperation and assistance.
>
> In addition, Danaher and its subsidiaries disclaim that the content of
> this email constitutes an offer to enter into, or the acceptance of,
> any
> contract or agreement or any amendment thereto; provided that the
> foregoing disclaimer does not invalidate the binding effect of any
> digital or other electronic reproduction of a manual signature that is
> included in any attachment to this email.
|
