Does this mean the other 98% of servers remain untested from a recovery viewpoint? Unfortunately, this is the case in many enterprises today. Lack of resources, tools, budget cuts.
In many case we even learn “competence centres” (silos) cause serious compliance risks: To test recovery of Environment X from the TSM backup requires Mr. Backup, Mr. AppOps and Mr. AppOwner. Hence, the recovery-assurance test - too tedious and cumbersome - isn’t happening. Possibly, the snowball has begun rolling.
Why the SMARTtsm tool ?
Because that’s what SMARTtsm is – a TOOL, not a manual process. The software automates full-server recovery tests. It auto-executes every day, week, month …. SMARTtsm auto-reports compliance. Just define the recovery frequency. SMARTtsm documents recoverability – AND actual Recovery Time (RTO)!The built-in integrity wizards even help Mr. Backup check integrity of TDP backups. With no knowledge of the application running on the server to be recovery tested.
The new hero – the SMART TSM admin
Imagine a TSM admin schedule a full Exchange recovery test from TDP backup – every week! No intervention, just checking the recovery report. Set ‘n forget recovery testing of 100s of servers onto a dissimilar test platform.
We expect this is why ‘compliance-is-a-must” institutions like finance/banks and state/public sector are testing the SMART way. No reason to conceal when SMART can reveal faulty backups before the fatal IT event, where you are required to execute a full server recovery from TSM.

0 kommentarer:
Post a Comment
Note: Only a member of this blog may post a comment.