Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Managing NovaBACKUP 22 Agents from the CMon

What CMon-managed jobs and devices look like on NovaBACKUP 22 agents, where to edit legacy jobs, and how to move managed agents over.

Applies to: NovaBACKUP PC Agent and NovaBACKUP Server Agent, version 22, managed from a NovaBACKUP Management Console (CMon).

The CMon works the same way with NovaBACKUP 22 agents as it did with 21.x agents. Reports, filters, and activity views are unchanged. What is new for you as an MSP is full system recovery. From the CMon, you can now set up backup jobs with Disaster Recovery selected for all your customers, and these jobs can write to local or cloud devices.

What You'll Learn

  • What CMon-managed jobs and devices look like on a NovaBACKUP 22 agent
  • Where to edit legacy jobs on managed agents
  • How to find which agents still have legacy image backup jobs
  • How agents connect to the CMon

Jobs and devices pushed from the CMon

ItemOn the agent in NovaBACKUP 22Where to change it
Backup jobs pushed from the CMonListed with a lock icon on the Backup page. They open read-only, including their schedule, and can still be started on the agent.CMon
Devices pushed from the CMonListed on the Devices page without edit or delete optionsCMon
Backup jobs with Disaster Recovery selectedRun like any other CMon-pushed jobCMon
Legacy jobs that were configured in the CMonKeep runningCMon
Legacy image backup jobsKeep runningLegacy NovaBACKUP UI on the agent only. They are not available in the CMon.
Legacy jobs set up on the agentKeep runningLegacy UI on the agent

A user who opens a CMon-pushed job on the agent sees the notice This backup job is managed by the Management Server and cannot be changed here.

Moving managed agents to NovaBACKUP 22

For jobs configured in the CMon, we recommend upgrading the agents first and then moving the jobs at your own pace. Everything stays in the CMon, you never switch to the Legacy UI, and there is no deadline.

  1. Upgrade the agents from the Updates tab of each agent in the CMon. Upgrade agents on a 21.x version earlier than 21.3.410 with your RMM tool instead. See Deploying and Upgrading Agents at Scale.
  2. In the CMon, create the replacement jobs: on Local Backup or Cloud Backup devices for jobs on legacy devices, and with Disaster Recovery selected for legacy image backup jobs. Disaster Recovery includes only the drive Windows runs from, so also select any other drives the legacy image backup job covered.
  3. Once the new jobs have completed a full backup, stop or delete the legacy jobs.

Important: Each recreated job starts with a new full backup. When many agents share one cloud storage account, recreate jobs in batches so the account stays within its quota.

Finding agents with legacy jobs

The CMon has no fleet-wide report of legacy jobs. Check each agent:

  1. Open the agent in the CMon.
  2. On the Jobs tab, check the Type column. Image Backup marks a legacy image backup job.
  3. On the Devices tab, check the Type column for legacy devices: tape and other legacy device types show as System, FTP devices as FTP, and NovaNet devices as Cloud.

Connecting an agent to the CMon

On the agent, go to Settings > Management Server:

  1. Enter the Server Address, the Server Port (default 4502), and the Default Server Group Name, for example Root\Customers\Contoso.
  2. Select Test Connection to check that the agent can reach the CMon.
  3. Select Save, then restart the agent service with Stop Service and Start Service.

To set this at installation time, use the MANAGEMENT_SERVER_* properties described in Deploying and Upgrading Agents at Scale. The agent connects to the CMon on TCP port 4502.

Licensing managed agents

Each agent activates its own license key, at installation or on its License page. The agent's License tab in the CMon shows the key the agent reports.

Things to know

  • You set up and monitor full system recovery remotely. The restore itself runs on the computer being restored, from its recovery media.
  • Multi-stream restore applies to restores started on the agent, not to restores started from the CMon.
  • To restore a computer's cloud device settings without signing in to the CMon on that computer, issue a recovery token. See Issuing a Device Recovery Token in the CMon.

Related Articles

  • Deploying and Upgrading Agents at Scale
  • Issuing a Device Recovery Token in the CMon
  • Replacing Legacy Image Backup Jobs with Full System Recovery
  • Managed Backup Services (MSP) FAQs

Still Need Help?

Contact NovaBACKUP Support: