Asigra backs up files through a gathering and distribution local data-collector server called DS-Client, which resides on a local network and is controlled by an application called DS-User.
Asigra backs up files through a gathering (backup) and distribution (restoration) local data-collector server called DS-Client, which resides on a local network and is controlled by an application called DS-User.
The DS-Client master backup server, called the DS-System, is controlled by yet another application called DS-Operator.
DS-Operator manages DS-System and also performs system accounting (such as charging accounts for disk storage, creating limits on storage, bandwidth throttling by clients, and other administrative features). DS-Operator’s features are handy to internal IT departments that charge for their services, as well as third-party backup service providers.
Overall, this method was slower, because there were no clients on the machines that would do optimization and caching, but the product relies on the operating system’s algorithms. In addition, network traffic is higher because there is no compression.
DS-Client runs on various platforms, but the choice of the platform is important. Because DS-Client will pull or push information based on its ability to log on to a server or user machine, its capabilities must match those of the intended server or user machine. For example, when DS-Client is hosted on a Windows machine, it can back up Server Message Block — Microsoft’s early network connectivity methodology — or SAMBA-connectable machines through standard SMB user name-password combinations.
DS-User doesn’t load agent software on a client that needs backup-and-restoration services. Instead, DS-User sets up the DS-Client application to log on to a user’s machine or a network server using standard network credentials specific to the machine or server under control. Backups or restorations then are authenticated with encryption methods that vary from Data Encryption Standard, to Advanced Encryption Standard (AES) (128-, 192- or 256-bit). The encryption keys are stored — dangerously — on the client, if they aren’t remembered during stressful situations, data will be lost forever. Fortunately, there’s only one key per client server.
Also, we found that although Asigra says its product easily allows for bare-metal restoration, we found the process difficult, because the initial operating-system files must be placed on a crippled server or workstation before a restoration mission can begin.
In terms of reporting, this system keeps detailed (but not file-level) records of each transaction and keeps a system-event log (which tracks logons and connection openings and closings). We could view the logs easily, but found no way to export the logs to a file format.
Televaulting requires that more initial administrative time be spent upfront to populate user credentials and assign backup sets and perform traffic management for backups. On the plus side, it has good security.
