Datastore365 - Secure Online Backup 

Frequently Asked Questions

Why backup?
How is the first backup done, given that there will be a lot of data?
Is software installed on any other machines?
What access permissions does this user require?
What level of granularity is possible in setting up the backup, i.e. file level/individual database?
What frequency of backup can be set?
Can the software be set to stop backing up after a certain time has elapsed?
How many versions of my backed up files are held offsite?
What happens if a server stops or crashes during backup or if the backup is interrupted for some other reason?
What platforms are supported?
Can the software backup Permissions on files?
If the software is agentless, how is MS SQL and Exchange backed up?
Can Datastore 365 run pre and post commands on servers?
How does Datastore 365 handle open files?
How and to what standard is the data encrypted?
What is delta blocking? How does it work?
Does all of our data get transferred every day?
At what point is the data deemed to be backed up and offsite?

Answers

Think of backing up as your insurance policy. How much business-critical information is held on your pc or laptop? If you lost all this information what impact would it have? Online backup protects you against lost data as a result of fire, theft, flood, corruption not mentioning software and hardware failures. Datastore365 will enable you to quickly and easily retrieve you valuable data in case of emergency.
For large data volumes, the initial backup may be done to a portable disk, backing up at LAN speed. When the full backup of your data is complete, the disk is transported back to Datastore365's off site Data Centres. Future backups, which are purely incremental, will be transmitted via the Internet connection and synchronised with your initial backup data at the Data Centre.
The Datastore 365 DS-Client backup software is totally agentless, requiring no additional software to be installed on any machines to enable backup, be it Novell® NetWare, Windows Microsoft® NT/2000/2003/XP, SQL or Exchange.
This user is responsible for backing up and restoring all the data on your network, it is essential that access permissions are of administrative equivalence. The Datastore 365 DS-Client can only backup data that this user can access. A less privileged user may be restricted, causing data to be missed.
A backup set can include a whole server, share/volume, directory or even a single file. The backup set could even include just a registry, should you desire.
The backups can be configured as often as every hour or as infrequently as once a year. More advanced schedule options include the last working day of the month or even one off backups on a particular date.
Yes, the software is designed to fit specific backup windows. The Datastore 365 DS-Client can be told what time to stop at, for example at 8:00am when employees are starting to arrive, or maybe by 5:00am if there is an important batch process to run.
By default, 30 versions of each backup are held. Unlike a tape backup, where the routine is to rotate tapes in a cycle, Datastore 365 will only backup a new version of a file when it has changed, guaranteeing that the client is not wasting space backing up exactly the same version more than once. For example, if a file only changes once a month, we will have 7 months worth of that file. The number of versions stored can be configured on an individual backup set basis. Each backup set can be configured down to include just one file if desired, giving you the ability to maximise the efficiency of the storage.
If the backup is stopped, for whatever reason, it will simply continue onto the next backup in its schedule. It will not revisit the failed backup set until the next time it is set to run, e.g. the following night, at which point it will pick up where it left off. If however the problem has been rectified, and backup window allows, the backup can be restarted manually, immediately. Datastore 365 has a dedicated team who monitor the progress of backup once a week . If a problem occurs, it will be escalated through the appropriate channels.
Datastore 365 has full agentless support for a range of network platforms: NetWare 3 facilities include the ability to backup the bindery, where NetWare 4 and 5 include support for NDS. Windows 2000/2003 is fully supported. Basic workstations and servers can have the registry backed up, where more advanced environments will take advantage of being able to backup MS SQL and Exchange, without the need to stop the service or install an agent. Datastore 365 provides full support to backup workstations operating Windows 95/98/XP & 2000 and its registry.
Yes, for Windows NT/2000/2003 on NTFS volumes Datastore 365 can backup both Permissions and Streams. The Permissions and Extended NetWare Attributes can be backed up for NetWare. This is a configurable option in both NetWare and Active Directory environments.
Microsoft® developed SQL and Exchange with the backup requirement in mind. Both products can respond to API calls requesting the services to dump their data, whilst online, to an external destination. In Datastore 365's case the product simply asks the specified MS SQL or Exchange server to stream the data to the Datastore 365 DS-Client where it is delta blocked and transmitted offsite. This process is a totally supported Microsoft function and guarantees compatibility with your existing MS systems. This adhesion to Microsoft standards does however prevent us from restoring individual Exchange mailboxes as this is not a function Microsoft have ever supported.
Yes, even though Datastore 365 is an agentless solution, it is still capable of running commands on remote servers, be it NetWare or NT/2000/2003. For example, shutting down a database or application running on a server to back it up correctly and restart afterwards, or perhaps interact with some overnight batch processing.
Open files are an issue in most backup environments. If a file is open exclusively on a workstation, it is the server´s responsibility to stop anyone else, including a backup package, accessing that file. To help counteract these issues Datastore 365 has a range of options which attempt to handle open files. These options, combined with use of the Pre and Post commands, should enable the backup of almost any file. More complex environments such as Oracle or Sybase can usually be configured to dump their data into a normal file which will be delta blocked and backed up as normal.
The small files and delta blocks of data are first compressed and then encrypted with AES encryption using a key which is set by the client during the installation of the DS-Client. This key is unknown to Datastore 365 and the data remains encrypted at all times, even when stored offsite. The backup data is only unencrypted by the Datastore 365 DS-Client at your site when it has retrieved the encrypted data from Datastore 365 Data Centre for a restore.
Delta blocking is an advanced logic that divides all files into 4K blocks. When the file is detected to have changed, the Checksum of each 4K block is compared against the last known Checksum for the same block of the same file (stored in the database on the Datastore 365 DSClient server). Any blocks that are different are pulled out to be re-transmitted. These delta blocks will also be compressed and encrypted before transmission
Only new and unique data will get backed up. Duplicate or unchanged files will not be transmitted.
The data is backed up in real time, so when the administration console indicates that the backup is complete - it is also an indication that the backup data offsite.