SQL Server 2005 Backup Third Party Tools
-
crever (2/1/2008)
I don't understand how you can say LiteSpeed is too decentralized. They push everything up to a central repository and you can do all of your reporting from there. I've been on LS for years and their model is very solid. I don't know who you talked to over there, but you either misunderstood them or they just don't know what they're talking about.they said you can have a central repository for the catalog data, but the backups go to a UNC path
do they go to a UNC path where each backup is it's own file or do they all go into once central database that no one can delete?
with evault and Avamar all the backups go into their backup database that the app reads to and from, not just catalog data but the actuall backups go in there. the way i understood litespeed is that the database is just for the catalog data and the backups are separate files like windows backup and if you want to go to a central server you have to go to a UNC path
-
No, LiteSpeed backups are individual files just like many other backups, including native. There's a clear advantage here in the ability to ship them to other servers and mirror backups to multiple locations.
You can control who can access those files at the OS level. I don't like the centralized backup DB way of doing things. I prefer to have the control over my backup files to be able to do anything with them I like.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
how many people in your IT department?
how many have access to admin accounts?
how many of those admin accounts have access to those files?
do you have different local admin passwords on each server?
do you have strong passwords?
it doesn't have to be deliberate, you can delete the backups by accident and lose them for good. in our case our tape robot is going off support soon and we need to do something.
i like centralized storage because you can't delete the central db. it's locked by the OS as long as the application is running just like SQL db files. with individual backup files it is possible to delete a file by accident and not be able to recover it. and we don't want to spend money on disk and tapes for backups. see no reason to do so
-
I like the object-level restore in litespeed and the like. It's really saved our asses a few times. Those vault products can't even touch that.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
Litespeed is a great product. However I think Red Gate and Idera do object restore as well. Perhaps hyperbac.
-
crever (2/1/2008)
I like the object-level restore in litespeed and the like. It's really saved our asses a few times. Those vault products can't even touch that.that's true and one downside of evault is that it can't even restore to a different server. you have to restore the file and then use a script to restore the db from SSMS. with Veritas you can restore to another server in one step.
i looked at Litespeed yesterday because of the object level restore capability, but the unc path thing is too much of a risk in my opinion. no one ever got fired because they told someone it will take so many hours to restore a table or sp because this what needs to be done. but the risk of losing actuall backups is too much. unfortunately i don't work for the white house
-
I don't remember RedGate having OLR, but Idera and HyperBac both do. Though I've talked to several people and Idera's OLR isn't getting good reviews at all. People aren't happy with it.
Watch my free SQL Server Tutorials at:
http://MidnightDBA.com
Blog Author of:
DBA Rant – http://www.MidnightDBA.com/DBARantMinion Maintenance is FREE:
-
I have used Lightspeed for years and it works great, however it's fairly pricy. I have heard from Quest reps that a row level restore is possible with the enterprise edition but OLR is usually sufficient.
-
Red Gates' SQL Backup does not support object level restore. Other products do, but there is a caveat with that feature, the last time we looked. In short, the table you restore using object level recovery may not contain the same data if you had performed a full restore.
The reason being that when a full database backup is made, all writes to the data files are suspended. Transactions committed during the backup are written to the transaction log as usual, but not to the data files until the backup completes. Because a backup is suppose to contain the state of the database at the time the backup ends, to restore a table 'correctly', you need to retrieve the data as contained in the data file, and also apply all committed transactions found in the transaction log.
When we evaluated Litespeed, it only restored table data from the backed up data files. Transactions that were commtted during the time of the backup were not applied at all. Hence we had cases where our table level restore contained different data from our full database restore.
I don't know if this has changed in recent versions.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017. -
There were some errors of fact in my previous post. A more accurate explanation can be found here (http://www.sqlbackuprestore.com/recoveringindividualtables.htm).
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017. -
i'm using Redgate SQL Backup v5.x, its a great product offering good speed and very high compression. It also gives us 256bit encryption which we need for our backups. Very flexible as we just code in the Redgate SP for our backup jobs. There is also a neat little util that injects Redgate backup jobs into an existing MS maintenance plan
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
-
Hi All,
We just recently started using Red Gate SQL Backup. I'm still getting used to the features but one thing I'm finding is that the restore from Transaction Log can take an extremely long time (ran a restore on a 3 gig DB and it's still running today and I started it Friday morning). Full backups are taken nightly and Tran Log is backed up every 15 minutes. I was wondering if anyone here might have any product-specific suggestions I can try to get the restore to be done within a reasonable amount of time. I understand that this is very broad, but any help one could give is greately appreciated.
Thanks!
Nate
-
Nate,
Send a note to Red Gate Support on this. I'll ping them as well.
-
Hi All,
Got a response from Red Gate which I included below since it's got some decent info in it. As for my particular case, it turned out the 3rd party tool we use to report on disk space didn't match up to what SQL Server was seeing. So, while I thought I was dealing with a very small Tran Log, it was actually quite large (13 gigs). So, a simple shrink operation followed by a full backup and subsequent Tran Log backups did the trick for a much faster restore.
Here's what Red Gate had to say:
"There are a couple of issues with restore jobs not reporting an error correctly which has been addressed in our latest release SQL Backup 5.4. You can obtain this update by using Check for updates in the SQL Backup Help menu.
You can check the status of the current restore by executing the following command in SSMS/QA :
exec master..sqbstatus
We have the following article regarding long running restores which you may find useful :
http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=knowledgebase\SQL_Backup\KB200806000267.htm"
Hope that helps someone else!
Thanks,
Nate
-
Thanks for the update and glad they got back to you.
Viewing 15 posts - 16 through 29 (of 29 total)
You must be logged in to reply to this topic. Login to reply