- The site for all your DTS needs.
"Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
news:%23w8WfN30DHA.2568@TK2MSFTNGP09.phx.gbl...
> Ahhh good. I learnt something new today. Perhaps EMC also use this API.
> Let me see if I can't find an example.
>
> --
>
> ----------------------------
> Allan Mitchell (Microsoft SQL Server MVP)
> MCSE,MCDBA
>
www.SQLDTS.com > I support PASS - the definitive, global community
> for SQL Server professionals -
http://www.sqlpass.org >
>
>
> "Emil Nadinic" <quake_dude@hotmail.com> wrote in message
> news:6024dc11.0401041622.59f70e04@posting.google.com...
> > Hi Allan,
> >
> > Microsoft has a "Microsoft SQL Server Virutal backup Device
> > Specification" SDK which details how you can create a virtual snapshot
> > device in memory, which provides the fastest snapshot method.. As part
> > of the SDK, they ship some API calls which have the potential to
> > "freeze" and "thaw" the transaction process, without interrupting the
> > running process whatsoever. How this works internally within SQL I'm
> > not sure, but my understanding was that this API could be used to
> > issue the Freeze and Thaw commands. I guess what I'm hoping to be able
> > to do is to write a small application which can do this. the sample
> > code they supply with the SDK doesn't specifically show the freeze and
> > thaw process, as it seems to be part of the Snapshot flow.. The only
> > example I've seen of someone being able to do this is the Hitachi
> > quicksnap.exe application, which they charge like wounded bulls for.
> > I'm guessing that no one outside of them has done anything similar -
> > there certainly seems to be a lack of information on the web about the
> > specifics of the API calls, from what I can see.
> >
> > Thanks!
> >
> > Regards,
> >
> > Emil.
> >
> >
> >
> > "Allan Mitchell" <allan@no-spam.sqldts.com> wrote in message
> news:<enV6oHr0DHA.2856@TK2MSFTNGP09.phx.gbl>...
> > > You are going to have to somehow PAUSE SQL Server.
> > >
> > > You can use NET PAUSE <<service name>>
> > >
> > > I have never done this and am unsure of the implications.
Applications
> will
> > > not be able to connect to SQL Server during this period so you will
need
> to
> > > make sure it is an "Off" period.
> > > After the snapshot has been taken you can issue NET CONTINUE <<service
> > > name>>
> > >
> > > Our SAN server snapshots take ~3secs for 450GB
> > >
> > > This may be the way EMC do it as well. Some applications have
spiralled
> out
> > > of control when the thaw didn't happen as expected but that was
remedied
> > > easily.
> > >
> > > I would suggest you will need a lot of testing.
> > >
> > > If you can guarantee the time this is done will be devoid of activity
> then
> > > you can easily STOP SQL Server and then issue a RESTART. This will
> cause
> > > transactions and applications to be exited gracefully with reliable
> error
> > > messages that mean something.
> > > --
> > > --
> > >
> > > Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
> > >
www.allisonmitchell.com - Expert SQL Server Consultancy.
> > >
www.SQLDTS.com - The site for all your DTS needs.
> > > I support PASS - the definitive, global community
> > > for SQL Server professionals -
http://www.sqlpass.org >
>