Haven't used cloudboost since forever (used it up until nw9.2 or so, as afterwards we went all-in on data domain DDVE instead).

What versions are we dealing with wrg to ne server and CB version?

so are all required ports opened between the nw server and the cloudboost instance? NW server running on-prem or also in the cloud?

https://www.dell.com/support/manuals/en-us/cloudboost-virtual-appliance/cloudboost_integration_guide_19.12/firewall-port-requirements?guid=guid-cdac2493-af3a-4b35-b5ab-013529a2d8d5&lang=en-us



What does "status" show on the cloudboost cli? Anything out of the ordinary?

So you can reach and configure it using the On-Prem CloudBoost Management Console? A proxy configured for CB to be able to connect to the On-Prem CloudBoost Management Console?

https://www.dell.com/support/kbdoc/en-us/000071986?lang=en "NetWorker: Triage: CloudBoost and NetWorker Solutions" might further help, however you can ignore the DPC cloud part as that has been replaced by the he On-Prem CloudBoost Management Console, but running commands like nsrports and nsradmin from both ends can help.

Hi, thanks for replying. 

I would say status is OK:
admin@mag-fs> status
Host Configuration:
  Hostname:         tlxx
  Domain:           tx.x.net
  FQDN:             tlxxxx
Version Information:
  Version:          19.11.0.1.Build.2
  Internal Version: 3.17.0
  Revision:         018a69bb
Network Interfaces:
             name            mode         address         netmask
             ----            ----         -------         -------
             eth0          static   10.241.238.26   255.255.254.0
 
Network Routes:
           prefix         netmask         gateway
           ------         -------         -------
          0.0.0.0         0.0.0.0  10.241.239.254
     10.x.x.0   255.255.254.0         0.0.0.0
 
DNS Configuration
  DNS Servers:     10.241.x, 10.241.x
Appliance Configuration
  Status:          Initial configuration completed
  Endpoint:        NA
=======================

CloudProfile is created and validation is OK. CloudBoost created two containers in Azure.

Networker cannot start Media Services.

CloudBoost CLI is quite limited, there is no option to run nsrports:
Also I can see that CB creates blobs in its containers, I guess these are backup files of CB itself. But it cannot push data thru itself to Azure. as I mentioned media services cannot start :(.

@nickcz​ login with the maginatics user instead of the admin user. So for that enable ssh-access by specifying a password (if not already done). That maginatics user would have sudo permissions.

1. Enable SSH access from the admin CLI:  ssh-access enable <PASSWORD>
2. SSH into the appliance as username maginatics
3. Exit the maginatics SSH session and disable SSH access from the admin CLI: ssh-access disable

Or leave it enabled. Up to you.

I still use CB on some setups in Azure (most of previous ones I replaced with DDVE).  From your original post, it is not an issue with communication towards storage account, but rather something blocking communication between backup server and CB appliance (also, do not use embedded sn option).