Secure data, images, and more with qt4-fsarchiver

Backing Up Over a LAN

Qt4-fsarchiver makes it possible to perform complete backups on computers sharing an LAN. However, this only works if a Samba client has been installed on the system that you want to back up. This is because the target machine should be either a Windows computer or a Linux system where the virtual filesystem CIFS VFS allows access to the directory. It is also necessary to create access to a suitable destination directory for the backup.

If the prerequisites for backing up a remote computer on the LAN are met, you should then call the routine for performing the backup via Actions | back up partition on a network .

The software will automatically check for accessible devices on the network and present a short dialog for authentication at the destination computer. Subsequently, the qt4-fsarchiver mounts the accessible device, and then it presents the same dialog used for local partition backups.

Images

Qt4-fsarchiver can also clone complete hard drives and SSDs. To start this action, click on the clone hard drive, create/restore hard drive image entry in the Actions menu. The subsequent window will display the bulk storage devices that are actually available. You now select the hard drive or SSD to be cloned, enter the destination drive, and then click in the lower left of the window on the clone hard drive button.

If you want to create an image file of the data of a bulk storage device, you can activate the radio button create a hard drive image found in the same window. Then, select the source drive and the file path where qt4-fsarchiver should deposit the image.

Now you should click at the lower right on create hard drive image . By selecting the restore hard drive image option found in the same window, you can restore the existing image onto bulk storage.

The corresponding dialogs do not permit any other options, such as selecting the number of processor cores or encryption mechanisms. However, the program compresses the image by default (Figure 5).