Catalog the backup set.
Once files are encrypted, the catalog of files is updated, compressed and encrypted itself. The catalog information includes each individual file's details including it's original location, which archive file it is stored in, and more. This information is imperative in order to recover the file later.
Connect to the My Data Vault.ca server and transfer archive files and catalog.
At this point your backup is ready for transport. Users will connect via the Internet. The software will use whatever Internet connection you have and have specified during configuration.
If you have a fixed connection, the software will recognize the connection and use it. If you have a dial-up connection, the software will check to see if you are already connected to the Internet, and if not make the dial-up connection you specified. Your connection speed will determine how long it takes to transfer your data. This is only an issue if you have a very large data volume and a slow connection using a telephone line. Obviously this would tie up the line for the duration of the backup.
Once your machine is connected to the Internet, the software contacts the data server and performs a series of identification checks. When the server is satisfied that the machine is a My Data Vault.ca client and the account is in good standing, your data is transmitted to the server.
When the transfer is complete the software disconnects from the server. If your system was not already connected to the Internet when the backup event started, it will automatically close the dial-up connection.
Log backup event activity.
Once the transfer is complete, the software checks to see that all the files were successfully sent and builds a log of the session. If there was an interruption during the connection, any files that didn't get transferred are held until the next backup connection and all the others are deleted.
The logs include a detailed step-by-step description of each backup event. They can be checked at any time from within the software so you can easily track how much time and space your backup is taking.
Wait for next backup event.
After writing the log, the software looks for the next scheduled event and unloads all but the launcher until that time. When the backup is not actually in the process of working the software uses very little resources.. just a timer waiting to start the process again. |