Activity overview
Latest activity by freddo12345
Thanks for your response Brian,
so if i understand correctly, the log backups from log shipping are only useful, if i can supply the seed backup plus all the subsequent log backups from the past year or two. that would be thousands of log files... [image] i think that was why the UI was taking so long. but this is not practical.
or can you just pick a log backup file and tell it how far back to look?
and finally, our hourly backups are apparently not useful for restoring to a point in time, but obviously they are useful for a full restore.
thanks,
Fred
Brian Donahue wrote:
Hi Fred,
More than likely you will need log backups to restore to a point in time -- they pretty much are the way to go. Restoring a full or a differential can only allow you to restore your database to the point in time that the backup was taken. Only a log restore will allow you to restore only part of the file up until the point in time that you want the database to reflect.
You can perform full backups of a database while log shipping is going on, and these backups do not have to figure into your restore strategy. So say you performa a seed backup, restore that, and log ship, you can take full backups of the source without the need to restore them on the target, as they're totally independent, provided you don't truncate the log somewhere along the line.
It sounds to me that the SQL Backup Console performance is the issue rather than the backup strategy.
/ comments
Thanks for your response Brian,
so if i understand correctly, the log backups from log shipping are only useful, if i can supply the seed backup plus all the subsequent log backups from the past ye...
Restoring Transaction Log Backups...
Hi,
i think i know what's going on, but need to be sure. Thanks for any help here.
we do hourly full backups of our production database. we also have log shipping set up for this database, and do ...