Hello again - no, the agent should not restart after the import of the backup .def file. For some reason it was down when you issued the enableRule command. Check the log file for the possible cause.
Ah, the error is caused by the fact that the EMC Mirror Data Sources do not get completely recreated when importing the backup file. That s because the mirror data source and corresponding services store the confguration in the registry. Importing the backup file recreates the configuration of the data sources in Autostart config, but not the registry part. Unfortunately these data sources have to be recreated manually. It still should no cause the backbone to restart at least from my experience.
After the AutoStart is installed, the "MirrorUnconfig.log" is there.
I use one backup.def configured by us own to restore the AutoStart configuration.
After investigation, I found out that the agent restart was caused by the misconfiguration of the backup.def.
There is one field called nodefd, after I wrote the IP address of my PC to the "source.addr" field, then after restore, the agent wasn't restarted.
nodefd server1{
nodeAddrs = {
{
sourceType = domain
source.addr = 172.21.1.153
destination.addr =
}
{
sourceType = domain
source.addr = 172.21.1.153
destination.addr =
}
}
mirrorInfo.address =
mirrorInfo.partner.nodeName =
}
So I want to ask one question, is anyone know the what does this field relate with? Is it specify the NIC IP of my PC? How will this field affect the AutoStart behavior? Is there corresponding field in the console?
daniel_vongehr
34 Posts
0
May 14th, 2010 01:00
Greetings,
I am out of the office and unavailable the week of Monday 10-May-2010
through Friday 14-May-2010. I will return Monday, 17-May-2010.
If assistance is needed with an existing service request please contact
support by phone at 1-877-534-2867 and the next available Technical
Support Engineer will be able to assist you.
If this is a new symptom, please don't hesitate to open a new case by
phone at 1-877-534-2867 or via the Powerlink web site at
http://powerlink.emc.com.
Best Regards,
Daniel
tribicic
157 Posts
1
May 14th, 2010 02:00
Hello again - no, the agent should not restart after the import of the backup .def file. For some reason it was down when you issued the enableRule command. Check the log file for the possible cause.
EnvisionPlus
79 Posts
0
May 14th, 2010 02:00
Thanks for your reply.
After the Agent restarted, I can enable the rule manually. So is it possible the problem is with the backup.def?
I've checked the file "autoRecover.log" under "C:\Program Files\EMC\AutoStart\ENvPlus\log\agent", the content is as follows:
daniel_vongehr
34 Posts
0
May 14th, 2010 02:00
Greetings,
I am out of the office and unavailable the week of Monday 10-May-2010
through Friday 14-May-2010. I will return Monday, 17-May-2010.
If assistance is needed with an existing service request please contact
support by phone at 1-877-534-2867 and the next available Technical
Support Engineer will be able to assist you.
If this is a new symptom, please don't hesitate to open a new case by
phone at 1-877-534-2867 or via the Powerlink web site at
http://powerlink.emc.com.
Best Regards,
Daniel
tribicic
157 Posts
1
May 14th, 2010 02:00
Ah, the error is caused by the fact that the EMC Mirror Data Sources do not get completely recreated when importing the backup file. That s because the mirror data source and corresponding services store the confguration in the registry. Importing the backup file recreates the configuration of the data sources in Autostart config, but not the registry part. Unfortunately these data sources have to be recreated manually. It still should no cause the backbone to restart at least from my experience.
daniel_vongehr
34 Posts
1
May 14th, 2010 02:00
Greetings,
I am out of the office and unavailable the week of Monday 10-May-2010
through Friday 14-May-2010. I will return Monday, 17-May-2010.
If assistance is needed with an existing service request please contact
support by phone at 1-877-534-2867 and the next available Technical
Support Engineer will be able to assist you.
If this is a new symptom, please don't hesitate to open a new case by
phone at 1-877-534-2867 or via the Powerlink web site at
http://powerlink.emc.com.
Best Regards,
Daniel
daniel_vongehr
34 Posts
0
May 14th, 2010 02:00
Greetings,
I am out of the office and unavailable the week of Monday 10-May-2010
through Friday 14-May-2010. I will return Monday, 17-May-2010.
If assistance is needed with an existing service request please contact
support by phone at 1-877-534-2867 and the next available Technical
Support Engineer will be able to assist you.
If this is a new symptom, please don't hesitate to open a new case by
phone at 1-877-534-2867 or via the Powerlink web site at
http://powerlink.emc.com.
Best Regards,
Daniel
EnvisionPlus
79 Posts
0
May 14th, 2010 05:00
Thanks for your timely reply!
After the AutoStart is installed, the "MirrorUnconfig.log" is there.
I use one backup.def configured by us own to restore the AutoStart configuration.
After investigation, I found out that the agent restart was caused by the misconfiguration of the backup.def.
There is one field called nodefd, after I wrote the IP address of my PC to the "source.addr" field, then after restore, the agent wasn't restarted.
nodefd server1{
daniel_vongehr
34 Posts
0
May 14th, 2010 05:00
Greetings,
I am out of the office and unavailable the week of Monday 10-May-2010
through Friday 14-May-2010. I will return Monday, 17-May-2010.
If assistance is needed with an existing service request please contact
support by phone at 1-877-534-2867 and the next available Technical
Support Engineer will be able to assist you.
If this is a new symptom, please don't hesitate to open a new case by
phone at 1-877-534-2867 or via the Powerlink web site at
http://powerlink.emc.com.
Best Regards,
Daniel
EnvisionPlus
79 Posts
0
May 15th, 2010 05:00
In Legato5.1 we didn't set the IP here, but the backup.def can be well restored without restart.
do you know the difference in Legato5.1 and AutoStart 5.3?
EnvisionPlus
79 Posts
0
May 15th, 2010 07:00
After several times test, I found if I delete the Nodefd {} filed in my backup.def, then the restore won't let the agent restart.
Also I export the domain information before and after I restore my backup.def to two files, I found the Nodefd() field were the same.
Now I want to ask you one question, if I didn't set this filed, if there will be some problem?
And is there some difference effect to the Domain between not setting the Nodefd{} field and setting the Nodefd{} as the following?