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
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.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
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, test, test before you do anything drastic with it.