Hystax Disaster Recovery overview

Hystax Acura Control Panel

Hystax Acura Control Panel (ACP) is a web-application for managing Disaster Recovery Hystax Acura solution. The main components of the ACP are:

  • Customer page with the information display on the used resources, Disaster Recovery plans, cloud sites and machine groups;
  • Cloud site page is information display and management of the failover;
  • Wizards of machine protection, failback start and recovery;
  • Notification page;
  • Reports are detailed information on system resources;
  • Managing users and their roles;
  • Replication and recovery settings windows.

Recommended browsers: Google Chrome, Mozilla Firefox, Safari.

Partner page overview

image0

The partner page contains the following information:

  1. Resource management and functionality menu
  2. Statistics on the number of partner customers
  3. Total number of customer machines
  4. Number of cloud sites launched by partner customers
  5. List of customers with statistics decomposition for each customer
  6. Functionality for adding new customers or editing information about existing ones (Section: ACP - Adding new customers)
  7. Notification panel displaying summary status about customers
  8. Page description

Notification panel

image1

Notification panel informs users about the need to intervene in solving problems with replication or recovery process. ACP uses the following color scheme:

Green color of the panel means that customers do not have problems requiring immediate intervention

Yellow color of the panel means that customers have problems that require attention and solution in the near future. Examples of notifications: the machine is out of space, the machine is unavailable for several days

Red color - immediate action is required. Examples of notifications: several unsuccessful consecutive replications of the machine, no notifications from replication agent, etc.

Add new customer

To add a new customer got to the Partner page and just click Add.

image2

Fill in the following required fields to add a customer: Company Name, Contact Email, Contact Phone, Address, Active checkbox (activity status of a customer and all his users).

image3

After clicking Save, the customer will be created, appear in the customer list. An admin user for the customer is created with the default password, which will need to be changed at the first login. When the customer is created, it is necessary to proceed to the process of protecting infrastructure.

  • Company Name - customer company name, will be displayed in UI, unique within the partner.
  • Contact Email - email address for communication with a customer representative on the solution usage and billing, unique within the partner.
  • Contact Phone is the telephone number of the customer’s representative.
  • Address
  • Active - shows whether the customer is active or not, this field affects the ability of customer users to use the system.

Edit existing customer

To edit existing customer, click on the Edit button in the list opposite the necessary customer.

image4

As the result, a dialog window with filled in customer data will appear. Make necessary changes in the dialog and click Save, after that customer data will be updated.

image5

Customer page overview

image6

The customer page contains the following information:

  1. Resource management and functionality menu
  2. Number of customer cloud sites
  3. Number of groups of machines (Section: ACP - Machine Group Management)
  4. Total number of customer machines
  5. List of running cloud sites with the ability to manage them
  6. List of running failbacks with the ability to manage them
  7. List of Disaster Recovery plans with the ability to manage them
  8. Groups of machines
  9. Notification panel showing the total status of customers
  10. Page description

Cloud sites

image7

Cloud Site (Section: ACP - Cloud Sites) is running failover of customer business application, which works in the backup data center. Customer page allows to see statistics on cloud sites and also perform actions on them: delete cloud sites when there is no need in them and change their settings.

Disater Recovery plans

image8

Customer page allows creating, viewing and editing Disaster Recovery plans (Section: ACP - Disaster Recovery plans). Disaster Recovery plan includes infrastructure description and instructions that should be performed to recreate the business application in backup data center in case of emergency. DR plan is created in advance on the basis of a productive infrastructure, tested by running test cloud sites, maintained up-to-date by periodic updates and transferred to the recovery process in case of disaster.

Machines and actions over them

image9

Customer page displays the machines that are in the scope (located in VMware vSphere, where Hystax Acura agents are installed), or protected by the solution. Machines can be grouped by various criteria: geographic location of the machine, general snapshot storage policy or replication schedule, etc. Customer can edit individual machines, groups and global settings in general.

