SQL TLog restore slow / handling

[foggy]

Steffen, transaction logs can be applied to the backed up database state only, they cannot be applied to a more recent database state. If you describe your setup in more detail, we could check whether it can be optimized for faster restores.

[foggy]

This doesn't depend on the backup method.

[DaveWatkins]

Surely is the resotre is only going back a couple of hours, the last full DB backup is in the same state as the existing production DB (assuming a DB backup hasn't occured in the last few hours). Full DB backups only happen with a VM backup don't they, so it's very likely the existing MDF file is the same.

That would mean if you could stop the DB without committing the existing TLOG then you should be able to easily apply on the restored TLOG up to the transaction requested right?

[yunales]

also please beware when restoring SQL using the explorer it's very slow. Refer to this thread:
vmware-vsphere-f24/sql-restore-speed-t3 ... ml#p204440

If using the export to another folder it's much faster! Seems to be a bug.

regards

[yunales]

Your welcome. Also the tests with Veeam B&R9 U2 have better performance. It's still not as fast as the export but definitely some improvement was made.