Blog Post

Exchange Team Blog
1 MIN READ

VSSTester script updated – troubleshoot Exchange 2013, 2010 and 2016 database backups

The_Exchange_Team's avatar
The_Exchange_Team
Platinum Contributor
Jul 28, 2016

Just wanted to let you know that the VSSTester script has now been updated to version 1.2. The main feature in this version is that the script now supports Exchange 2016 servers.

To read more about previous update see this, or for much more comprehensive information about the script, see the original blog post here.

Matthew Huynh

Updated Jul 01, 2019
Version 2.0
tips 'n tricks
tools
troubleshooting

5 Comments

  • Deleted's avatar
    Deleted
    Jul 28, 2016
    If you are taking database backup's you're doing it wrong. #ThePreferredArchitecture
    • Deleted's avatar
      Deleted
      Jul 28, 2016
      Love your thinking. :)
      • Deleted's avatar
        Deleted
        Jul 28, 2016
        Lagged database copies are all very well, if you have SLAs that specify that data deleted more than a few weeks ago will not be recoverable and you don't have legal reasons to need to be able to restore a given mailbox to a particular point in time. Every time we've been asked to restore a mailbox it's been from months ago, maybe because a user left under a cloud and an investigation is taking place; maybe they left and came back again. Touch wood, we haven't needed to restore because of system failure but we HAVE needed to restore for various "layer 8" reasons.

        One size does NOT fit all and saying backup is wrong is way too simplistic.