Settings are as follows:

  • As a default, global settings are applied to all groups and machines
  • Editing group settings, the new settings are applied to all (in the group or to be added later) machines with the default settings, otherwise the settings of specific machines will work if they are changed
  • Editing the settings of machines, the machines are affected by the settings of a specific machine, otherwise the group settings or global settings

Protecting new machines, through the automatic detection of machines on VMware vSphere, the machines enter the set-up group for the agent (Section: ACP - Machine Protection Process).

Add new machine group

To add a new group got to machines Groups and just click Add.

image10

As the result, a dialog window with filled in customer data will appear. Fill in group name and its description. Group name should be unique within a customer.

image11

After clicking Save, the group will be created and appear on the Customer page.

By default, there is a Default group for each customer, which cannot be deleted. In the list of groups, it is highlighted by the corresponding symbol next to its name. The default group cannot be changed.

Remove and rename groups

To remove or rename a group, select appropriate items in the group menu:

image12

Default group cannot be removed, just can be renamed.

Move machines between groups

To move machines between groups, select machines in groups and click “Move to another group” in the menu “Actions”.

image13

As the result, a dialog window with filled in customer data will appear. Select an appropriate group.

image14

Protect new machines

To protect new machines use protect process(Section: ACP - Protect). If the machines are running on VMware vSphere, after starting the agents on vSphere they appear in the list of machines (the machines get to the main group for the agent) as unprotected. Select machines and click “Start replication” in the menu “Actions”.

image15

After that the machines begin to replicate in accordance with schedule rules (Section: ACP – Replication schedule).

Sync machines replications

To sync machines replication mark the machines which should be replicated simultaneously and click “Start replication” in the menu “Actions”. Replication of all selected machines will start and then they will be protected concurrently.

image16

Park / unpark replication

To park / unpark replication select machines from different groups and click “Park” in the menu “Actions”. This action pauses agent replicating task for the machine.

image17

To unpark replication click “Start replication” in the menu “Actions”.

Edit replication schedule

It is possible to edit replication schedule on the level of separate machines, group or general settings.

image18

Settings are as follows:

  • As a default, global settings are applied to all groups and machines
  • Editing group settings, the new settings are applied to all (in the group or to be added later) machines with the default settings, otherwise the settings of specific machines will work if they are changed
  • Editing the settings of machines, the machines are affected by the settings of a specific machine, otherwise the group settings or global settings

To change settings click Edit replication schedule in the menu Actions (for separate machines),

image19

in the menu of separate groups

image20

or in the general settings menu of machines groups.

image21

There are two options for schedule:

  • Interval schedule, when replication occurs at equal intervals of time. For example: every 15 minutes or every 6 hours. This option is ideal for non-critical elements of a business-application, so it does not seriously affect the performance of the system and does not load the network.
  • Continuous replication is start of replicas immediately after the completion of the previous ones. It is ideal for critical components, such as databases and mail services.

Attention

A minor impact on the performance of the machine and the network through continuous replication can be found with continuous replication.

Edit retention policies

Retention policies give the ability to set the amount of time before restore points, stored in the target cloud, are automatically deleted.

It is possible to edit retention policies on the level of separate machines, group or general settings.

image22

Settings are as follows:

  • As a default, global settings are applied to all groups and machines to edit retention policies.
  • Editing group settings, the new settings are applied to all (in the group or to be added later) machines with the default settings, otherwise the settings of specific machines will work if they are changed
  • Editing the settings of machines, the machines are affected by the settings of a specific machine, otherwise the group settings or global settings

To edit settings click Edit retention policies in the menu Actions (for separate machines),

image23

in the menu of separate groups

image24

or in the general settings menu of machines groups

image25

To edit retention policies set the storage period:

  • all restore points (days) - for how many days all restore points will be stored. In other words, for this period of time no restore points will be deleted, and after that, they continue to transform into restore points once a day.

