Red Gate forums: SQL Log Rescue

help

mai — Wed, 15 Dec 2010 12:12:30 GMT

Hi,
i want to use SQL log rescue tool by another .net solution to get all db rows history how can do this???
thanks in advance

RE: No recent data in live log

bigdog — Thu, 02 Sep 2010 21:04:08 GMT

Actually our transaction logs are not backed up at all, just the FULL.

The logs also had not been truncated for quite some time and grew ridiculously large. Once I truncated the logs I started getting fresh data in SQL Log Rescue, and it has already saved me nicely. This set up suits my needs well enough.

I have other questions but not related to this particular post. You can consider it closed.

RE: No recent data in live log

Chris Auckland — Mon, 16 Aug 2010 14:30:51 GMT

The SQL log rescue forum is still monitored, but as it's not one of our supported products, help on this forum will be limited.

When you configured your project, did you add the FULL backup plus the unbroken chain of transaction log backups?

If you just have the FULL plus the live log, then it probably won't work very well, unless there hasn't been any t-log backups since the FULL.

I hope this helps.

No recent data in live log

bigdog — Fri, 13 Aug 2010 14:08:09 GMT

Hello Everyone I hope this is still an actively monitored forum.

I have an old SQL Server 2000 instance with data mysteriously disappearing. With no other clues I have installed Log Rescue 1.2 upon several recommendations around the web.

My database is on a full recovery model and backed up nightly using built-in maintenance plan. The plan is optimized to "remove unused space from database files" but the transaction log backup is not part of this plan.

1. When I include the latest backup when loading my recovery project I get nothing.

2. When I run it without a backup and just let it pull the live logs, I get the same months old data every time.

I was worried that the nightly backup was truncating the logs so I tested it by manipulating some data and immediately loading my rescue project. I still just get the same old data, nothing recent.

I restored the same database on my development server and it works fine, even after hand running a full backup (though no nightly maintenance plans there).

Any ideas why I can't see any recent transactions?

RE: file format for sql log rescue

csinusa — Wed, 07 Jul 2010 15:19:59 GMT

Do you have any other product that can read TLog then as my backups are in .sqb format?

RE: file format for sql log rescue

eddie davis — Wed, 07 Jul 2010 14:58:48 GMT

Thank you for your reply.

SQL Log Rescue only supports SQL Server 2000 and can only read:

1. The live SQL Server 2000 Transaction Log.
2. Backup files created using either our own SQL Backup V5 or earlier and native SQL Server backup files.

If you wish to use SQL Log Rescue against SQL Server 2005 and 2008, unfortunately these later version of SQL Server are not supported.

Also if you wish to read backup files created using SQL Backup V6.*, regrettably the .sqb file format changed in SQL Backup V6 and SQL Log Rescue cannot read SQL Backup V6 files.

As per my colleague Anu's post in this thread on the 1st July 2010, Log Rescue is free and unsupported product. There has been no development work done on this product for a number of years and there are no plans to do so.

Many Thanks
Eddie

RE: file format for sql log rescue

csinusa — Thu, 01 Jul 2010 16:30:28 GMT

So what file format does this tool support?

RE: file format for sql log rescue

Anu Deshpande — Thu, 01 Jul 2010 09:25:45 GMT

Log Rescue is free and unsupported and there has been no development work done on this product for quite a while.

While it should fully support SQL 2000 it does not support SQL 2005 or 2008, so if any of your sources are SQL 2005 or SQL 2008 it will not work.

Also as there is no work being done on it any changes to other products won't be catered for in Log Rescue.

If it is telling you that the backup file format is unsupported then I'm afraid that there is not much that I can do. I'm sorry that I can't be of more help.

The forum might offer more insight - http://www.red-gate.com/MessageBoard/viewforum.php?f=21

I'm sorry that I can't be more help.

file format for sql log rescue

csinusa — Tue, 29 Jun 2010 23:04:22 GMT

Hi All,
I have downloaded sql log resue 1.20 and it installed successfully.
But when I try to open backup files, it gives me 2 different unique message.
"Not a supported backup file format" .
and the error "Unable to access backup file"

Both errors are on the files have ext .sqb.

Please advice.

Thanks

RE: SQL2005 - why is Lumigent going to support it and not you?

Brian Donahue — Wed, 31 Mar 2010 13:56:17 GMT

Hello,

There aren't any plans to do a log reader tool on the horizon and the reason for cancelling SQL Log Rescue had more to do with Microsoft's attempt to protect the log file format than a market-driven decision based on sales volume. I think we would have liked very much to keep it going, but it was too risky to update. This is the reason why it had been a free tool for so long, because we couldn't in good conscience take money for a product that we had no intention of supporting any more.

Before SQL Server 2005 came out, we had charged $495 for the tool!

RE: SQL2005 - why is Lumigent going to support it and not you?

slyeager73 — Tue, 30 Mar 2010 19:50:12 GMT

Hello,

I am curious if a new version is in development or is there another RG product that will also read the transaction logs for SQL 2008? We used Log Rescue on our SQL 2K DB's. This was a great tool that helped us trouble shoot what a user did and when, very quickly. We dropped Lumigent's Log Explorer since Log Rescue did every thing we needed and was also free.

We also use Red-Gates SQL Backup which is a great tool that speeds up and encrypts our databases backups and our log files backups that we use for log shipping. We gave SQL Backup a try because we had such great success with Log Rescue and have been happy so far.

Since we are on SQL 2008, and compress and encrypt our log backups with SQL Backup we are unable to try and purchase another tool that will give us the ability to read the transaction logs without having to jump through some hoops. This functionality isn't needed often, but when the need is there, it is a priority.

I would love to hear that SQL Log Rescue is coming back even if it is no longer free with a reasonable purchase price. If not we will likely have to move to Quest, since they do provide a backup compression and encryption software along with software that gives us the ability to read the transaction logs.

Thank you for your time,

RE: Log Rescue With Filestream Database

Brian Donahue — Mon, 16 Nov 2009 16:00:55 GMT

Hi,

Sorry, but Log Rescue has been discontinued and it only ever worked with SQL Server 2000, so no filestream support.

Log Rescue With Filestream Database

winksc — Mon, 16 Nov 2009 11:43:49 GMT

Will log rescue work with the new filestream feature of sql server 2008?

For example if I accidentally deleted a row from a filestream table could I recover all the data with Log Rescue?

RE: Please Resurrect Log Rescue to support more current versions

DonMan — Wed, 19 Aug 2009 16:45:28 GMT

Yes. I am using SQL Backup 6.2. Since the Object Level Recovery does not leverage transaction log backups, it is not adequate to meet that need. But along those lines object level point in time recovery could be made available with Log Rescue intergrated into it. What I truely am looking for is a replacement for Lumigent Log Explorer since it won't work with SQL 2008.. I may need to consider the Apex or Quest products for that, but would prefer to get it from Red Gate.

RE: Please Resurrect Log Rescue to support more current versions

Michelle Taylor — Wed, 19 Aug 2009 11:11:29 GMT

Have you had a look at SQL Backup 6.2? Depending on exactly what you wanted Log Rescue for, the Object Level Recovery might be able to help...