I am going to be rebuilding my commserve in the near future, and the IP address is going to be changing. Is there a way to 'bulk edit' all of the DIPs associated with the commserve, or will I have to do them all one by one? I thought there used to be a control panel feature that displayed all DIPs (and could edit them there) but I don't see that option.
Solved
'bulk edit' data interface pairs for commserve ?
+2Best answer by Graham Swift
Hello
I had a customer who used DIPS extensively and they were problematical to maintain over time and in their case had wrong DIPs due to OS changes etc.
We moved away from defining them in the old way in favour for using client computer groups and then using the network/subnet options to define the DIPs at the CCG level. Then all you need to do is drop the client in to the correct CCG to get the correct settings.
Far simpler to manage :)
You can probably still use the workflows/API/Qscripts above to do the same. I also did the same via scripts in workflows, ie created CCGs, DIPs and the moved clients into the groups using an input file for the initial bulk migration.
Now we don’t need to create DIPs, just drop the clients in to the right group and it just works.
https://documentation.commvault.com/2022e/expert/107131_setting_up_data_interface_pair_between_two_client_groups.html is the documentation and for me I used the CIDR format in the CCG based DIPs to cover the specific backup networks.
We now only need to manage about 60 DIPs down from about 1000.
+23- Vaulter
- 4996 replies
I’m not seeing any tool, though there is a report you can download:
https://cloud.commvault.com/webconsole/softwarestore/#!/135/663/2026
Though this only lists them.
there are several REST API options here, though:
https://api.commvault.com/#9e3cecca-d714-4acd-b7e8-e9c357cb918e
check out this one:
https://api.commvault.com/#261d13c3-7864-45a5-a49a-e565fcada6c4
That should do what you need.
+23- Vaulter
- 1300 replies
There is a way to modify en-mass using a qscript and input file:
That should be able to do what you need, although its worth experimenting beforehand.
+19- Commvault Certified Expert
- 1246 replies
Maybe its worth investigating if you could drop the use of DIPs towards the CommServe when you are going to move to a new one. I normally see the use of DIP only between MAs and clients, but it could very well be of course that your CommServe also functions as a MA.
- Vaulter
- 118 replies
I have a simple workflow if that helps.
you will need both workflows attached -
import Set Dips 1st and then set dips bulk.
You pass in a text file to this.
The file will contain a comma delimited line of the clientip, media agent ip, client name, media agent name
10.0.2.34,10.0.2.35,linux1,bcs-ma1
10.0.2.35,10.0.2.36,oracle1,bcs-ma1
When you run the workflow it will ask for the file location i.e. C:\temp\addDips.txt
Gary Seibak - TAM Commvault
1 person likes this
+11- Vaulter
- 79 replies
- Answer
Hello
I had a customer who used DIPS extensively and they were problematical to maintain over time and in their case had wrong DIPs due to OS changes etc.
We moved away from defining them in the old way in favour for using client computer groups and then using the network/subnet options to define the DIPs at the CCG level. Then all you need to do is drop the client in to the correct CCG to get the correct settings.
Far simpler to manage :)
You can probably still use the workflows/API/Qscripts above to do the same. I also did the same via scripts in workflows, ie created CCGs, DIPs and the moved clients into the groups using an input file for the initial bulk migration.
Now we don’t need to create DIPs, just drop the clients in to the right group and it just works.
https://documentation.commvault.com/2022e/expert/107131_setting_up_data_interface_pair_between_two_client_groups.html is the documentation and for me I used the CIDR format in the CCG based DIPs to cover the specific backup networks.
We now only need to manage about 60 DIPs down from about 1000.
Thanks, Graham - Note: opinions are my own :)
+10Graham Swift wrote:
Hello
I had a customer who used DIPS extensively and they were problematical to maintain over time and in their case had wrong DIPs due to OS changes etc.
We moved away from defining them in the old way in favour for using client computer groups and then using the network/subnet options to define the DIPs at the CCG level. Then all you need to do is drop the client in to the correct CCG to get the correct settings.
Far simpler to manage :)
You can probably still use the workflows/API/Qscripts above to do the same. I also did the same via scripts in workflows, ie created CCGs, DIPs and the moved clients into the groups using an input file for the initial bulk migration.
Now we don’t need to create DIPs, just drop the clients in to the right group and it just works.
https://documentation.commvault.com/2022e/expert/107131_setting_up_data_interface_pair_between_two_client_groups.html is the documentation and for me I used the CIDR format in the CCG based DIPs to cover the specific backup networks.
We now only need to manage about 60 DIPs down from about 1000.
this is the way.
The poster formerly known as @christopherlecky
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.