Note

Pay attention to the set replication schedule not to get out of existing quotes from the target cloud. Use the “0” value to keep the last restore point for the current day.

  • daily restore points (days) - a number of days during which only the last restore point will be stored, after this period of time they will be transformed into weekly restore points.
  • weekly restore points (weeks) - a number of weeks that will have only the last restore point per week stored. After the specified time, the restore point will be passed to the monthly retention.
  • monthly restore points (months) - a number of months during which only the last restore point will be stored, after this period of time they will be transformed into one per year restore points.
  • annual restore points (years) - a number of years that will have only the last restore point per year stored. After the specified time, the restore point will be snaped off the system to save space.

Note

Retention job runs as soon as a new replication takes place and uses UTC time to clean up the data.

A short example to illustrate how it works:

Assuming a customer has the following retention settings:
  • All - 1
  • Daily - 2
  • Weekly - 2
  • Monthly - 3
  • Annually - 2

This means that retention will keep all the restore points created today, the next day retention will clean up all restore points from yesterday except the last one.

All of the above happens until the end of the week and with the first replication on the next week, retention will keep only the last restore point for the previous week.

This way by the end of the month there will be 2 restore points, one per the last two weeks. The next month comes up, monthly retention takes place and keeps only one restore point for the previous month, the last one. The same happens for a year.

Generate DR plan from machines group

It is possible to generate DR plan from machines group on the level of separate machines, group or general settings. To generate DR plan from machines group for several machines or groups select machines (for the case of generation for several machines) and click Generate DR plan in the menu Action (for the case of generation for several machines).

image26

in the menu of groups

image27

As the result, a dialog window for DR plan creation to edit DR plan settings, give name to it. Its name should be unique within the customer.

image28

To generate DR plan from machines group click Generate DR plan from machines group on the DR plan creation page (Section: ACP - Disaster Recovery plans).

Edit VMware vSphere settings

To replicate machines VMware vSphere, Hystax Acura uses VMware CBT API, to use which it needs just login and password for VMware vSphere. To edit login / password on VMware vSphere, update settings on Hystax Acura to continue. To do it use the edit settings of VMware vSphere form, which is available through the appropriate menu item in the global settings of the machine.

image29

Select an appropriate VMware vSphere platform and edit settings. After this the agents will automatically receive updated settings and continue the replication. The platform name should be unique within the customer.

image30

Notification panel

image31

Notification panel informs users about the need to intervene in solving problems with replication or recovery process. ACP uses the following color scheme:

Green color of the panel means that customers do not have problems requiring immediate intervention

Yellow color of the panel means that customers have problems that require attention and solution in the near future. Examples of notifications: the machine is out of space, the machine is unavailable for several days

Red color - immediate action is required. Examples of notifications: several unsuccessful consecutive replications of the machine, no notifications from replication agent, etc.

Disaster Recovery plans

image32

Disaster Recovery Plan is a description of the infrastructure and the set of necessary instructions, used to recreate the business application in the DC in case of disaster. The DR plan is created in advance on the basis of a productive infrastructure, tested by running cloud sites, maintained up-to-date by periodic updates and transferred to the recovery process in case of disaster.

The customer can create an arbitrary number of Disaster Recovery plans: one for restoring the entire infrastructure or several with a breakdown into groups of machines, departments, machines roles for the Disaster Recovery plan, etc.

To restore (Recovery Process) select one or more Disaster Recovery plans on the basis of which the cloud site will be started (Section: ACP - Cloud Sites).

Disaster Recovery plans must always be kept up-to-date, since at the time of the accident, additional time may be required to update the plan and, accordingly, the downtime of the infrastructure and the business application will increase.

Create a Disaster Recovery plan

To create a Disaster Recovery plan just click Add on the Customer page.

image33

Adding a new plan specify its name and the contents of the plan. DR plan name should be unique within the customer.

