Record Locks

Friday, March 30, 2012

Hello everybody,
I'd like to get some help about Recovery model.
My scenario:
MS SQL Server 2K SP3
Backup with C.A. Brighstor Enterprise Backup
If i choose the simple recovery model this will impact me if i use a 3rd
Paty backup tool?
Thanks
Leandro Loureiro dos Santos
Vitoria/ES
BrazilDepends on what the 3:rd party backup tool does. Use simple recovery model
if you don't do transaction log backups. If you do transaction log backups,
use full recovery model.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Leandro Loureiro dos Santos" <leandro@.email.com> wrote in message
news:%232M0lqK8DHA.2540@.TK2MSFTNGP11.phx.gbl...
> Hello everybody,
> I'd like to get some help about Recovery model.
> My scenario:
> MS SQL Server 2K SP3
> Backup with C.A. Brighstor Enterprise Backup
> If i choose the simple recovery model this will impact me if i use a 3rd
> Paty backup tool?
> Thanks
> Leandro Loureiro dos Santos
> Vitoria/ES
> Brazil
>
>

recovery question

I have a full backup of a sql database on 4/27
I have a full backup of a sql datbase on 6/27
Is it possible to recover the data on 6/26 without seeing the changes on
6/27?On Tue, 24 Jul 2007 10:51:33 -0700, "nobody" <nobody@.nobody.com>
wrote:
>I have a full backup of a sql database on 4/27
>I have a full backup of a sql datbase on 6/27
>Is it possible to recover the data on 6/26 without seeing the changes on
>6/27?
If the database is in Full recovery mode, and you have all the log
backups from 4/27 through 6/26, then you can restore the 4/27 database
backup and apply all the log up to the point you want to stop
(point-in-time recover).
Otherwise, no.
Roy Harvey
Beacon Falls, CT|||In article <#JjvGthzHHA.5160@.TK2MSFTNGP05.phx.gbl>, nobody@.nobody.com
says...
> I have a full backup of a sql database on 4/27
> I have a full backup of a sql datbase on 6/27
> Is it possible to recover the data on 6/26 without seeing the changes on
> 6/27?
>
>
if you have full recovery turned on, and all the required LOG backups,
you can use "STOPAT" to do a point-in-time restore. If you have not run
a backup of the TLOG that should be the first thing you do.
--
Graham (Pete) Berry
PeteBerry@.Caltech.edu|||I have no log backups. So No?
"Pete Berry" <PeteBerry@.Caltech.edu> wrote in message
news:MPG.210fe9254040420a98969a@.msnews.microsoft.com...
> In article <#JjvGthzHHA.5160@.TK2MSFTNGP05.phx.gbl>, nobody@.nobody.com
> says...
>> I have a full backup of a sql database on 4/27
>> I have a full backup of a sql datbase on 6/27
>> Is it possible to recover the data on 6/26 without seeing the changes on
>> 6/27?
>>
> if you have full recovery turned on, and all the required LOG backups,
> you can use "STOPAT" to do a point-in-time restore. If you have not run
> a backup of the TLOG that should be the first thing you do.
> --
> Graham (Pete) Berry
> PeteBerry@.Caltech.edu|||actually i found out its only a table within a database that needs to be
fixed or restored. how can this be done?
"nobody" <nobody@.nobody.com> wrote in message
news:u3qP2bjzHHA.5980@.TK2MSFTNGP04.phx.gbl...
>I have no log backups. So No?
> "Pete Berry" <PeteBerry@.Caltech.edu> wrote in message
> news:MPG.210fe9254040420a98969a@.msnews.microsoft.com...
>> In article <#JjvGthzHHA.5160@.TK2MSFTNGP05.phx.gbl>, nobody@.nobody.com
>> says...
>> I have a full backup of a sql database on 4/27
>> I have a full backup of a sql datbase on 6/27
>> Is it possible to recover the data on 6/26 without seeing the changes on
>> 6/27?
>>
>> if you have full recovery turned on, and all the required LOG backups,
>> you can use "STOPAT" to do a point-in-time restore. If you have not run
>> a backup of the TLOG that should be the first thing you do.
>> --
>> Graham (Pete) Berry
>> PeteBerry@.Caltech.edu
>|||In article <u3qP2bjzHHA.5980@.TK2MSFTNGP04.phx.gbl>, nobody@.nobody.com
says...
> I have no log backups. So No?
> "Pete Berry" <PeteBerry@.Caltech.edu> wrote in message
> news:MPG.210fe9254040420a98969a@.msnews.microsoft.com...
> > In article <#JjvGthzHHA.5160@.TK2MSFTNGP05.phx.gbl>, nobody@.nobody.com
> > says...
> >> I have a full backup of a sql database on 4/27
> >>
> >> I have a full backup of a sql datbase on 6/27
> >>
> >> Is it possible to recover the data on 6/26 without seeing the changes on
> >> 6/27?
> >>
> >>
> >>
> > if you have full recovery turned on, and all the required LOG backups,
> > you can use "STOPAT" to do a point-in-time restore. If you have not run
> > a backup of the TLOG that should be the first thing you do.
> > --
> > Graham (Pete) Berry
> > PeteBerry@.Caltech.edu
>
Again depends on the recovery model
simple => NO
full => yes if you do a backup of the tail of the log first
--
Graham (Pete) Berry
PeteBerry@.Caltech.edusql

