November 10, 2010 at 5:38 am
Hi
I am having a Fullbackup (Monday Night) and T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12 log backup in interverl of every 2hr i need to store Full backup and T1 to T12.What happen was some one had deleted T4,T8 log backup,now unable to restore them anyther option is there.Lose here is accepted
Thanks
Parthi
Thanks
Parthi
November 10, 2010 at 5:45 am
You'll be able to rollback to T3.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
November 10, 2010 at 5:46 am
parthi-1705 (11/10/2010)
HiI am having a Fullbackup (Monday Night) and T1,T2,T3,T4,T5,T6,T7,T8,T9,T10,T11,T12 log backup in interverl of every 2hr i need to store Full backup and T1 to T12.What happen was some one had deleted T4,T8 log backup,now unable to restore them anyther option is there.Lose here is accepted
Thanks
Parthi
Nope not possible.(upto t3)
Is it production database ?
Find out its is deleted or moved.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 10, 2010 at 5:56 am
muthukkumaran (11/10/2010)
Nope not possible.(upto t3)Is it production database ?
Find out its is deleted or moved.
Hi
It is not production it is local some one has deleted the log neededly or unknowingly .I am able to log till t3 only after that errors only
Thanks
Parthi
Thanks
Parthi
November 10, 2010 at 6:12 am
Is your database accessible right now? are you trying to restore it to some other server or same server?
November 10, 2010 at 6:13 am
parthi-1705 (11/10/2010)
muthukkumaran (11/10/2010)
Nope not possible.(upto t3)Is it production database ?
Find out its is deleted or moved.
Hi
It is not production it is local some one has deleted the log neededly or unknowingly .I am able to log till t3 only after that errors only
Thanks
Parthi
Yep, you can restore upto t3.
T-log backup will maintain the log sequence numbers (LSN),if the LSN will not fit then the sql throw the error.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
November 10, 2010 at 6:25 am
ps. (11/10/2010)
Is your database accessible right now? are you trying to restore it to some other server or same server?
Hi
Database is in restoring state
No i am trying to restore them in different server
Thanks
Parthi
Thanks
Parthi
November 10, 2010 at 6:29 am
What about your database on source server. Is it in restoring state? you said you are restoring on a different server.
November 10, 2010 at 6:38 am
ps. (11/10/2010)
What about your database on source server. Is it in restoring state? you said you are restoring on a different server.
On source server there is no space thats why i have choosed new server.The source database it is in normal only not able to see any tables and programability
Thanks
Parthi
November 10, 2010 at 7:13 am
if source database is available you can
1. take a full backup and move it to target. this will give u current data.
2. take a diff backup and use it along with previous full backup. this too will give you current data.
November 10, 2010 at 7:27 am
If you are struggling with space on the source server, as you mentioned AND do not have all of the transaction log files for a full and complete restore on a new server - try to detach/attach the database.
This method will not use any space on the source server.
Chris Powell
George: You're kidding.
Elroy: Nope.
George: Then lie to me and say you're kidding.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply