I don't see an option to do that. Log backups would be read sequentially anyway so i do not think it would help.

If you have the correct version of SQL...

norecovery option would have to kick off connections as well.

You would need a lot of uncommitted transactions I would say before getting a noticeable degradation in restore time.

If by latency...

LSN information is also listed in the backupset table referenced in the query above

or you could check the restore history.......

--returns info on when databases were restored and from which backup file

SELECT [rs].[destination_database_name],

[rs].[restore_date],

[bs].[backup_start_date],

[bs].[backup_finish_date],

[bs].[database_name] as [source_database_name],

[bmf].[physical_device_name] as [backup_file_used_for_restore]

FROM msdb..restorehistory rs

INNER...

nope, you can restore db with recovery to bring it online without restoring any further files, but you cannot reverse that with the norecovery clause.

Using norecovery you need to supply...

its just a setting in the log shipping gui and affects the next restore. You can flip back and forth as you require.

I can't see it having an affect...

if the database is restored in a recovered state there is no way to use the transaction logs to roll it forward from that point.

iirc = acronym for 'If I Recall Correctly'

File expire will not delete the files. Choose backup to disk, choose a folder

then add another task using a maintenance cleanup task to...

krypto69 (6/11/2013)

---

Thanks George..

I created the Maint plan for the log.

It did create the trn file the same size as the log, but it did not shrink the log. Is...

OK, then Unitrends is probably not doing log backups. run this whilst connected to your database, if no rows returned there are no log backups

declare @dbname sysname

set @dbname = db_name()

print...

no sorry I need this to see the recovery mode of your database unless you happen to know it

select recovery_model_desc from master.sys.databases where name = 'your database name here'

ok so looks like you are already getting full backups taken Mon to friday at 7pm or so plus some other adhoc ones.

I still need the result from the other...

start further back and work your way forward in chunks, that SP is cursor based and can be slow and intrusive.

whether 60 days is enough only you can really tell...

are you backing up across the network? Looks like a network glitch to me (error 64), it says it in the error message.

I wouldn't trust the backup without a test...

what does this command return?

select recovery_model_desc from master.sys.databases where name = 'your database name here'

Is this unitrends tool taking any sort of backups at all that you could restore?

run this...