You searched for the word(s):
< 1 second(s)
The consolidation of the SP here might work better in conserving Tape utilization.
You can consider configuring a Global Secondary Copy (https://documentation.commvault.com/commvault/v11/article?p=11638.htm)
This will allow you to use the same Tape Media across multiple SP, which will be helpful in minimizing the tape ...
On the CommServe there is a log file call ''EvMgrS.log'', can you please share a snippet of the log when you attempt to ''Delete'' the client
This might provide more information on the cause of the error
In regards to setting up - Microsoft Failover Cluster Environment, the associated Documentation (https://documentation.commvault.com/commvault/v11_sp13/article?p=5025.htm) is correct.
From Commvault their should be a single Client, which will resolve to the client name, hostname and ip information. Then the Microsoft OS Cluster will ...
From a Commvault perspective, you can configure another Copy (pointing to the new Azure Blob) for each of the Storage Policy (that you are migrating). Then trigger an Aux copy to replicate the data using Commvault's Aux Copy operation.
By doing the above, you are able to monitor the replication job via Commvault
From the description, your primary issue sounds like a ''Read'' access issue to the Nutanix AFS SMB share, as ''Scan phase takes 10 hrs and backup phase takes more than 200 hrs. '' - which doesn't sound correct.
I would recommend to engage Support to assist with the review to determine why the Read operation on the Client is soo ...