“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@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Raj Patel
Sent: Tuesday, January 05, 2010
6:30 PM
To: Bill Holland
Cc: toasters@mathworks.com
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@gmail.com> 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@gmail.com> 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.