Recovery question

Hello everybody,
I'd like to get some help about Recovery model.
My scenario:
MS SQL Server 2K SP3
Backup with C.A. Brighstor Enterprise Backup
If i choose the simple recovery model this will impact me if i use a 3rd
Paty backup tool?
Thanks
Leandro Loureiro dos Santos
Vitoria/ES
BrazilDepends on what the 3:rd party backup tool does. Use simple recovery model
if you don't do transaction log backups. If you do transaction log backups,
use full recovery model.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Leandro Loureiro dos Santos" <leandro@.email.com> wrote in message
news:%232M0lqK8DHA.2540@.TK2MSFTNGP11.phx.gbl...
> Hello everybody,
> I'd like to get some help about Recovery model.
> My scenario:
> MS SQL Server 2K SP3
> Backup with C.A. Brighstor Enterprise Backup
> If i choose the simple recovery model this will impact me if i use a 3rd
> Paty backup tool?
> Thanks
> Leandro Loureiro dos Santos
> Vitoria/ES
> Brazil
>
>

Recovery problem

In my production database i have lost data in three tables.so i just want to restore the data from my backup which was created.

I am connecting over remote desktop connetion to the server.

With in the databases i right click the database which has my three tables within them.

Then select all tasks->restore database

In restore i select files or file groups

then i select the day i want to restore the ok

It comes up with this error

Cannot open the back up device 'C:\programs\......'

device error or device online

Restore database is terminating abnormally

Is it because i am not doing at the server as i am connecting over remote desktop....

And my database has several tables apart from these three tables.is it possible for me just to restore these three tables.

i am using sql server 2000 database

Please let me know..

Are you using the GUI on the remote server or the GUI on your local machine? The GUI you use will need to be on the machine that the file resides if you are using localfile paths.

Also, you will only be able to restore those 3 tables using a PARTIAL restore if they exist in a separate filegroup to the rest of the data.If you only have one filegroup then you will have to restore the whole thing.

Either way, i think your only option is to do the restore to a separate database and then copy the data to your "live" db.

Check out the RESTORE information in Books Online as this gives a fairly thorough rundown of all the options.

HTH!

|||

Hi,

YOU CAN RETRIEVE THE BACKUP DATA FROM THE DELETED DATA..

I AM WORKING WITH SQL SERVER 2005.

JUST TRY ONCE AFTER THAT YOU CAN!!!!!!!!!!

Recovery Plan -

I want to make sure that what I'm thinking can actually be
done.
We currently have our production server with the datafiles
(including systems) on one removeable drive (E) and the
logs on another (F).We maintain a backup server that hold
all the data/log files on the D drive. Both server's have
the same server configurations.
The backup server is kept up to date via log shipping. If
we had disk failure, we would be able to bring the
databases out of standby mode and rename the server (with
a few other steps in there)...
HERE"S MY REAL QUESTION -
Now if we had a different failure where we had our disk
drives, but could no longer use the server, would the
following be possible.
Could we add the E and F drive to the backup server.
leaving the exsisting database in place. Modify the SQL
Server startup paramenters to use the master database on
the E drive instead of the D drive.
The master on the E drive would then point to all the
databases we have on the E and F drive and we would be
ready to go'
I hope that makes sense... It just seems a little too
easy...
Please advise and poke holes.
ThanksDefine removable drive here ... I'm not sure what you mean.
If you had a disk failure, why would you bother even
attempting an operation that may not work if your log
shipped secondary is brought online? I assume you'd want
to do some sort of attach, but that makes no sense. You
still have issues of DB users, etc.
You would also be changing the drive signatures, etc. I
wouldn't go there. And renaming everything (server, IP,
etc.) is always IMHO not the way to go. Your DR plans
should be able to tolerate the name change of the server
in a log shipping situation. Too many manual steps, too
many moving parts ... too many things that could go wrong.
Log shipping just works.|||By removable drives I mean external drives that can be
taken from one server and added to another. We do this
right now when we have large backups (150gig)that we need
to move to different servers. You haven't heard of this
before?
Since our log shipping server can be up to an hour behind,
if we have our production data we would prefer to use
that. The log shipping server is to be used only when we
cannot recovery the data from production.
Our current failover method does have attaching involved,
but I was thinking if my system databases are on the drive
we just moved over, why couldn't I point my SQL startup
paraments to the new master database, which in turn would
already have the databases/logins already setup.
>--Original Message--
>Define removable drive here ... I'm not sure what you
mean.
>If you had a disk failure, why would you bother even
>attempting an operation that may not work if your log
>shipped secondary is brought online? I assume you'd want
>to do some sort of attach, but that makes no sense. You
>still have issues of DB users, etc.
>You would also be changing the drive signatures, etc. I
>wouldn't go there. And renaming everything (server, IP,
>etc.) is always IMHO not the way to go. Your DR plans
>should be able to tolerate the name change of the server
>in a log shipping situation. Too many manual steps, too
>many moving parts ... too many things that could go wrong.
>Log shipping just works.
>
>.
>

Friday, March 30, 2012

recovery question

Recovery question

recovery question

recovery question

Recovery question

Recovery problem

Recovery Plan -

Record Locks

Blog Archive

About Me