You mean the cloning status on the monitoring tab of your NMC ? os it the replication status on the DD ? If the group is marked as complete then it should always be 100% completion status.
NMC and server are same version? You can try to clean java cache though I doubt it will help (I have currently one server which keeps changing displayed value to enable/disabled all the time and it is specific only to that one server no matter which NMC I use - so it seems like the way how server communicated data back to NMC pull might affect what/how is displayed).
8.1.1.x NMC act funny for me too.. The week old jobs that were sucsess full earlier suddenly get displayed as aborted. I am yet to rename the tmp and jobsdb on it and see if that helps but for now it continues to act this way.
crazyrov
4 Operator
•
1.3K Posts
0
October 8th, 2014 01:00
You mean the cloning status on the monitoring tab of your NMC ? os it the replication status on the DD ? If the group is marked as complete then it should always be 100% completion status.
Sadhbh1
1 Rookie
•
16 Posts
0
October 8th, 2014 05:00
Hi Crazyrov,
Thanks for your reply.
It is the clone status in the group details. see below.
Thanks again
crazyrov
4 Operator
•
1.3K Posts
0
October 8th, 2014 06:00
Can you get the "Total Size" displayed on the clones status window. Just to compare the sizes.
Sadhbh1
1 Rookie
•
16 Posts
0
October 8th, 2014 08:00
The size of the clone do match what was backed up, which makes me think that all is good, however it looks bad when it say only 50% completed...
ble1
4 Operator
•
14.4K Posts
0
October 9th, 2014 00:00
NMC and server are same version? You can try to clean java cache though I doubt it will help (I have currently one server which keeps changing displayed value to enable/disabled all the time and it is specific only to that one server no matter which NMC I use - so it seems like the way how server communicated data back to NMC pull might affect what/how is displayed).
crazyrov
4 Operator
•
1.3K Posts
0
October 9th, 2014 00:00
8.1.1.x NMC act funny for me too.. The week old jobs that were sucsess full earlier suddenly get displayed as aborted. I am yet to rename the tmp and jobsdb on it and see if that helps but for now it continues to act this way.