User guide

acrocmd export archive --loc=bsp://ASN/my_vault --credentials="ASN user",pass1

--arc=my_archive --password=123 --target=\\bkpsrv\backups

--credentials=netuser,pass2

This command exports a password-protected archive from a managed vault to a network share. The

first credentials are required to access the vault my_vault managed by the storage node ASN. The

--password parameter specifies the password for the archive my_archive. The second credentials

enable writing to the shared folder \\bkpsrv\backups.

3.12.2 Error handling

--retry_count=<number of attempts>

--retry_delay=<delay>

These parameters are used with the backup and recovery commands only.

When a recoverable error occurs, the software re-attempts to perform the unsuccessful operation.

You can set the number of attempts and the time interval between attempts. The attempts will be

stopped as soon as the operation succeeds OR the specified number of attempts is performed,

depending on which comes first.

You need to specify both parameters. The --retry_delay parameter must directly follow the

--retry_count parameter.

Example: --retry_count=10 --retry_delay=20s

If the parameters are not specified, the number of attempts is 5 and the time interval between

attempts is 30 seconds (as if you typed --retry_count=5 --retry_delay=30s). To completely

disable re-attempts, specify --retry_count=0.

The interval may be set in seconds (s, by default), minutes (m) or hours (h).

Examples:

 10-second interval: --retry_delay=10 or --retry_delay=10s

 1-minute interval: --retry_delay=1m

 1-hour interval: --retry_delay=1h

3.12.3 file_params

{-f|--file_params}=<full local path>

Specifies the full path to an input parameter file. The path must be local (for example,

c:\temp\1.txt or /home/user1/1.txt). For more detailed information, see Syntax (p. 8).

3.12.4 force_yes

--force_yes

If the parameter is specified, the software will automatically handle situations requiring user

interaction as if the user answers Yes or OK to the interaction request. If the interaction request

does not imply these answers (for example, the possible answers to a reboot prompt are Reboot

and Cancel), the software will ignore this request. If an operation cannot continue without user

interaction, it will fail.