Backup & Disaster Recovery specification

Infrascale Backup & Disaster Recovery allows you to:

• automatically back up data from computers and servers;

• restore the required versions of the backup data;

• retain backups for unlimited time; and

• boot Disaster Recovery (DR) image and virtual machine (VM) backups as VMs running on the Backup & Disaster Recovery appliance.

Specifications of physical appliances

Please see the updated individual section that covers all supported and EOL models.

Specifications of virtual appliances

Requirements for running on third-party hardware

Sizing examples

Deployment and replication configurations

Appliances can automatically send data to another location. Secondary appliance is always passive, meaning it accepts the replicated data from the primary appliance, but cannot back up extra endpoints.

Security and disk encryption

Hard disks in the primary appliances (those located on the customer’s premises) can be encrypted using LUKS,—an industry standard hard disk encryption system built into Linux.

Hard disks in the secondary appliances (those located in the Infrascale data centers) are encrypted by default using the AES-256 algorithm.

Learn more about the appliance disk encryption.

Transfer of data to the cloud is performed over AES-256-encrypted connection.

Data center security

We use Tier 3 and Tier 4 data centers. These are certified under SAS 70 Type II and SSAE 16, secured with video surveillance 24×7 and biometric access controls to limit physical access to the data center floors. All servers are security-hardened before deployment, patched, protected with antivirus software and firewalls.

Protected environments

VMware, Hyper-V, and physical machines

For browsing and restoring, Infrascale Backup & Disaster Recovery supports ext2, ext3, ext4, XFS, Btrfs, FAT16, FAT32, NTFS, UFS, HFS, HFS+, JFS, ReiserFS, MINIX (1.0, 2.0, 3), exFAT, NILFS2, and F2FS file systems on both MBR and GPT partitions, on the software or hardware RAIDs, or on the dynamic disks in Windows. ZFS was not tested. Windows Storage Spaces, Reiser4, and ReFS are not supported for browsing and restoring.

Virtual machines in Xen environments

Backup of a VM running on Citrix XenDesktop or XenServer can be performed with the DR backup agent installed in the VM. Boot on the appliance or restore to a Xen environment of a DR image backup is not supported.

Citrix NetScaler VPX appliances running on VMware or Hyper-V can be backed up and restored. Boot is not supported at the moment.

Backup schedules

Schedules support monthly, weekly, daily, hourly, by day of week with per-minute granularity backups.

Backup data retention

For backups of VMware and Hyper-V VMs, you can set retention to keep all backups up to 14 days, one per day up to 14 weeks, one per week up to 1 year, one per month forever.

For file and folder and DR image backups of physical machines, you can set for how long to keep full, differential, and incremental backups.

Backup retention is set separately for primary and secondary appliances.

Learn more about backup data retention.

Monitoring and reporting

Appliance sends alerts and reports via email about the following events:

• Backup and restore: VM automatic registration report, job success or failure, lack of job progress, daily and weekly summary.

• Security audit: User login notification and daily summary.

• System: New update available and system settings were changed.

• Replication: Failure, communication failure, summary report.

• License: Communication failure, violation, license warning.

In the Infrascale Dashboard, there is a backup monitoring section for all appliances of the account with email notification and integration with ConnectWise Manage and Autotask PSA.

Integrations

• ConnectWise Manage (billing, ticketing, Dashboard embedding, asset (appliance) tracking)

• Autotask PSA (ticketing)

Deduplication file system

We use proprietary technology called deduplication file system (DDFS). All data is split in 64K-blocks, and only one unique instance of each block is stored on disk. We calculate the number of all instances in the entire stored data per each block.