Neural cloud backup utilises data differential technology to ensure that only changed data blocks are copied up to your service during a backup operation. This significantly decreases the time and bandwidth required to perform a backup.
When utilising such technologies, the only time the full dataset is transferred is on the first backup operation. In some cases, where there is limited upload bandwidth or a large amount of data to be backed up, it may be preferred to ‘seed’ this initial backup by sending the data in on a USB hard drive, or other backup media.
The following process guide is intended for technicians and engineers and a comprehensive understanding of backup processes, backup software, networking and system administration is assumed.
Data Seeding Process
Configure your backup software and perform any applicable test functions to confirm the connection is successful.
Setup instructions can be found in the cloud backup webApp.
Disable automatic backup and scheduling features of the software relating to the cloud backup job. This should remain disabled until later in the process.
Step 3 (optional):
If the data being backed up is confidential, contains financial or medical records, or is otherwise sensitive, it is strongly recommended that you create an encrypted data file in which to store the data utilising TrueCrypt (www.truecrypt.org)
Please be sure to send the key separately via e-mail to support.
Complete the data post-in form
(Link to the document is available at the bottom of this article)
Using appropriate packaging and registered post, send the backup media to:
ATTN: BACKUP MEDIA
PO Box 12234
George St, Brisbane QLD 4003
Your backup data will be processed by Neural and you will receive e-mail confirmation when this is complete. Do not proceed to the next step until you have received this confirmation.
Configure the backup software to enable scheduling. Monitor the results and confirm the backup operation succeeds. Confirm that the backup software does not attempt to do a ‘full backup’ – it must be set to perform an incremental, or ‘standard’ backup.
Run a test restoration on non-production data, to a test restoration location. If the backup software supports it then testing of granular (such as a single file) restoration testing may be used.
Your backup seed and configuration is now complete. Subsequent scheduled backups will be performed using incremental differentials, so only changed data will be copied across your connection.