Axcient x360Recover Setup Beta

Connect Axcient x360Recover to let Junto check backups for your customers' servers, workstations, and NAS devices. The agent can read a customer's overall backup health, list protected systems and their latest restore points, explain failing backup jobs from their run history, confirm which restore points exist, check AutoVerify results, and inspect on-site backup appliances.

The integration is read-only. Junto never starts a backup, restore, or virtualization, and never changes backup settings. Those stay in the Axcient portal.

Junto supports one Axcient configuration per organization. Connect your Axcient partner account once with an API key, then map each Junto company to its Axcient client so the agent sees the right customer's backups.

Prerequisites

• A Junto Admin or Owner account
• An Axcient administrator who can create API keys in the x360Portal
• Customer companies in Junto, imported from your PSA, to map to Axcient clients

Step 1: Create an Axcient API Key

1. Sign in to the x360Portal as an Axcient administrator.
2. Go to Settings > API Keys and create a key.
3. Copy the key before leaving the page. Axcient shows it only once.

Junto only reads backup data with the key.

Step 2: Configure in Junto

1. Go to Settings > Integrations > Axcient.

2. Click Add configuration.

3. Complete the form:

   Field	What to enter
   API key	The key from Step 1
   Active	Leave enabled to make the integration available to the agent. Turn it off to remove agent access without deleting the connection.

4. Click Create configuration. Junto checks the key against Axcient before saving it, so an invalid key is rejected with an error in the dialog. On success the button shows Saved, a Configuration created notice names the Axcient organization you connected to, and the dialog closes.

The configuration card shows your Axcient organization name, the last four characters of the API key, and an Active or Inactive badge. Junto encrypts the key when it is stored and never displays it again. Add configuration is disabled once a configuration exists.

Step 3: Test the Connection

Click Test connection on the configuration card. A successful test reports Connection successful and names the Axcient organization the key belongs to. A failed test reports Connection test failed with the reason. The test only reads your Axcient organization record and changes nothing in Axcient. You can run it at any time, for example after rotating the key.

Step 4: Map Companies

Each Junto company maps to one Axcient client, and each Axcient client belongs to only one Junto company. An unmapped company cannot use the Axcient tools.

1. Click Map companies on the active configuration.
2. In the Map companies to Axcient clients dialog, choose the Axcient client for each Junto company, or leave it as Not mapped. The Status column shows Mapped or Unmapped.
3. Click Save mappings and confirm Mappings saved appears.

You can also click Run auto-map. Auto-map matches Axcient clients to Junto companies by name: exact matches are applied automatically and similar names are presented for you to review and confirm. Inactive Axcient clients appear in the list marked (inactive) and can be mapped by hand, but auto-map skips them.

Mappings can only be saved while the configuration is Active. If a saved client is marked no longer in Axcient, it was removed from your Axcient account; choose another client or Not mapped before saving. If the notice reads Mappings saved with skipped companies, some selections were skipped because those companies are hidden or no longer in your Junto organization.

What the Agent Can Do

Capability	What Junto can do	Risk level
Client backup summary	Read a customer's overall health status (Normal, Warned, Troubled, Unprotected, or Parked), protected system counts by kind (appliance-based, direct-to-cloud, cloud archive) and type, and local, vault, and cloud storage used	Low
Protected systems	List the customer's servers, workstations, NAS devices, and archives with health status and reason, operating system, IP address, agent version, and the latest local, cloud, and vault restore points. Filter by health status or device type, or search by name, IP, MAC address, or operating system	Low
Protected system detail	Read one system's current and previous health, storage used, protected and excluded volumes, the vaults it replicates to, its backup jobs, local cache verification, the latest AutoVerify result, and a link to the device page in the Axcient portal	Low
Backup jobs	List the backup and replication jobs configured for one system, with type, enabled and offsite state, health status, latest restore point, and target vault	Low
Job run history	Read a job's runs with status, start and end time, restore point produced, initial or full backup, data written, and the error message for failed runs. Filter by in-progress, initial, successful, or failed runs	Low
Restore points	List the restore points held for one system, grouped by vault, with each point's time and whether it is currently in use	Low
AutoVerify results	Read whether recent backups booted as a virtual machine, with the heartbeat, VSS, and check-disk results and a screenshot link	Low
Backup appliances	List the customer's on-site appliances with model, software version, health and reason, management tunnel status and when it was last up, storage used and total, and the systems each one protects	Low