image34

The body of the DR plan is a JSON instruction for restoring the infrastructure and the business application in the DC. To generate a plan based on all customer machines, click on the link Generate DR plan from all machines.

To generate the DR plan based on several machines or a group of machines just click Generate DR plan in the menu Actions for the machine

image35

the menu item in the group properties.

image36

DR plan syntax

DR plan body is a JSON instruction for restoring infrastructure and business application in the DC.

Example of Disaster Recovery plan:

{
"devices": {
    "IIS_Acura-Demo": {
    "rank": 1,
    "id": "52ce9361-b282-72b6-425a-f67347c5b79a",
    "ports": [
        {
        "name": "port_0",
        "ip": "192.168.15.112",
        "subnet": "main_subnet"
        },
        {
        "name": "port_1",
        "subnet": "external"
        }
    ]
    },
    "rhel7.2": {
    "id": "522f3448-6a56-aa45-2131-207f7dda6664",
    "ports": [
        {
        "name": "port_0",
        "ip": "192.168.15.100",
        "subnet": "main_subnet"
        }
    ],
    "rank": 0,
    "boot_condition": {
        "delay_seconds": 120,
        "type": "wait"
    }
    }
},
"subnets": {
    "main_subnet": {
        "cidr": "192.168.15.0/24",
        "subnet_id": "eda47a07-d1dd-4aca-ae8f-c652e997008e"
    }
  }
}

Basetags:

devices - сcontains a description of each machine. It is necessary to list all the machines that should be recreated in the cloud site.

