In order to backup onto an external hard drive, the correct identifier (e.g.: /dev/sdb1, /dev/sdc1) for the job definition must be entered. The simplest way is to call up the identifier using the 'restore' tab in the connected (not the mounted) drive. Provided the drive is connected, the identifier will be visible under 'External device' (in our example: /dev/sdb1).
A new backup can now be created under 'Jobs', by entering the identifier under 'External device'.
Note: Provided that an entry exists under 'external device', the backup will immediately be executed onto an external hard drive. If the entry is inconsistent, the backup cannot be executed; this is then reported in the log file.
Note II: The two options 'stop' and 'cluster' are available under 'mode'. The 'cluster' option allows backups to be created in clustered servers (a minimum of two ArchivistaVM servers). An instance to be backed up on the first node ends up on the last node, all remaining instances end up on the previous node. Here it must be ensured that the hard drive is connected to the correct node. For example: If an instance to be backed up onto the first node of a double cluster ends up on the hard drive of the second node; this suggests that the hard drive connection to the first node is non-functional.