All Axcient tools are read-only. Read-only tools do not require approval: each ships with Approval set to Automatic and is visible to all staff. Admins can change either setting per tool under Tool Policies.

Scope and Reporting

• Customer context: Every tool works on one mapped company at a time. In a company-bound chat or runbook, the agent uses that company's Axcient client. In an organization-wide Explore chat, name the company, or ask for a report across all companies mapped to Axcient.
• Ownership checks: The agent only reads protected systems that belong to the company's mapped Axcient client. A system from another customer is refused, even if you supply its ID.
• Identifiers: The agent takes system and job IDs from Axcient inventory and never guesses them.
• Systems without an agent: Only machines with an Axcient agent appear. A machine missing from the list has no Axcient protection; it does not have a failed backup.
• Replication versus backup: A recent local restore point with older cloud or vault points means replication is behind, not that the backup itself failed.
• Site-wide failures: When several systems at one site fail together, the agent checks the site's appliances. A tunnel that is down or a full appliance is the usual cause. Direct-to-cloud systems have no appliance.
• Result limits: Protected systems are listed 100 per page, job history 50 runs per page, and restore points 50 per vault per page. Job history looks back 7 days by default and up to 90 days. AutoVerify returns the 5 newest results per appliance or vault by default, up to 50. The agent reads every page before reporting totals.
• Storage values: Storage and usage figures are reported in bytes.
• Restores: Restores, backups, and virtualizations are started in the Axcient portal. The agent can give you the device page link from the system's details.

Use in Explore and Runbooks

Axcient tools are available in Explore, in company-bound ticket chats, and in runbooks. Because every tool is read-only, a runbook step that checks backup health can run without waiting for anyone to approve it.

Example requests:

• "How are Acme's Axcient backups? List any systems that are not Normal."
• "Is ACME-FS01 backed up? When was the last cloud restore point?"
• "Why is the backup failing on ACME-SQL02? Show the failed runs from the last two weeks."
• "Can we restore ACME-DC01 to last Tuesday? Check the restore points and recent AutoVerify results."
• "Several of Acme's servers stopped backing up overnight. Check their appliance."
• "Give me a backup health report for every company mapped to Axcient."

Managing the Connection

• Update the API key: Click Edit, enter the new API key, and click Update configuration. Leave the field blank to keep the current key. Junto checks the new key against Axcient before saving. A key from the same Axcient organization keeps your company mappings; a key from a different Axcient organization clears them, because client IDs belong to the old organization. Map companies again after switching organizations.
• Pause the integration: Click Edit, turn off Active, and click Update configuration. The key and mappings stay saved, the agent loses access, and Map companies is disabled until you reactivate.
• Remove the integration: Click Disconnect, then confirm Disconnect in the Disconnect Axcient? dialog. This removes the saved API key and all Axcient company mappings from Junto. Nothing changes in Axcient.

Troubleshooting

• Connection fails or the key is rejected: "Axcient rejected the API key" means the key is wrong, revoked, or was copied incompletely. Create a new key in the x360Portal under Settings > API Keys, then click Edit and enter it.
• "The stored Axcient API key can't be read": Click Edit, enter the API key again, and save.
• "Could not reach Axcient": Axcient did not respond. Wait a few minutes and click Test connection again.
• Rate limit reached: Axcient limits how often the API can be called. Junto retries automatically; if the message persists, wait a minute and try again.
• Cannot add a second configuration: Axcient supports one configuration per organization. Click Edit on the existing configuration to change the key.
• Map companies is disabled: The configuration must be Active. Click Edit, turn on Active, and save.
• No Axcient clients appear in the mapping dialog: Add clients in the x360Portal, then reopen the dialog. If no Junto companies appear, import companies from your PSA first.
• Mapping cannot be saved: A selected client may have been removed from Axcient, a client may be selected for two companies, or another administrator may have changed mappings at the same time. Close and reopen the mapping dialog to refresh the list, then save again. If the message says the API key moved to another organization while clients were loading, reopen the dialog and map against the current organization.
• The agent says a company is not mapped to an Axcient client: Open Map companies and assign that company's Axcient client.
• The agent says a system is not one of the company's protected systems: The system belongs to a different Axcient client than the one mapped. Check the company's mapping.
• A machine is missing from the protected systems list: It has no Axcient agent installed, or it is protected under a different Axcient client.
• "The Axcient API key is not allowed to read that record": The key does not have access to that client or device in Axcient. Check the key's access in the x360Portal.

Related

• Tool Policies
• Explore
• Datto Continuity
• Cove Data Protection