Cool Solutions

How to Move NDPS to Another Server and/or Volume



By:

June 10, 2009 2:41 pm

Reads:5,326

Comments:0

Score:Unrated

By Ruud van der Zwet

Here are the steps to move NDPS to another server and/or volume.

Step 1: Export LDAP-file

Search through your eDirectory (LDAP) and search for all NDPS related objects and attributes.

ldapsearch -x -h "ipaddres" -p 389 -D cn="fdn" -W -b
OU="printer context fdn" -s sub "(|(objectclass=NDPSManager)
(objectclass=NDPSBroker) (objectclass=Queue))" datapoolLocations
databaseVolumeName resourceMgrDatabaseVolume Volume hostServer ACL
ObjectClass queueDirectory >/root/ndpsexport

The “ipaddress” is the ip address of a server with an eDirectory replica. On this server LDAP is listening on port 389, so in this case it is not secure.

Check if your server is listening on port 389 with netstat -nptl (for Linux) and tcpcon (for NetWare).

Step 2: Change exported file

Replace all source server/volume paths to the new destination server/volume paths with an editor.

Save this file to /root/ndpsmodified

#Don’t remove ACL’s !!!!!!

Step 3: Shutdown NDPS

Shutdown NDPS Broker and Print Manager.

Step 4: Copy NDPS data

Copy the NDPS source server/volume to the destination server/volume.

Step 5: Import the modified ldap-file

Import the file /root/ndpsmodified in eDirectory with ldapmodify.

ldapmodify -x -h "ip address" -p 389 -D cn="fdn" -W -f
/root/ndpsmodified

The “ipaddress” is the ip address of a server with an eDirectory replica.

Step 6: Start NDPS on destination server

Start the NDPS Broker first and wait a couple of minutes until everything is loaded. Then start the NDPS printmanager and check if all NDPS printers will be enabled.

Now you have moved NDPS to another server and/or volume.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading ... Loading ...

Categories: Uncategorized

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS