Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
pleitch
Starting Member
8 Posts |
 Posted - 2008-07-23 : 02:33:48
|
| I have a great product that I have used for years, Lumigent Log Explorer. It goes through either backed up or on-line logs and provides complete data alteration information (what the values were, what they were changed to and who changed the data). It also provides point in time restore at the database, table or row level (or undo a specific transaction that might have spanned several tables).My problem is that the company I work for has recently moved all SQL Servers to use ComVault for transaction log backups. Without the transaction logs, I can't use Log Explorer. There seems no obvious way to get access to the actual log files from ComVault, it only gives an interface that allows the user to restore.So I am wondering if there is any option to have a log backup that doesn't update the "start of logical log" so that another log backup can dump out to file the same information? That is allow two seperate log backup processes that don't affect eachother.I have tried with "NoTruncate" because it is supposed to do this:NoTruncate The log is not truncated. All transactions remain in the log. I'm not sure what's up, I can't see that incuding this option makes a lick of difference. Every time I backup with "No_Truncate" I only get the most recent logs since the last log backup. I am assuming that they are kept in the ".LDF" log file, but are still marked as no longer needing to be backed up.Alternatively, has anyone has had success getting transaction log files out of ComVault?Thanks,Phililp |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-07-23 : 08:22:09
|
| Well, there is Copy_only option backups which doesn't affect T-log chain. But it is available only in SQL server 2005. |
 |
|
|
|
|
|
Multiple Transaction Log backups