Specify where the archive will be stored and the name of the archive.
1. Selecting the destination
Enter the full path to the destination in the Path field, or select the desired destination in the folders tree.
- To back up data to Acronis Online Backup Storage, click Log in and specify the credentials to log in to the online storage. Then, expand the Online backup storage group and select the account.
Prior to backing up to the online storage, you need to buy a subscription to the online backup service and activate the subscription on the machine(s) you want to back up. Online backup is not available in Linux and under bootable media.
Acronis Backup & Recovery Online might be unavailable in your region. To find more information, click here: http://www.acronis.com/my/backup-recovery-online/
- To back up data to a centralized vault, expand the Centralized group and click the vault.
- To back up data to a personal vault, expand the Personal group and click the vault.
- To back up data to a local folder on the machine, expand the Local folders group and click the required folder.
- To back up data to a network share, expand the Network folders group, select the required networked machine and, then click the shared folder. If the network share requires access credentials, the program will ask for them.
Note for Linux users: To specify a Common Internet File System (CIFS) network share which is mounted on a mount point such as /mnt/share, select this mount point instead of the network share itself.
- To back up data to an FTP or SFTP server, type the server name or address in the Path field as follows:
ftp://ftp_server:port _number or sftp://sftp_server:port number
If the port number is not specified, port 21 is used for FTP and port 22 is used for SFTP.
After entering access credentials, the folders on the server become available. Click the appropriate folder on the server.
You can access the server as an anonymous user if the server enables such access. To do so, click Use anonymous access instead of entering credentials.
According to the original FTP specification, credentials required for access to FTP servers are transferred through a network as plaintext. This means that the user name and password can be intercepted by an eavesdropper using a packet sniffer.
- To back up data to a locally attached tape device, expand the Tape drives group, then click the required device.
2. Using the archives table
To assist you with choosing the right destination, the table displays the names of the archives contained in each location you select. While you are reviewing the location content, archives can be added, deleted or modified by another user or by the program itself according to scheduled operations. Use the Refresh button to refresh the list of archives.
3. Naming the new archive
Once you select the archive destination, the program generates a name for the new archive and displays it in the Name field. The name commonly looks like Archive(1). The generated name is unique within the selected location. If you are satisfied with the automatically generated name, click OK. Otherwise enter another unique name and click OK.
If the automatically generated name looks like [Virtualization Server Type] [Virtual Machine Name], this means that the name contain variables. Such might be the case when you have selected virtual machines to back up. Virtualization Server Type stands for the virtualization server type (ESX, Hyper-V or other). Virtual Machine Name stands for the virtual machine name. You can add suffixes to the name but never delete the variables, since each virtual machine has to back up to a separate archive with the unique name.
Backing up to an existing archive
You can configure the backup plan to back up to an existing archive. To do so, select the archive in the archives table or type the archive name in the Name field. If the archive is protected with a password, the program will ask for it in the pop-up window.
By selecting the existing archive, you are meddling in the area of another backup plan that uses the archive. This is not an issue if the other plan is discontinued, but in general you should follow the rule: “one backup plan – one archive”. Doing the opposite will not prevent the program from functioning but is not practical or efficient, except for some specific cases.
Why two or more plans should not back up to the same archive
- Backing up different sources to the same archive makes using the archive difficult from the usability standpoint. When it comes to recovery, every second counts, but you might be lost in the archive content.
Backup plans that operate with the same archive should back up the same data items (say, both plans back up volume C.)
- Applying multiple retention rules to an archive makes the archive content in some way unpredictable. Since each of the rules will be applied to the entire archive, the backups belonging to one backup plan can be easily deleted along with the backups belonging to the other. You should especially not expect the classic behavior of the GFS and Tower of Hanoi backup schemes.
Normally, each complex backup plan should back up to its own archive.