Hardware requirements
- Min. 4GB ECC RAM
- 64-bit x86 processor
- Primary disk should be flash storage (>32GB)
- Legacy boot (UEFI is currently not supported)
- Cache disk for RAID or cloud storage should be SSD/NVMe (>32GB)
Download for Hyper-V, VirtualBox
Usage instructions:
- With Hyper-V setup a Generation 1 VM (no UEFI support)
- Decompress, then attach downloaded virtual hard disk as primary (boot) disk to a newly created virtual machine
- Attach other cache or storage (virtual) disks to VM
- Boot VM and browse to VM IP (via http) and follow the setup instructions
Download for VMWare
Usage instructions:
- Decompress, then attach downloaded virtual hard disk as primary (boot) disk to a newly created virtual machine
- Attach other cache or storage (virtual) disks to VM
- Boot VM and browse to VM IP (via http) and follow the setup instructions
Download for Bare Metal
Usage instructions:
- Decompress, then write image to primary disk via e.g. dd (Linux) or Win32diskimager
- Boot from primary disk
- Browse to server IP (via http) and follow the setup instructions
Install to Cloud Instance (DigitalOcean/Vultr/GCE/…)
Usage instructions:
- Create a new Debian 11/buster instance satisfying the minimum hardware requirements above (4GB RAM, >32GB disk, preferably second disk with >32GB). All data on the instance will be destroyed, so make sure you are really using a new instance
- Login as root via SSH and run:
wget https://dl3.infscape.com/images/urbackup-app-11-25.sh && bash urbackup-app-11-25.sh
- The script will download and install the appliance, then reboot. Copy & paste / note down the login password shown during installation
- If the installation is interrupted, you’ll have to destroy the instance and start with a new debian instance to retry
- Browse to http://INSTANCEIP or http://INSTANCEHOSTNAME and follow the setup instructions. As a first step you’ll have to enter the setup login password that the setup script shows
While this installation method is simple it might not always work (it replaces an operating system that is currently in use). As an alternative if your VPS provider allows booting into a recovery Linux system and you have some Linux knowledge the system can also be installed as following:
- Reboot into the rescue operating system
- Make sure dependencies are available. On Debian based operating systems e.g. by running
apt install wget zstd
- Download the appliance image to the operating system disk. Make sure the disk name (in the example /dev/sda) you are using in this command is actually the operating system disk (e.g. via lsblk).
wget "https://dl3.infscape.com/images/urbackup-app-11-25.img.zst" -O - | zstd -d -c > /dev/sda
The command can be re-run if it fails mid-way. - Remove the rescue operating system and boot to the installed operating system
- Browse to http://INSTANCEIP or http://INSTANCEHOSTNAME and follow the setup instructions. Unfortunately the appliance is not protected by password initially, so do not connect the appliance to the Internet before you have finished setup
Amazon Web Services
Usage instructions:
- The appliance is available on the AWS Marketplace
- Detailed step-by-step instructions (including setting up a S3 bucket) are available here. If you are okay with (temporary) non-secure access you could skip the step where a CloudFront distribution is setup and directly access your instance via IP/hostname.
- Create a S3 bucket. Setup an IAM policy that allows Read, Write, Delete and List on that S3 bucket
- Create a EC2 instance using the image from the AWS Marketplace. System disk should be at least >32GB (better 64GB), with a second disk with at least >32GB (better >64GB) attached. The second disk will be used as cache for S3
- Open TCP ports 80, 443 and 55415 during configuration
- After starting the EC2 instance enter the instance id (shown e.g. in the AWS console) in the first setup step
Microsoft Azure
Usage instructions:
- The appliance is available on the Azure Marketplace
- Create a storage account and a blob storage container in this account
- All attached disks will be used as Azure Blob Storage cache. Make sure to attach at least 64GB. Instance storage will be automatically used
- During creation specify a username and password (not a ssh key)
- Open TCP ports 80 (HTTP), 443 (HTTPS) and 55415 during creation
- Assign a hostname to the VM after creation (e.g. *.westeurope.cloudapp.azure.com)
- Browse to the hostname. As a first step the appliance will enable SSL. In the second step it will ask for the username and password specified during VM creation
- The third step will ask for the storage account name, a storage account key and the blob storage container name. The appliance will store all data into this blob storage container