This final recovery scenario is a bit of fun, designed to show off your creativity and push the boundaries of what\u2019s possible. We want to see what recoveries can be achieved with some \u201cout of the box\u201d thinking. <\/p>\n\n\n\n
So, we know that there are three main pathways for recovery, as you\u2019ve seen in the previous recovery challenges. <\/p>\n\n\n\n
What else can we do? <\/p>\n\n\n\n
That\u2019s why we created an \u201cExtreme\u201d category \u2013 for anyone who can use non-standard methods to do a successful recovery. <\/p>\n\n\n\n
What can be considered extreme? It\u2019s up to the creativity of each challenger! My definition is something that\u2019s \u201coff the beaten path\u201d, such as a combination of: <\/p>\n\n\n\n
Contents <\/p>\n\n\n\n
By the time I did this challenge, I had already done a few recoveries, so I had got my times down to a minimum. <\/p>\n\n\n\n For the BackupAssist ER Challenge Leaderboard, my hands-on time is 2 minutes and 40 seconds. <\/p>\n\n\n\n Here\u2019s the video of me doing it: <\/p>\n\n\n\n\n \n
\n Task<\/b><\/td>\n Duration<\/b><\/td>\n <\/tr>\n\n \n Hands-on with BackupAssist ER<\/b>
– Creating a bootable Lifeline Media ISO
– Booting the Lifeline Media, and starting the recovery<\/td>\n 2 min 40 sec<\/td>\n <\/tr>\n\n \n Waiting time <\/b>
– Waiting for Lifeline Media to be created
– Waiting for data to be copied from backup to the recovery machine.
– Waiting for the recovery machine to boot and detect new hardware, and get to the login screen. <\/td>\n 22 min 37 sec<\/td>\n <\/tr>\n\n \n Total time <\/b><\/td>\n 25 min 17 sec<\/b><\/td>\n <\/tr>\n <\/tbody>\n <\/table>\n<\/figure>\n\n\n\n