![]() |
|
|||
|
Proper Backups The general definition of "proper"
backups requires redundancy. One must keep multiple copies of the same
files at different points in their development, called versions.
As an example, you should have a different copy of each backed-up file
for each backup session. Further, you should be able to easily restore
any of your files up to any given point in time. Banks do it, big corporations
do it, and so should small businesses. Only Remote Backup has such an easy to use version control system. Backups are encrypted for complete security. Would you
want someone to be able to slip one of your backup tapes into a pocket
and take it to your competitor? It happens all the time. Tape backups
are not generally encrypted, so anyone can read them and gain access
to your client database, billing records, payroll, tax info, and everything
else on your computer. Remote
Backup encrypts its backups for
complete security so nobody, not even your Backup Service Provider can
read your files. Finally and most importantly - Backups are immediately
sent offsite and stored safely away from your computer and your business.
This is where almost every business makes its biggest mistake. Even
if you do everything else perfectly, your backups are of little use
if your building burns or you are unable to physically recover your
tapes from the premises. Most small companies who do backups leave the
tapes in the building with the computer, where they can be destroyed
right along with the computer. Of course, you can see that this would be a problem
in a fire or flood or an earthquake. But it's also useful in emergencies
where businesses are forced to evacuate their offices quickly. Even
businesses that do backups and have good, undamaged tapes have to shut
down. Many go out of business simply because they don't have access
to their data. Remote
Backup solves this problem by
automatically storing this valuable data at more than one site. So,
a business can be back up and running with new computers and their latest
data no matter what catastrophe happens.
|
![]() |