A single full backup is made initially, then incremental backups are scheduled to run automatically at agreed daily, weekly and monthly times based on the data volumes and data changes involved. Your data is backed up to a TimeVault-internal filesystem. This backup filesystem will appear as regular TimeVault consumption in your monthly account, though you will not have direct access to it.
TimeVault backups are retained daily for 7 days, weekly for 4 weeks, monthly for 12 months, and annually for the life of your TimePlan; recognising that the more recently data changes, the more granularity of restoration checkpoints is needed. Intersect regularly monitors all TimeVault backups to confirm they are completing successfully and within the time allocated for them to run.
TimeVault works with the internal storage of all OwnTime virtual machines. Technically this means any OpenStack virtual machine that can expose attached ephemeral block storage as an NFS mounted filesystem. TimeVault is a companion to, but different from SpaceVault, designed to backup generic Space collections.
TimeVault makes an exact copy of anything in an OwnTime attached filesystem. But not everything can survive; binary data from active databases and applications typically requires manufacturer recommended/supplied export tools. We recommend you to use them to prepare database dumps and application exports and include these in your data collection for backup. If in doubt, please get in touch for advice.
Source and Backup size
You can set up TimeVault to run on any number of OwnTime VMs. There are some pragmatic constraints: standard backup sources can be up to 20 TB in size, and contain up to 2 million files. If your filesystem is larger than these thresholds, you may need to split it into logical sub-sources. For data volumes significantly larger than these thresholds, a custom solution will be required; please get in touch and we’ll work through this with you.
Backup size depends on a number of factors including filesystem size, the frequency of backup, the retention period, and how much data changes over time. TimeVault backup technology helps minimise overall storage consumed by hardware compression, incremental copies, and software optimisation.
Backing up small files
Files can range from 0 bytes up to any size, though practical maximum file sizes will apply. If you have large numbers (order 100,000+) of small files (order 10KB in size) we strongly recommend these be compressed and aggregated into zip or archive files.
How does TimeVault determine if my data has changed?
TimeVault uses file metadata to determine if your files have changed, typically file creation date and file modification date. If you require a different mechanism, for example based on data checksums, you will need a custom solution: please contact us for advice.
TimeVault uses administrative privileges to copy your data. Due to the heterogeneous nature of cloud computing and storage, backed-up file permissions are not guaranteed to be maintained post-restoration. Specific arrangements may be accommodated if possible.