Problems with scripting and nsradmin after a password change

Question

Good day all, Here are the facts: NetWorker version - 8.2.4.4 NMC server installed separate from Zone Servers Migrating from an old NetWorker Server to a new NetWorker Server (same NW versions) Scripts detailed below to migrate the clients (worked last Thursday and didn't work yesterday) NetWorker password was locked over the weekend Unlocked and reset the password in AD and via NMC (unfortunately Security won't let us go longer than 90 days without a password change and I missed it this time) This is a 2 script process: nsrmig1.pl nsrmig2db.pl nsrmig1.pl creates the query to run the migration from a prepopluated text file that contains only client names: #!/usr/bin/perl # # nsrmig1.pl - Extract key information about NSR clients and prepare client create syntax for migration. # # Check for presence of file given as argument. if ( ! -f $ARGV[0] ) {   die 'No such file '$ARGV[0]'.'; } # Read file for list of clients. open(CLIENTS,'$ARGV[0]') || die 'Cannot open file '$ARGV[0]' for reading.'; @clients = ; close(CLIENTS); # Open search output file. open(SEARCH,'>$ARGV[0].mig1') || die 'Cannot open search file for output.'; print SEARCH 'show name;client id;comment;parallelism;save set;scheduled backup;aliases

'; # Iterate over clients to create the search syntax. foreach $client (sort @clients) {   chop($client);   print SEARCH '. type:nsr client;scheduled backup:enabled;name:${client}
p

'; } # Close the search output file. close(SEARCH); exit(0); The 2nd file nsrmig2db.pl creates the 'create' and 'disable' files to be run against the gaining NetWorker Zone Server (file_name.create) and against the losing NetWorker Zone server (file_name.disable) #!/usr/bin/perl # # nsrmig2.pl - Extract key information about NSR clients and prepare client create syntax for migration. # use POSIX qw(strftime); # Check for presence of file given as argument. if ( ! -f $ARGV[0] || ! -f '$ARGV[0].mig1' ) {   die 'No such file '$ARGV[0]/$ARGV[0].mig1'.'; } # Check for server name as argument. if ( length($ARGV[1]) == 0 ) {   die 'No server name given.'; } # Run the search. Massage output. my $searchout = qx#/usr/sbin/nsradmin -s $ARGV[1] -i $ARGV[0].mig1#; $searchout =~ s/Current query set//g; $searchout =~ s/;
 */;/g; $searchout =~ s/
 */
/g; $searchout =~ s/ [\]
/ /g; $searchout =~ s/;parallelism: 4;/;/g; $searchout =~ s/;comment: ;/;/g; $searchout =~ s/;save set: All;/;/g; # Debug # print $searchout; exit(0); # Client creation output. my $createout = $searchout; $createout =~ s/name:/
create type: nsr client;name:/g; $createout =~ s/client id: [0-9a-z\-]*;//g; $createout =~ s/name:/group: cloud-db-%;retention policy: 6 weeks;browse policy: 6 weeks;name:/g; # Iterate over entries and assign a group. my @groups = ('a', 'b', 'c', 'd', 'e', 'f', 'g'); my $cnt = 0; while ( index($createout,'%') != -1 ) {   $createout =~ s/%/$groups[$cnt]/;   $cnt = 0 if $cnt++ > 5; } # Debug #print '$createout
'; exit(0); # Write create script. open(CREATE,'>$ARGV[0].mig2.create') || die 'Cannot create file: $ARGV[0].mig2.create'; print CREATE '$createout
'; close(CREATE); # Client disablement output. open(DISABLE,'>$ARGV[0].mig2.disable') || die 'Cannot create file: $ARGV[0].mig2.disable'; my $disableout = $searchout; foreach $client ( grep(/name:/, split('
',$disableout)) ) {   $client =~ s/.*name: //;   $client =~ s/;.*//;   print DISABLE '. type: nsr client;scheduled backup:enabled;name: $client
update scheduled backup:disabled;comment: \'DISABLED - Migrated - DO NOT ENABLE - ' . strftime('%Y%m%d', localtime) . '\'

'; } close(DISABLE); # Debug #print '$disableout
'; exit(0); exit(0); Like I said before, it was running perfectly fine Thursday and yesterday it no longer runs.  What I find interesting is I can connect to nsradmin and run the commands to obtain the information interactively.  However, offline / non-interactively, I receive the message in the file_name.create file: No resources found for query: create type: nsr client; group: group_name;retention policy: 6 weeks;name: client_name ;scheduled backup: enabled;type: nsr client; The output from Thursday was like this: create type: nsr client;group: group_name;retention policy: 6 weeks; browse policy: 6 weeks;name: client_name;scheduled backup: Enabled; comment: Any comments included in the comment field;save set: 'Save sets';aliases: alias1,alias2;parallelism: 8; I'm assuming there is something in the background I have missed when I changed the password via the following steps after changing it in Active Directory: Log into NMC Click Setup button Click Setup (menu) Configure Login Authentication Ensure External Repository is selected and click Next Change the password on each Authority servers (Do not cut and paste) Click Next Click Next Click I did see the following message on the 'older' servers; 'Unable to retrieve data while parsing lockbox phrase.  The lockbox phrase has an invalid format.'  My peer who has been here considerably longer than I said this is routine behavior after a password change Coincidentally, there is nothing written to the daemon.raw log since I updated the password. Any help is greatly appreciated as I still have over a thousand clients to migrate from 2 older zone servers that are being replaced by the zone servers. Sincerely, Lee

higgie1 · Accepted Answer

All,

So, I thought I would look a little closer at the previous files that were created that were successful and the one that I most recently created that is not successful. They all looked the same. Until I looked at the non printing characters and that is where the difference is:

Successful output of the first script using cat -An filename:

130 . type:nsr client;scheduled backup:enabled;name:server_name $

131 p$

132 $

Now the most recent output with the same cat command:

25 . type:nsr client;scheduled backup:enabled;name:server_nameM-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- M-BM- $

26 p$

27 $

So, now to figure out the differences between the two cases. They were both called using the same command:

./nsrmig1.pl file_name

After using the familar command:

tr -cd '\11\12\15\40-\176' < badfile > cleanfile

This now shows accurately:

25 . type:nsr client;scheduled backup:enabled;name:server_name$

26 p$

27 $

So, I will mark this as answered.

higgie1 · Answer

All, I forgot to mention all the zone servers but one is running in RHEL 6.8 & 7 and one in Windows 2008. Thanks, Lee

higgie1 · Answer

All,

I guess, really what my question is why would all of a sudden (only after a password change) would a script that worked perfectly fine all of a sudden stop working?

There must be something I'm missing in regards to the password change, but for the life of me, I cannot figure it out. Everything else is running fine. No issues with the back ups.

Thank you all in advance.

Sincerely,

Lee

NetWorker

Was this post helpful?