Forward and Backward recovery RRS feed

  • Question

  • Hi,

    What is difference between forward recovery and backward recovery? Can you give me example?


    Tuesday, October 14, 2014 4:58 AM

All replies

  • Backwards recovery can be thought of as simply restoring the last saved point. Forward recovery is often about starting from the last saved point and then applying transactions that are newer than the save point, i.e. you are now forward of the save point.

    Tuesday, October 14, 2014 9:17 AM
  • Thank you,

    Which software used backward recovery and which software used forward recovery?

    When we used in our software 'forward recovery' and when 'backward recovery'?


    Thursday, October 16, 2014 5:47 AM
  • There are different reasons for the choice, but typically a backward recovery will take some time to complete whereas forward recovery will normally be faster providing there are not a large number of transactions to replay. Hence why a recovery strategy will usually be a combination of both.

    Friday, October 17, 2014 10:28 AM
  • I need more details about these concepts.
    Saturday, October 18, 2014 7:27 AM
  • You need to ask a specific question otherwise the answer will be, 'use a search engine'.

    Monday, October 20, 2014 7:11 AM
  • Hi,

    Which software is used forward recovery? and which software is used backward recovery?

    • Edited by Arash_89 Tuesday, October 21, 2014 9:24 AM
    Tuesday, October 21, 2014 9:22 AM
  • You might want to look up CheckPointing.  SSIS\SQL has check pointing built in so you can restore from a specific point.  Check pointing seems like an overvalued functionality.  Large batch processes should check point, but in practice very few operational managers will attempt to recover from a check point.  They will just restart the entire process. 

    Replaying Logs from SQL can also get you forward.  This is why you can use Log Shipping for Disaster Recovery servers to be synced.

    • Edited by Brian Bu Tuesday, October 21, 2014 6:52 PM
    Tuesday, October 21, 2014 6:33 PM
  • As mentioned SQL Server will do both. In a highly transactional environment you would typically see a full (or incremental) backup taken on a regular basis, perhaps daily. However, that would potentially mean you would lose a whole days worth of transactions, which could be a disaster. Therefore you take very regular transaction log backups to enable you to replay them should a problem occur between the full backups.

    Wednesday, October 22, 2014 8:04 AM