{
"devices": {
    "rhel7.2": {
      "id": "522f3448-6a56-aa45-2131-207f7dda6664",
      "ports": {
        "port_0": {
          "ip": "192.168.15.100",
          "subnet": "main_subnet"
        }
      },
      "rank": 0,
      "boot_condition": {
        "delay_seconds": 120,
        "type": "wait"
      }
    }
}

subnets – contains a description of networks that need to be recreated in the DC.

{
 "subnets": {
    "main_subnet": {
        "cidr": "192.168.15.0/24",
        "subnet_id": "eda47a07-d1dd-4aca-ae8f-c652e997008e"
    }
  }

project_name – a name of the OpenStack project, in which the cloud site will be launched. If the project does not exist, it will be created. By default, the name of the cloud site is used. The created projects will be deleted together with the cloud site.

{
"project_name":"acura_project"
}

Syntax of machine description

Machine description consists of a number of parameters describing machine properties such as: machine name, network settings, rank and conditions for loading the machine to maintain the sequence and orchestration of launching process of the cloud site.

{
"rhel7.2": {
     "id": "522f3448-6a56-aa45-2131-207f7dda6664",
     "security_groups": [
            "sg-1",
            "sg-2"
      ],
      "availability_zone": "zone-1",
      "user_data": "#!/bin/bash\nrpm -e hlragent\nrm -rf /etc/hystax\n",
      "ports": {
        "port_0": {
          "ip": "192.168.15.100",
          "subnet": "main_subnet"
        }
      },
      "rank": 0,
      "boot_condition": {
        "delay_seconds": 120,
        "type": "wait"
      }
    }
}

Machine description parameters:

Parameter Description Required field
machine name Base tag for machine description. Name will be used to identify machine in the cloud site. Yes
id Internal id of customer machine that is generated with DR plan pre-generation. Also can be found by moving mouse pointer to the machine name in the machine list on the Customer page. Yes
ports

List of network machine interfaces configurations. There can be one or more interfaces. Interfaces will be added in the same order in which they are described.

Interface description has the following parameters:
Parameter Description Required parameter
name interface name Yes
ip interface IP address No
mac interface mac address. Ignored for AWS target cloud. No
subnet subnet name, the interface will belong to Yes
routing_allowed allows machine to be a router (has “true” or “false” values, default value is “false”). Ignored for AWS target cloud. No
floating_ip adds floating_ip for port (has “true” or “false” values, default value is “false”). Using this parameter with the “true” value limits the machine to have only one port. No

Example:

"ports": [
 {
     "name": "port_0",
     "ip": "192.168.15.100",
     "subnet": "main_subnet"
 }
 ]
Yes
rank Order in which a group of machines will be launched. For example: machines with rank 2 will be launched only after all machines with rank 1 are started, and those in turn only after all machines with a rank 0 are started. Yes
boot_condition

Condition in which machine is considered to be running. Delay in time is supported, at the expiration of which the machine is considered to be running. The condition extends to the whole rank, if there are several machines with a delay in time, the rank is considered fulfilled while waiting for the longest time.

Syntax:

"boot_condition": {
        "delay_seconds": number of seconds to wait,
        "type": "wait"
      }

Example:

"boot_condition": {
        "delay_seconds": 120,
        "type": "wait"
      }
No
flavor Name or ID of existing flavor in the target cloud. No
security_groups List of security groups to use for the the machine. This will overwrite the default group(s). No
availability_zone Name of Availability Zone to use for the machine. This will overwrite the availability_zone that is specified in the cloud config settings No
user_data Script to be executed on the target machine. To use the key “user_data”, the source machine must have installed cloud_init, otherwise, it will be ignored. This key can be used only for OpenStack target cloud. No

Syntax of network description

Network description consists of a number of parameters such as: network name, its CIDR and address of DNS servers.

Example:

{
"subnets": {
    "main_subnet": {
        "cidr": "192.168.15.0/24",
        "subnet_id": "eda47a07-d1dd-4aca-ae8f-c652e997008e"
        }
  }
}

Network description parameters:

Parameter Description Required parameter
network name network identifier name is a base tag for network description Yes
cidr network CIDR Yes
dns_nameservers IP address of DNS servers. For OpenStack target cloud only. Ignored for AWS target cloud. No
subnet_id existing subnet ID in the target cloud. Yes

Note

Specified subnet_id must be available for the used Availability Zone.

Edit existing DR plan

To edit existing DR plan select an appropriate DR plan and click Edit on the Customer page.

image37

As the result, a dialog window, where DR plan can be edited, will appear.

image38

Cloud sites

Cloud site is customer business application running in the backup DC which consists of network infrastructure, components included into business application.

image39

The main components of the page are:

  1. Resource Management and Functionality menu
  2. Total number of machines running in the cloud site
  3. Functionality for editing site name and removing the site
  4. Information about type and condition of the cloud site
  5. List of running machines with the ability to manage them

To run cloud site start the Recovery Process (Section: Recovery Process).

User and solution settings

Access to user settings and solutions is done through the menu item Settings in the upper right corner.

image49

Attention

Due to the user’s rights, the set of available options may vary.

The window with the settings:

image50

User settings

image51

There is a possibility to edit password and user’s full name on the page of current user settings. Attention: after editing, the settings automatically take effect and it will be necessary to enter updated data to log in in future.

User management

This option is available only if the current user has a role with the right to manage users. Management is possible only by users at the current hierarchy level and below, that is, the user of the customer does not see and cannot edit the users of another customer and partner.

It is possible to add / remove users, give roles for specific resources, change the activity of current users, reset their passwords to new values and change user data such as full name on this page.

image52

Create users

To create a new user just click Add user.

image53

As the result, a dialog window will appear. Fill in the information about a new user and user’s Organization(partner or customer).

Assign roles

Role assignment determines what rights the user has in a particular role action area (specific partner, customer, customer machine group). If an administrator role is created and assigned to a specific customer, the user will have administrator rights for that customer resources.

Creating an assignment consists in granting to the selected user a certain role for a specific scope of the role / resource. Click Assign Role and select Role and Scope.

If the user has appropriate rights, he can assign roles according to its scope and only within this scope.

Created assignment takes effect automatically from the moment it was created.

Roles management

This option is only available if current user has a role with the right to manage roles. Partner users have access to partner roles, customer users have access to customer roles as well as to roles shared with them by their partner. To assign roles to specific users click

User management.

This page allows to add / remove roles, edit a set of rights for each role and change the flag of their activity.

image54

Add a role

image53

To add a role fill in its name and description and select a role template (set of permissions, possible options: root, partner, customer, group) that manages the set of permissions and the organization that owns the role for which it will be available for assigning.

Attention

During role assignment if user has appropriate rights, he can see the roles within his organization - role owner.

It is also necessary to set the checkbox Share the role with customers if the role should be available to partner’s customers.

Manage a set of permissions

To manage a set of permissions for role (already existing or just created) just manage the status of the checkboxes for each permission.

image56

Ticked checkbox means the inclusion of the permission for the action, the removed checkbox means the ban on the action. In this case, the added checkbox in one of the roles and its assignment to the scope means permission for a particular action within this scope in spite of the fact that it can be removed in other roles assigned to the scope.

Attention

Editing existing roles will change the list of rights for users to whom this role has already been assigned. When a role is created and permissions are set, it can be assigned to users on the User management tab.

Company settings management

This option is only available if the current user has a role with the right to manage the company settings. This page allows to edit the fields of the company to which the current user belongs. Fields available for editing:

  • Company Name – name of customer’s company, this information will be displayed in UI.
  • Contact Email – email for communication with customer representative on the use of the solution and billing.
  • Contact Phone – customer representative telephone number
  • Address - customer correspondence address

Protecting machines

To protect machine click Protect new platform in the menu Group settings

image57

or Download agents in the main menu of web interface.

image58

Depending on whether a user is authorized by partner or customer, protection process consists of three (for partner) or two (for customer) steps.

For partner, the first step is to select a customer for which it is necessary to protect the machine.

image59

The second step is to select an agent type by protected platform - VMware, Linux or Windows:

image60

The next step is to select:

  • Group to which machines protected by agent will be included.
  • VMware vSphere platform. Fill in its description and login / password; or select existing platform from the list. Parameters of protected DR platforms can be edited in the menu of global customer’s settings (Section ACP - Edit settings of VMware vSphere).

image61

The last step is to download the agent.

After downloading and installing the agent all machines from vSphere will automatically appear in UI in the machine group specified on the second step. Machines will be in Unprotected status. Select machines to protect and click Start replication in the menu Actions.

image15

Recovery process

To start recovery process during failover testing or in case of disaster click Run Recover on the customer page with selected DR plans

image62

or Recover in the main menu.

image63

Recovery process consists of three (for partner) or two (for customer) steps.

For partner, the first step is to select a customer for which it is necessary to protect the machine.

image64

Next step is to select DR plans (Section ACP - DR plans) from which restore process will be carried out. In this case, it is possible to create customized DR plan - in case DR plans have not been updated for some time, but at the moment there is no time to update current plans for the latest changes.

image65

Attention

If several DR plans contain descriptions of the same resources, the next step will not be available until the conflict is resolved by changing one of the plans. This is done to prevent collisions during cloud site start, which can lead to unpredictable consequences.

Last step when restoring to backup DC consists of filling in cloud site name, recovery point (point at which the infrastructure should be restored) and final validation / modification of DR plan and brief description of future cloud site. Cloud site name must be unique within the customer, contain only Latin letters, numbers and special symbols “-“, “_” and “.”.

Recovery point is a point in time to which the business application will be restored. For each machine, the nearest replicas in the past from the specified point in time will be taken.

image66

To run cloud site for failover, start machines and configure them in accordance with the final DR plan click Run Recover.

The Cloud Site page will be opened to monitor the machines statuses and information.

image39

Failback to production

When the main platform is restored after disaster it is necessary to failback business application to it with all the changes that have been accumulated on the backup platform since the launch of the cloud site and redirecting user traffic to it.

The process consists of:

  1. Downloading an agent with prepared DR plan, running it on production environment to download changes from the last recovery point.
  2. Testing business application on production environment.
  3. Stopping machines in cloud site to finalize the changes.
  4. Downloading changes from running cloud site to new production.
  5. Starting machines in production and redirecting traffic to it.
  6. Protection of new production.

To start failback click the button Failback in the main menu.

image67

Failback process includes four (for the partner) or three (for the customer) steps.

For the partner, the first step is to select a customer who needs failback.

image68

On the second step, select a cloud office and a DR plan to return to the product - a scenario, describing the machines to be downloaded and created in VMware vSphere.

image69

On the third step, specify the platform that will be used as a target - select previously protected platform or add a new one.

image70

On the last step use the button Download Agent to get the agent . The agent installed on the new environment is required to download the data from running cloud office.

If the agent is installed, it will be displayed as online, and it will be possible to specify the target storage and host for the machine.

image71

Agent requirements

Ports for correct agent work:
  • Acura host - tcp/80, tcp/443
  • vSphere host - tcp/443
  • ESXi host(s) - tcp/udp/902
  • Receive logs from the Acura cluster - udp/12201

Failback process uses the same agent that is used for the replication process. At the same time there is a number of host permissions the agent requires for successful failback. For ESXi 6.0 and older, the list of permissions looks the following way:

  • Resource.Assign VirtualMachine to Resource Pool
  • Datastore.Allocate Space
  • Datastore.AllocateSpace
  • Network.Assign Network
  • VirtualMachine.Inventory.Create
  • VirtualMachine.Configuration.Add New Disk
  • VirtualMachine.Configuration.Raw Device
  • VirtualMachine.State.Create Snapshot
  • VirtualMachine.State.Remove Snapshot
  • VirtualMachine.Interaction.Power Off
  • VirtualMachine.Interaction.Power On
  • VirtualMachine.Config.AdvancedConfig
  • VirtualMachine.Provisioning.DiskRandomAccess
  • VirtualMachine.Config.AddRemoveDevice
  • VirtualMachine.Config.CPUCount
  • VirtualMachine.Config.Memory

For ESXi 6.5 and higher create a role with the following privileges:

Datastore
  • Allocate space
Global
  • Enable methods
Network
  • Assign network
Resource
  • Assign Virtual machine to resource pool
Virtual machine
  • Change Configuration
    • Acquire disk lease
    • Add new disk
    • Advanced configuration
    • Configure Raw device
    • Toggle disk change tracking
    • Change CPU count
    • Memory
  • Edit Inventory
    • Create from existing
    • Create new
  • Interaction
    • Backup operation on virtual machine
    • Power off
    • Power on
  • Provisioning
    • Allow disk access
    • Allow read-only disk access
    • Allow virtual machine download
Snapshot management
  • Create snapshot
  • Remove snapshot
  • Revert to snapshot

Agent installation

Install agent on one of ESXi hosts and run it. Refer to Install VMware agents for detailed instructions.

Log in via the terminal to the user’s account that was issued earlier during downloading the agent.

Reports

Hystax Acura provides with a sophisticated set of reports on various components usage. Partners and customers and get information on Machine state and Cloud Sites statistics.

Partners can get statistics for a specific customer or for all customers. Customers can get statistics applicable to them.

Start and End date controls are available to limit stats scope to a specific time range.

Export to CSV is available in case necessity of further data analysis.

Machine State Report

Machine state report provides information about changes in number of protected / unprotected / parked machines in a specific timeframe.

Export to CSV is available in case necessity of further data analysis.

Cloud Site Report

Cloud site report provides information about resources utilized in cloud sites in a specific timeframe. You can find information about number of cloud sites, number machines in those cloud sites.

Export to CSV is available in case necessity of further data analysis.