Unsolved
This post is more than 5 years old
72 Posts
0
3177
April 27th, 2007 06:00
Unable to extract resource info for client...
Hi,
we are going to migrate to a new windows domain from old windows domain and now im performing tests.
after migration I have problems with backup of the clients,
I get "Unable to extract resource info for client". I thought it can be related with naming resolution but it resolves OK using servername.old.domain.com and using servername.new.domain.com, IP of the server is not changed. res\servers file changed and services restarted.
What I did wrong? maybe some additional steps are required when migrating to new domain? btw. aliases also added to use servername.old.domain.com and servername.new.domain.com
we are going to migrate to a new windows domain from old windows domain and now im performing tests.
after migration I have problems with backup of the clients,
I get "Unable to extract resource info for client". I thought it can be related with naming resolution but it resolves OK using servername.old.domain.com and using servername.new.domain.com, IP of the server is not changed. res\servers file changed and services restarted.
What I did wrong? maybe some additional steps are required when migrating to new domain? btw. aliases also added to use servername.old.domain.com and servername.new.domain.com
ble1
4 Operator
•
14.4K Posts
0
April 27th, 2007 06:00
ble1
4 Operator
•
14.4K Posts
0
April 27th, 2007 06:00
mdabasinskas
72 Posts
0
April 27th, 2007 06:00
but im trying to backup only backup server it self and I get:
1 retry attempted
save: RAP error: Unable to extract resource info for client servername.new.domain.com.
save: Cannot open save session with servername.new.domain.com
mdabasinskas
72 Posts
0
April 27th, 2007 07:00
removed from aliases servername.old.domain.com and restarted server.
but I lost indexes and it created new folder servername.new.domain.com
to resolve this problem, is it enough to stop services, copy everything from servername.old.domain.com to servername.new.domain.com and start services?
because index folders of client computes have no suffixes in their folders, but backupserver index folder is with fqdn (old.domain.com and new.domain.com)
mdabasinskas
72 Posts
0
April 27th, 2007 07:00
stopped networker services.
rejoined to a new domain,
rebooted services.
Networker started without any problems, it could find indexes of my backup server and so on. but backup did not started,
when I've added into aliases:
servername.new.domain.com
servername.old.domain.com
servername
previously aliases were:
servername.old.domain.com
servername
axavier1
76 Posts
0
April 27th, 2007 11:00
I suggest you read this document carefully:
https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1/en_US/ESG_Legacy_Conversion/Support/Bulletins/396.htm
this document describe how to rename a networker server correctly.
Regards,
Anderson
xvan_egmond
74 Posts
0
April 27th, 2007 12:00
if you are using shortname for the client-name, this can also be a networker issue where /nsr/tmp holds some info on the client-name.
Depending on your version of networker (I think 7.1.2 and older have this issue), you may want to stop networker server, remove /nsr/tmp, and then start networker server. /nsr/tmp will be recreated at startup of networker.
Try to backup client now.
This issue should be solved in versions 7.2.2 and later.
goodluck,
Xander