05-16-2022 06:02 AM
Hello,
I got 2 Clusters (exactly the same version ==> 12.5.1).
Using the CLI command "utils disaster_recovery , I have the following completion options on Publisher Cluster #1 :
admin:utils disaster_recovery
utils disaster_recovery backup*
utils disaster_recovery cancel_backup
utils disaster_recovery device*
utils disaster_recovery estimate_tar_size
utils disaster_recovery history
utils disaster_recovery jschLogs
utils disaster_recovery prepare*
utils disaster_recovery restore*
utils disaster_recovery schedule*
utils disaster_recovery show_backupfiles
utils disaster_recovery show_registration
utils disaster_recovery status
And on the second Cluster (from publisher) I have :
admin:utils disaster_recovery
utils disaster_recovery backup*
utils disaster_recovery cancel_backup
utils disaster_recovery device*
utils disaster_recovery estimate_tar_size
utils disaster_recovery history
utils disaster_recovery jschLogs
utils disaster_recovery restore*
utils disaster_recovery schedule*
utils disaster_recovery show_backupfiles
utils disaster_recovery show_registration
utils disaster_recovery show_tapeid
utils disaster_recovery status
Why do not I have same options ? Especially why do not I have "utils disaster_recovery prepare" on the first Publisher ?
Solved! Go to Solution.
05-30-2022 01:36 AM
Issue is now fixed.
To fix the issue, the workaround is to suppress the "cliCommands.xml" file (need root login access, means that you need to contact the TAC). Your next session (as "administrator" user) will re-create the "cliCommands.xml" file when starting CLI ... and then everything will be ok.
05-16-2022 06:16 AM
Hi,
for the first command utils disaster_recovery prepare*:
Have you already added any subscribers? I guess, this command is only visible, as long as it's a single-node cluster (so only the pub).
for the second command utils disaster_recovery show_tapeid:
This command is not mentioned in the CLI reference guide at all.
05-16-2022 06:27 AM
Thanks for your answer.
In fact, my Clusters already exist (1 Pub and 8 Sub in each Cluster).
All nodes are also authenticated. "callmanager DBSub authenticated" when I tape "show network cluster".
05-30-2022 01:36 AM
Issue is now fixed.
To fix the issue, the workaround is to suppress the "cliCommands.xml" file (need root login access, means that you need to contact the TAC). Your next session (as "administrator" user) will re-create the "cliCommands.xml" file when starting CLI ... and then everything will be ok.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide