Skip to main content

ARIS Technical Help

Manually restore installation

If the setup failed because prerequisites were not met, you must recover your ARIS installation and run the setup again.

Procedure. Procedure

  1. Check the tasks, log files, and error messages to locate the locked files and make them writable again.

  2. Check if all files are writable.

  3. List all backups that were made from the runnables on this node and identify the backup ID of the backup you want to use. To do so, execute the list runnable backups ARIS Cloud Controller command, such as:

    ACC+ n1>list runnable backups
On node n1:
for instance abs_l (GroupId = com.aris.modeling.components, ArtifactId = y-server-run-prod):
   BackupId = 0    Date = 2020-07-11 Time : 01:11:14 Version = 10.0.12
   BackupId = 1    Date = 2020-07-13 Time : 01:17:10 Version = 10.0.12

    BackupId = 2 Date = 2020-07-14 Time : 11:29:16 Version = 10.0.12

  4. Restore all runnables that caused the setup to fail. Therefore, execute the restore runnable backup command one after another for each related runnable.

    Syntax:

    <nodeSpecWithAllNodes>? "restore" ("instance" | "runnable")? (backups | backup) (<instanceId> <backupId>? )?

    This command restores runnable backups on the current node, a specified node, or on all nodes. If only an instance ID is specified, the last backup of this instance is restored. If a backup ID is specified in addition to the instance ID, the backup with the given backup ID is restored. If no instance ID is specified for any of the configured runnables, the last backup available is restored.

    Example:

    ACC+ n1>restore runnable backup abs_l 1
This will restore the backup 1 (created at 2020-07-13 01:17:10) for runnable abs_l on n1 (GroupId = com.aris.modeling.components, ArtifactId = y-server-run-prod, Version = 10.0.12.1).
Are you sure? (Y/N)
y
Restore confirmed by user.
Successfully restored runnable abs_l from backup 2020-07-13 01:17:10.

  5. If the remote repository cannot be accessed, switch to the internal repository. To do so, enter:

    set local.repository.only=true

  6. When you restored all related runnables, enter list and check if all runnables are available in the recovered state.

  7. Make sure again that all prerequisites are met so that the setup can access and delete the required files.

  8. Run the setup again related to your operating system.

      Warning

      Do not start the setup before the runnables are restored because the setup will fail again. Since the maximum number of backups created by a setup is three, you risk data loss after unsuccessfully updating your installation three times.

    1. Adapt your modified files if required according to your installation protocol.

    2. Check the patched installation.

    3. Start all runnables. Therefore, you can use the startall ARIS Cloud Controller command or the ARIS > Administration > Start ARIS Connect Server link in the Windows Start menu.

    Your ARIS server installation is patched. All bugs mentioned in the related Readme document are fixed.

    Restore an ARIS installation

    If you updated your installation successfully, all listed bugs are fixed. If you have problems with these fixes, you can manually restore all runnables to their pre-patched state using the Restore runnable backup ARIS Cloud Controller command.

    Procedure. Procedure

    1. Stop all runnables using the stopall ARIS Cloud Controller command on each node.

    2. Check if all files are writable.

    3. List all backups that were made from the runnables on this node and identify the backup ID of the backup you want to use. To do so, execute the list runnable backups ARIS Cloud Controller command, such as:

      ACC+ n1>list runnable backups
On node n1:
for instance abs_l (GroupId = com.aris.modeling.components, ArtifactId = y-server-run-prod):
   BackupId = 0    Date = 2020-07-11 Time : 01:11:14 Version = 10.0.12
   BackupId = 1    Date = 2020-07-13 Time : 01:17:10 Version = 10.0.12

      BackupId = 2 Date = 2020-07-14 Time : 11:29:16 Version = 10.0.12

    4. Restore all runnables. Therefore, execute the restore runnable backup command one after another for each related runnable. You can identify the runnables by the build number that is related to the build.

      Syntax:

      <nodeSpecWithAllNodes>? "restore" ("instance" | "runnable")? (backups | backup) (<instanceId> <backupId>? )?

      This command restores runnable backups on the current node, a specified node, or on all nodes. If only an instance ID is specified, the last backup of this instance is restored. If a backup ID is specified in addition to the instance ID, the backup with the given backup ID is restored. If no instance ID is specified for any of the configured runnables, the last backup available is restored.

      Example:

      ACC+ n1>restore runnable backup abs_l 1
This will restore the backup 1 (created at 2020-07-13 01:17:10) for runnable abs_l on n1 (GroupId = com.aris.modeling.components, ArtifactId = y-server-run-prod, Version = 10.0.12.1).
Are you sure? (Y/N)
y
Restore confirmed by user.
Successfully restored runnable abs_l from backup 2020-07-13 01:17:10.

    5. If the remote repository cannot be accessed, switch to the internal repository. To do so, enter:

      set local.repository.only=true

    6. When you restored all related runnables, enter list and check if all runnables are available in the recovered state.

    The setup was rolled back and your installation is in the same state as before.