Backup / Disaster Recovery
What would be your loss - if the worst comes to the worst
Whether it's a virus, a hacker attack, a natural disaster (such as a flood or earthquake), sabotage, hardware failure, theft, human error, or other external influences:
When IT goes down, almost everything stops today. From the Internet via the mail server and the merchandise management to the telephones and the production (if computer-controlled). The question is: how long?
There are essentially two decicive factors.
How old is the last useful backup? If, for example, it is from the evening before, there are already several man-hours available to carry out the work that has been done since. With 20 employees working on a computer-based basis, 100 hours or more will quickly come together. And what about the emails (possibly inquiries, orders, or important contract documents) that came in between the last backup and the failure?
In our solution, the last useful backup can be minimal 15 minutes ago. It is therefore possible to make an incremental backup at the sector level every 15 minutes without interrupting the ongoing operation. With 20 employees this would mean a "follow-up time" of 5 hours. However, it should also be taken into account that the employees probably still know very well what they have done in the last 15 minutes. Whether they manage this completely for half a day, may be doubted.
How long does it take to get the system up and running again? (Here the values can be in the hourly, daily or weekly range.) In the case of the failures after the hacker attack on the computers of the German Bundestag or the attacks on the EDP of various German hospitals the downtime went even into the monthly range). There are even backup solutions where the server operating system must first be reinstalled, before the backup tape can be tediously downloaded. This is no longer sensible in SMEs.
In our solution, restoring a server system can be in the range of minutes (assuming the backup is on-site). The whole thing is realized by recovery technologies like "VirtualBoot" and "HeadStart Restore". This will boot the image created by ShadowProtect in a virtual machine. In this way, it is also very easy to check whether the backup is not only on the plate, but also really works in an emergency. Do you know this with your current solution? You would not be the only one who assumed for months or even years to have a working backup, in case of an emergency, during recovery, but to find that it was defective
So it's worth tackling the "Disaster Recovery Plan" theme and "practice" the scenario in times of need. We will help you.
On all servers (Windows or Linux) "ShadowProtect" should be installed.
During productive operation, an incremental image of all volumes should be made at least once every hour.
The backup should be on the release of an internal SAN or NAS (RAID) to which only the BackupUser has write access.
With the "ImageManager" (free of charge), the image chain should be checked regularly and the images should be consolidated.
With "ShadowStream" the images should be replicated to a second location (for example to Santa Cruz Video Security LLC).
In addition, it is recommended to have a system environment for "VirtualBoot" and "HeadStart Restore" for faster recovery. In addition, with "ImageControl" (free) you can centrally manage backups/images if you are responsible for restoring many servers.
For consultation or a free trial of ShadowProtect call 831-428-3438.