You can do a point in time recovery to Oct 5th if you have only full backups and a last transction log backup (called a tail log backup). Your transaction log backup contains all transactions back to the last log backup. So that should be sufficient to do a point in time recovery.

That you are getting the message "transaction log does not contain the point" indicates one of the following:

• There were other transaction log backups taken before your last transaction log backup.
• The database was Simple recovery mode somewhere between the 1st and the 23rd of October.

The reason your transaction log is so big is that it was not backed up regurarly. As transactions happen, the log grows. A transaction log backup truncates your transaction log, and then the empty space can be used for new transactions. The reason can also be that there was a big amount of data modified.

Recommendation: regurarly backup your database (for example every day) and your transaction logs (at least every hour or even more often, depending on the activity in the database). Keep those backups in a safe place. Then you will be able to do proper point in time recovery.

You can do a point in time recovery to Oct 5th if you have only full backups and a last transction log backup (called a tail log backup). Your transaction log backup contains all transactions back to the last log backup. So that should be sufficient to do a point in time recovery.

That you are getting the message "transaction log does not contain the point" indicates one of the following:

• There were other transaction log backups taken before your last transaction log backup.
• The database was in Simple recovery mode somewhere between the 1st and the 23rd of October.

The reason your transaction log is so big is that it was not backed up regurarly. As transactions happen, the log grows. A transaction log backup truncates your transaction log, and then the empty space can be used for new transactions. The reason can also be that there was a big amount of data modified.

Recommendation: regurarly backup your database (for example every day) and your transaction logs (at least every hour or even more often, depending on the activity in the database). Keep those backups in a safe place. Then you will be able to do proper point in time recovery.

You cannot do a point in time recovery to Oct 5th if you don't have backupped the transaction log before October 10th (your last full backup). Your transaction log backup only contains the transactions that took place after your last full backup (that from Oct. 10th).

The message you're getting indicates that the point you want to recover to is too early. That's because you need a transaction log backup that contains the transactions up to the point you want to restore to. So if you had made a transaction log backup between your full backups (lets assume you made it on Oct 7th), you could restore the full backup of Oct 1st and use the transaction log backup of the 7th for the point in time recovery.

The reason your transaction log is so big is that you did not backup it regurarly. As transactions happen, the log grows. A full backup truncates your transaction log, so your latest transaction log contains all the transactions from the 10th of October until the 23rd of October.

Recommendation: regurarly backup your database (for example every day) and your transaction logs (for example every hour). Then you will be able to do proper point in time recovery.

You can do a point in time recovery to Oct 5th if you have only full backups and a last transction log backup (called a tail log backup). Your transaction log backup contains all transactions back to the last log backup. So that should be sufficient to do a point in time recovery.

That you are getting the message "transaction log does not contain the point" indicates one of the following:

• There were other transaction log backups taken before your last transaction log backup.
• The database was Simple recovery mode somewhere between the 1st and the 23rd of October.

The reason your transaction log is so big is that it was not backed up regurarly. As transactions happen, the log grows. A transaction log backup truncates your transaction log, and then the empty space can be used for new transactions. The reason can also be that there was a big amount of data modified.

Recommendation: regurarly backup your database (for example every day) and your transaction logs (at least every hour or even more often, depending on the activity in the database). Keep those backups in a safe place. Then you will be able to do proper point in time recovery.