Got it. The Windows client is used for the NetBackup workflow which does not have CloudBoost built-in. In that workflow the standalone CloudBoost client mounts the CloudBoost device as if it were a Windows share (UNC path) which NetBackup can then use to store its backup containers. The document you are referring to was suggesting you that you could also use that client to test CloudBoost connectivity from any Windows computer, such as your admin workstation. Support uses it this way because for basic connectivity troubleshooting it is often more convenient to be able to test directly from a specific computer without having to switch to the NetWorker console and trigger a backup.
geordiekorper
22 Posts
1
July 5th, 2017 07:00
There is no separate installer. It is built-in to the standard NetWorker client.
Diego.Palopoli
1 Rookie
•
32 Posts
0
July 5th, 2017 07:00
Awesome explanation Geordie!
Thank you very much again!
Diego.Palopoli
1 Rookie
•
32 Posts
0
July 5th, 2017 07:00
Thanks a lot Geordie!
I was confused because some docs pointed out: "download the CB Windows client" (DOC-52445).
geordiekorper
22 Posts
1
July 5th, 2017 07:00
Got it. The Windows client is used for the NetBackup workflow which does not have CloudBoost built-in. In that workflow the standalone CloudBoost client mounts the CloudBoost device as if it were a Windows share (UNC path) which NetBackup can then use to store its backup containers. The document you are referring to was suggesting you that you could also use that client to test CloudBoost connectivity from any Windows computer, such as your admin workstation. Support uses it this way because for basic connectivity troubleshooting it is often more convenient to be able to test directly from a specific computer without having to switch to the NetWorker console and trigger a backup.