Unsolved
1 Rookie
•
2 Posts
0
17
July 14th, 2025 13:22
issue when intergrating CloudBoost with Networker
Hello,
Could anyone to help me to understand/fix one issue with CloudBoost.
I have created Cloud profile with Azure. validated it:
....
--endpoint https://cbpoc.blob.core.windows.net/ validate
Code:
0
Output:
Checking list containers/blobstore credentials ...
Checking non-existing container ...
Checking create container ...
Checking existing container ...
Checking listing blobs (empty container) ...
Checking blob creation ...
Checking listing blobs ...
Checking blob retrieval ...
Checking blob existence ...
Checking signed get (without timeout) ...
Checking signed get (with timeout) ...
Checking blob removal ...
Checking signed put (without timeout)
Checking signed put (with timeout)
Checking signed put overwrites (without timeout)
Checking blobstore time skew ...
Checking clear container ...
Checking delete container ...
RESULTS:
LIST : SUPPORTED
NON_EXISTING_CONTAINER : SUPPORTED
CREATE_CONTAINER : SUPPORTED
CHECK_EXISTING_CONTAINER : SUPPORTED
LIST_BLOBS_EMPTY_CONTAINER : SUPPORTED
CREATE_BLOB : SUPPORTED
LIST_BLOBS : SUPPORTED
FETCH_BLOB : SUPPORTED
CHECK_BLOB_EXISTENCE : SUPPORTED
FETCH_BLOB_SIGNED : SUPPORTED
FETCH_BLOB_SIGNED_TIMEOUT : UNSUPPORTED
REMOVE_BLOB : SUPPORTED
CREATE_BLOB_SIGNED : SUPPORTED
CREATE_BLOB_SIGNED_TIMEOUT : UNSUPPORTED
CREATE_BLOB_SIGNED_OVERWRITE : SUPPORTED
CLOCK_SKEW_CHECK : PASSED
CLEAR_CONTAINER : SUPPORTED
REMOVE_CONTAINER : SUPPORTED
Error:
admin@mag-fs>
==========
But when I try to integrate it with networker I get:
E0710 10:54:39.625855 313001 00000271 curl_transport_detail.cc:1133] Error: [28] - Connection timed out after 20000 milliseconds. Number of attempts: 5 URL: https://cbpoc.blob.core.windows.net/mag-1752059339-jerdti/share_info.txt
E0710 10:54:59.628747 313001 00000271 curl_transport_detail.cc:1133] Error: [28] - Connection timed out after 20000 milliseconds. Number of attempts: 6 URL: https://cbpoc.blob.core.windows.net/mag-1752059339-jerdti/share_info.txt
E0710 10:55:19.631383 313001 00000271 curl_transport_detail.cc:1133] Error: [28] - Connection timed out after 20000 milliseconds. Number of attempts: 7 URL: https://cbpoc.blob.core.windows.net/mag-1752059339-jerdti/share_info.txt
E0710 10:55:39.634383 313001 00000271 curl_transport_detail.cc:1133] Error: [28] - Connection timed out after 20000 milliseconds. Number of attempts: 8 URL: https://cbpoc.blob.core.windows.net/mag-1752059339-jerdti/share_info.txt
E0710 10:55:59.637825 313001 00000271 curl_transport_detail.cc:1133] Error: [28] - Connection timed out after 20001 milliseconds. Number of attempts: 9 URL: https://cbpoc.blob.core.windows.net/mag-
......
When I'm trying to use the embedded storage node, same failure messages and also the constant waiting for media services to start.
If anyone faced with that could you share your solution?
Thank you in advance
bbeckers1
2 Intern
•
191 Posts
0
July 15th, 2025 07:57
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.
nickcz
1 Rookie
•
2 Posts
0
July 15th, 2025 08:41
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 :(.
bbeckers1
2 Intern
•
191 Posts
0
July 15th, 2025 10:22
@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.
Or leave it enabled. Up to you.