+4
Hello, everyone.
I need your support.
For the past week the "Metallic" backup when doing a Syntethic Full gives this error: "Index server is disabled on the Media agent [service_2019].
Source: cms01102c1eu06, Process: StartSynthFull".
I restarted the MediaAgent "service_2019" but the problem is still there.
I ask for your help, how can I solve it?
Thank you
Carmine
+11
Hello
Please let us know if you have adequate space on the install directory of the server? Is check readiness passing for this MA?
Also, what is the Index cache location path on this MA? If that’s full as well, you may need to increase some space on it.
Best,
Rajiv Singal
+4
Hi Rajiv,
the space available on the MA server 'service_2019' is 9.81 GB.
It is the only MA available, there are no others.
The index cache location path on this MA is “C:\Program Files\Metallic\ContentStore\IndexCache”
and the space occupied is 22,1 gb
Can you explain to me in a very simple way what to do?
Thanks
Carmine
+11
Hello
Please navigate to client computers > Select the MA > Right Click > All task > Check readiness.
Best,
Rajiv Singal
+4
Bye,
I am using Metallic
and the Check readiness is ready for all VM
+11
On the MA, can you please check the value of DISABLE_INDEX_SERVER in registry? You can simply use find once you have opened the registry.
Also, if you right click on the MA > Properties > Advanced > Additional settings. What is the value there? It should be 0 if you need Index server enabled on this MA.
Best,
Rajiv Singal
+4
Bye,
I went into Regedit and searched for the DISABLE_INDEX_SERVER value but found nothing.
Can you tell me in which path to create the dword and what value to give it?
Thanks
Carmine
+11
You can directly make additional setting from commcell and it will list under registry of the client. Client computers> right click on the MA > Properties > Advanced > Additional settings add the DISABLE_INDEX_SERVER as the additional setting with value as 0.
Reference doc: https://documentation.commvault.com/additionalsetting/details?name=%22DISABLE_INDEX_SERVER%22&id=6259
Do restart the MA services after adding the setting.
Best,
Rajiv Singal
+4
Bye,
I repeat that I am using Metallic's commandcenter
"https://m102.metallic.io/commandcenter" and I cannot find the directions you propose.
Also, redoing the "check readiness" I get this result:
+11
My bad
Best,
Rajiv Singal
+4
I did the test again and the result is as follows:
+11
Best,
Rajiv Singal
+5
Hi,
You can add more space first, 50 GB at C drive will be enough just for the OS in 2023. Metallic will take additional 50-200 GB depending on amount of data handled.
+2
Good Day
Apologies for the confusion here. I do see the Media Agent is online now, without any issues.
In order, to clarify why the Media Agent was offline even though you had an free spacing of 9.81 GB is that - with Metallic, by default we define an frequency when the Media Agent needs to go to offline to avoid any potential crashes at the OS level getting the Disk filled up, and by Default if the Index Cache path get’s lesser than 10 GB the Index Cache will be taken automatically to offline mode.
Reference for you:
So, you can always ensure the Index Cache path holds an spacing more than 10 GB, if not that’s expected to have the Index cache to be offline by default with Metallic.
Hope this clarifies over the reason why the MA was offline, let me know if you need any further queries or concerns, thank you!
Cheers,
Arvind - Metallic Specialist.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
