Sign In
Forgot Password

Don’t have an account? Create One.

Cloud Catalyst sync_to_cloud tool



Cloud Catalyst sync_to_cloud tool


The sync_to_cloud tool is designed to be run on a CloudCatalyst server. It will upload to the cloud any MSDP container and catalog files in the CloudCatalyst cache that have been modified since they were last uploaded.


Product Version:

All versions of NetBackup Cloud Catalyst


Problem Description:

This tool will primarily be used as one of the premigration steps to prepare a CloudCatalyst server for migration to MSDP Cloud. Specific information about those steps will be included in the documentation for the migration procedure.


This tool can also be used to repair a CloudCatalyst server that has gone down because the cache has become full. It is possible for CC cache to become full if

there are too many files that have not been uploaded to the cloud and CloudCatalyst will not evict any files from the cache that have not been uploaded.


When the CloudCatalyst server is down, there are no active backup or duplication jobs to trigger the upload of these files to cloud so the cache remains full and the CloudCatalyst server stays down.


This scenario is rare but it can occur when the upload bandwidth to the cloud is too small to accommodate the amount of data being written to CloudCatalyst by backup or duplication jobs (i.e., the inbound bandwidth).




NOTE: These binaries are intended to help address a certain issue or enhance

a certain feature within the Veritas software for which these binaries were

created. They are intended solely for the recipient and must not be further

distributed to other parties, as they may not be generally available. Their

use is subject to the terms and conditions of your applicable Veritas license

and support agreements. They have not been fully tested by Veritas in all

environments, so please do not install these binaries unless instructed to

do so by Veritas.

Tool Installation and Execution Instructions:


  1. Download zip file
  2. Extract sync_to_cloud and put it on the CloudCatalyst server
  3. Make certain all NetBackup services are up and running on the CC server.
  4. Make certain that NO SLP or backup or optdup jobs are or will be running when the sync_to_cloud process is started. Running backups or duplications to the CC server while the script is running could cause conflicts.
  5. Execute sync_to_cloud as root

            # ./sync_to_cloud


Note: Execute sync_to_cloud in such a way that it can run for a long period of

           time without timing out. For example, use nohup or some other method that

           will allow the command to continue even if you are disconnected to the system. 

           If there are TBs of data to upload to the cloud from CC Cache, that process

           can take a lot of time depending on available bandwidth.


       6. Monitor the /usr/openv/netbackup/logs/esfs_storage log file for "Upload is done" messages.

       7. The output from the script will be in the /usr/openv/esfs/log/ops/sync_to_cloud directory. There will be one sync_to_cloud.<pid> output file and one upload_results.<pid> output file.


Sample output (small system, not representative of amount of output for production system):


CloudCatalyst sync_to_cloud utility version 2


This utility will upload any MSDP container files (.bin/.bhd) and MSDP catalog files (po.db/ul.db) that have been modified since they were last uploaded.

It may run for a long time if there are many files to upload. Log files to monitor progress will be in: /usr/openv/esfs/log/ops/sync_to_cloud


Continue? (y/n) [n]: y


Syncing files...


Successfully synced 11034 files...

Successfully synced 12 files...


Done syncing files.


Applies to the following product releases

Update files

File name Description Version Platform Size