Hardware, Software and Other Requirements
Replibit recommends a minimum of 8GB of RAM and 4 CPU cores with support for Intel VT or AMD-V hardware virtualization. More RAM and CPU resources are recommended when protecting many systems, or if you plan to provide virtualization as a recovery option.
Typically, appliances should be built using high-end workstation or low-end server equipment depending on the target environment. Vaults should be constructed on low- to mid-range server equipment for performance and reliability.
Dedicated IPMI or other out-of-band management is recommended to ensure robust remote management options when maintaining your fleet of devices.
External IP Addresses (if you are hosting your own cloud)
Each vault and management portal instance running in your data center is an independent machine. Each of these devices will need their own dedicated Public IP address unless you are using a third-party VPN tunnel solution to route traffic from your customer appliances. Creating Public DNS records for each device is optional but recommended.
If you are using the Axcient cloud, these details will be taken care of for you.
- LAN: Ports 9090-10000 need to be open between the protected system and the appliance.
- WAN: Ports 443, 9080 and 9081need to be open between the appliance and the vault.
Ports 22, 443, and 10000+ need to be open between all appliances and vaults and the Management Portal.
- One port per managed device needs to be open above 10000. For example, if you have 50 appliances and vaults under management, you need to open ports 10000-10049.
Appliance and Vault Installation Requirements
- It is highly recommended that Axcient Replibit be installed on bare metal. Virtual installations are not supported or recommended for production environments. To install Axcient Replibit as a virtual machine, refer to the Deploying Replibit as a Virtual Machine article.
- Axcient Replibit offers the flexibility to select your own hardware or purchase pre-configured BDR appliances.
- Axcient Replibit BDR appliances provide exceptional performance and reliability using all FastFlash SSD storage and our patented Durabit data integrity system. BDR appliances can be specifically preconfigured for your customer location.
- It is recommended to use a single disk, or a hardware RAID-1 disk volume for the operating system. Protection of the operating system disk is not critical, as there is a recovery procedure to reload and restore all device settings from the storage pool.
- Unless you are using a SAN it is recommend to deploy three or more physical disks and use ZFS Software RAID when creating the Storage Pool. ZFS RAID is more robust than hardware RAID and Replibit has been optimized to provide disk failure and replacement of ZFS volumes.
- When using a SAN, you may opt to create a RAID-0 Storage Pool consisting of iSCSI LUNs. (The disk redundancy will be provided by the SAN.) For optimal performance, create a RAID-1 storage pool using multiple 10Gbe network adapters to provide access to the iSCSI disk volumes. Ideally, each iSCSI volume should be provided by a separate SAN server.
- DHCP should be enabled on the network when installing Replibit to simplify the startup network configuration of the device for licensing and initial software upgrade. During configuration or after setup has completed, a permanent static IP address should be assigned to the device so that Agents have consistent access to the device.
Best Practices for Agent Deployment on Windows
Completely uninstall other backup software and Reboot if possible
- Some legacy backup software, such as Backup Exec or Acronis may not completely remove their proprietary VSS extensions when uninstalled from Add/Remove Programs. It is recommended to use their stand-alone uninstaller utility if available to ensure proper cleanup and removal of these agents.
Search for Unknown Large File Creation
- Perform a search for files greater than 50MB created within the last 7 days. Verify that there are no ongoing large data dumps being performed on the server that can dramatically balloon the size of eFolder Replibit’s incremental backup images. Some possible examples to avoid: SQL Database backups; Quickbooks company file backups; PST File exports or copies, Windows Server Backup images, etc.
- If large file creation is discovered, alleviate the issue by disabling the source of the file creation, or retarget the file storage to a separate disk volume and then disable that volume from backup by the eFolder Replibit agent.
Verify VSS Settings
- From an elevated command prompt, run ‘vssadmin list shadowstorage’ Examine the volume shadow copy size column and verify that it is NOT set to UNBOUNDED
- The recommended default storage size is 10% of total space
- If less than 15% of the disk volume is free, it is recommended to redirect shadowstorage to another volume with sufficient free space.
- To modify shadowstorage configuration, run the following command
‘vssadmin resize shadowstorage /for=C: /on=D: /maxsize=3GB’
replace the source, destination and maxsize values as appropriate.
Customers and Locations
- When deploying eFolder Replibit to customers with multiple locations, create only one customer account within the License Portal and assign multiple locations to the account.
- Each customer location that has servers to be protected should have its own Appliance. eFolder Replibit does not recommend performing backup operations of remote servers over Intranet or VPN connections with less than 1Gigabit of bandwidth available.
Networks, Switching, and Routing
- Appliances should be connected to the same physical LAN and VLAN as the protected systems they are guarding. Avoid transporting data through firewalls or routers to alleviate network congestion and performance bottlenecks.
- Appliances and Protected Systems should be connected to 1Gigabit Ethernet switches or faster for best performance.
Backup Time Window
- Microsoft’s best practice recommendation is to increase the minimum configured backup window by 15 minutes for every TB of disk size. (Total volume size, not space in use.) For example, a server with 2TB in total disk capacity should not be backed up any more frequently than every 30 minutes.
Avoid Scheduled Defragmenting of Disks
- Performing disk defragment operations on systems protected by image-based backup solutions can generate unnecessarily large incremental backups due to excessive block changes. It is not recommended to perform frequent, or regularly scheduled defragmentation operations on systems protected by image-based backup solutions like Replibit
- Prior to installing the Axcient Replibit Agent, it is recommended to perform a thorough disk defrag of both regular files and the Master File Table, if possible. This will help ensure that the initial base image for the protected system is in a healthy state.
Microsoft Exchange and SQL Server VSS Agents
- The Exchange VSS agent is disabled by default on Windows Server 2003 SBS. Ensure that this service is set to Automatic startup and running in order to ensure consistent Exchange backups and log file cleanup.
- The Exchange VSS agent is set to Manual by default on Exchange 2008 and newer. Ensure that this service is set to Automatic startup and running in order to ensure consistent Exchange backups and log file cleanup.
- Verify that the Microsoft SQL VSS Writer service is set to Automatic and is running in order to ensure consistent backups of Microsoft SQL databases.
- Microsoft Windows systems distributed as OEM installations are not supported for virtualization. Many OEM distributions are deliberately crippled so that they will not run as a virtual machine.
- Virtualizing Microsoft OEM distributions is a violation of the Microsoft Licensing Terms and Conditions. eFolder Replibit will not provide support for virtualizing OEM distributions of Microsoft operating systems.
- Recovery of Microsoft OEM distributions to new hardware is a violation of the Microsoft Licensing Terms and Conditions. OEM distributions may only legally be recovered onto the original hardware on which it shipped. eFolder Replibit will not provide support for recovery of OEM distributions to replacement hardware.