OES2.3 to OES11.1 on VMware

Greetings,
We are about to start our journey on migrating our OES2.3 servers to
OES11.1 using the Transfer ID. We have used this process before many
times for migrations and my question is not really about that process,
but more on the planning for roll back in case something goes wrong
during the Transfer ID.
According to the documentation, it is advised to perform an eDir backup
prior to start. Since both our source and target servers are on VMware,
we were discussing shutting down both source and target to get a cold VM
snapshot prior to the Transfer ID process.
Since I have never rolled back a server from a VM snapshot before with
eDirectory, could this introduce issues into our eDirectory environment?
Any insight would be appreciated.
Thanks!
~Don

On 07.11.2013 17:29, Don wrote:
> Greetings,
>
> We are about to start our journey on migrating our OES2.3 servers to
> OES11.1 using the Transfer ID. We have used this process before many
> times for migrations and my question is not really about that process,
> but more on the planning for roll back in case something goes wrong
> during the Transfer ID.
>
> According to the documentation, it is advised to perform an eDir backup
> prior to start. Since both our source and target servers are on VMware,
> we were discussing shutting down both source and target to get a cold VM
> snapshot prior to the Transfer ID process.
>
> Since I have never rolled back a server from a VM snapshot before with
> eDirectory, could this introduce issues into our eDirectory environment?
Yes, absolutely. The transfer ID activity at all stages makes extensive
eDirectory changes that cannot be simply undone by going back in time on
just one server. You introduce a new (temporary) server into the tree,
remove it again, and make quite a few changes to eDir when the OES2 gets
updated to OES11, e.g around the proxy users for the server.
Nothing here is a full showstopper, but it takes a lot of planning and
extensive in-depth knowledge to backout of a transfer ID either way.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

Similar Messages

Best plan for this scenario (migrate oes2 to oes11)

Hi there!
I would like to ask you guys the best plan for migrate a few servers that I have
in oes2 to oes11.
I have four servers in oes2sp2/sp3, these servers have a few NSS
volumes over NCS. Also I have my iPrint service on two machines,
also using NCS. I have one cluster between two machines and
other cluster between the other two machines. For exmaple,
machine1 and machine2, three NSS volumes (every NSS volume is a cluster
resource) and other resource in the same cluster for iPrint. Cluster: CL1
machine3 and machine4, one NSS volume (for other people in the company)
in other cluster. Cluster: CL2. In this cluster only have a NSS volume/resource.
Machine1/3 are physical, machine2/4 are virtual (vmware)
My CA is in other server that I will migrate after a while. So, It seems that there is
no problem with the certificate. Machine1 and machine3 are a replica for the eDir in
my organization.
My plan: I have deployed two virtual machines and one physical with oes11sp1 and sles11sp2.
I think that the best plan is migrate with migration tool iPrint first, like a cluster resource,
and NSS volumes, and after that, make a transfer ID (like a different project)
For machine1/3, move NSS volumes and after, make a transfer ID.
Is this correct? I dont know If I have to delete the current clusters (cl1 and cl2) and
create new ones, after that, create every resource as It was on the old ones.
thank you so much !
Antonio.

Originally Posted by kjhurni
This is just my opinion, of course, but:
If you don't want to have to migrate your NSS data and keep the same server names/IP/s and cluster load scripts, then I believe a Rolling Cluster Upgrade is a good way to go.
If you look in my signature, there's a link to my OES2 guides. Somewhere there is one that I did for our Rolling Cluster Upgrade.
If all you have is NSS and iPrint, then you only need to use the miggui (migration utility) for iPrint--or so I think (I do have to followup on this one as I vaguely recall I asked this a while back and there may have been a way to do this without migrating stuff again).
But your NSS data will simply "re-mount" on the OES11 nodes and you'll be fine (so that's why I like the rolling cluster upgrades).
Let me double-check on the OES2 -> OES11 cluster option with iPrint.
--Kevin
Thank you Kevin for your answer.
Finally, I think Im going to proceed using transfer ID on my servers that Im only using NSS over NCS (I only have two machines with one NSS volume)
because it seems that its a good option. I would like to keep old IPs from all the servers, cluster and resources if possible. So, testing this
migration on my test environment it seems that it works fine:
- I use miggui for transfer id between all the machines: physical -> physical and virtual -> virtual. eDirectory assumes new hostname, IP, etc.
the only task "out of the box" is that I have to delete the cluster and regenerate (reconfigure NCS on the new servers) but its pretty easy. This way
I have the two old ips from the older machines and all the ips from the cluster and the cluster resources also. I think that its the best plan.
For the other two machines that has 4 nss volumes and iPrint I must think about a plan. But with those, Im going to proceed this way. I hope
I have chosen a good plan!
thank you so much all for your answers / advices

Needing to migrate/upgrade NSM 3.02.76 from OES2 to OES11

Currently running on OES2 SP2a server. NSM version 3.0.2.76
Need to upgrade to new server. New server is OES11 SP1. Also would like to upgrade to latest NSM version.
Do I need to upgrade in place now and then move to new server? Can OES2 SP2a even run NSM 3.1?
Looked at documentation some, but don't see clear process on moving NSM to new server.
I didn't find any tips in the Discussion forum.
You've given me tips in the past and they have always worked great.
Can you point me to documentation and give best practices in making this upgrade and change.
Any assistance is greatly appreciated.
thanks,
Lin

For the benefit of others doing the same, I'd migrate then upgrade. Here's how I migrated Storage Manager Engine from OES2 to OES11:
1 - Unload old Engine and disable from starting on server boot.
2 - Install NSM Engine on new server, open firewall port 3009, and configure the engine using nsmengine-config, but don't start the engine.
3 - On the new server, rename /var/opt/novell/storagemanager/engine/data to data-original
4 - Copy /var/opt/novell/storagemanager/engine/data from old server to new server, then fire-up the new Engine
5 - Run NSMAdmin against the new server and next your way through the wizard. I had to create a new NSMProxy user, but you can use the existing NSMAdmins group.
6 - Reconfigure Event and Agent servers to point to the new Engine.
Regards,
Anthony

Miggi tool, issue migrating OES2 to OES11

I have had this issue at three consecutive sites of late. All in the process of doing transfer id of OES2sp3 to OES11sp1. Each server also has been a DNS/DHCP server as well. I am basically shutting down those services beforehand, and doing the transfer id. All prerequisites have been done beforehand, and the pre checks and health checks pass fine. The process hangs all three times on the last part on the LUM transfer. It simplys hangs on the process and want finish. I actually opened an SR on one of the boxes the first time and Novell had me kill the process to let it finish. Problem is that is fouls up the LDAP and SSL certs and all of it has to be done manually afterwards. If this was one site I would let it ride, but since I have had three separate customers who I ran into this issue on each one makes me feel something else is going on. Now, this is the first times I have done transfer id going to OES11sp1. I have done many going from NetWare and OES2 to OES11, so not sure if issue in OES11sp1?? Anyway, just thought I would see if anyone else had run into this issue. I have more to do this year so would like to know what is causing this issue.

Looks like from the SR, it has multiple issues. First the server has issues with certificates and post recreation it went through and next is the nam commands were failing.
My suggestion is verify the nam preferred-server on the target server before TransferID is accessible or not and if not point to a proper ldap server in the tree.
Also make sure that you have patched the server to the latest and the certificates of the server and as well as tree are valid.
If by any chance TransferID UI is closed for any reason, you can execute the remaining TransferID steps using command-lines documented in the guide.
-Ramesh
>>> jlewter<[email protected]> 08/12/2013 08:06 PM >>>
SR was 10847842383
Here is the migration log:
2013-07-30 15:21:50,495 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 15:21:50,495 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 15:21:50,496 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 15:21:50,599 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 15:21:50,600 INFO - ServerIDSwap:ndscheck:
2013-07-30 15:21:50,600 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 15:21:50,600 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 15:21:50,603 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:50:37,147 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:56:46,871 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:namconfig:/etc/nam.conf
file exists. Moving it to /etc/nam.conf.migsave
2013-07-30 16:56:46,887 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:57:39,239 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:57:56,595 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Starting to
execute NDSRepair command
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndsrepair -U
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:No log messages willbe updated during the execution
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:04:34,314 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:04:34,447 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:04:34,448 INFO - ServerIDSwap:ndsconfig:Executing
Command: /opt/novell/eDirectory/bin/ndsconfig add -m sas -a
"admin.chatham" -w env:ADM_PASSWD --config-file
/etc/opt/novell/eDirectory/conf/nds.conf
2013-07-30 17:04:55,463 INFO - ServerIDSwap:LUM Repair:ndsconfig add
-m sas returned...
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:11:06,175 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:11:06,315 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
CN=utility.chathamhall.org, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
OU=Organizational CA, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 17:11:07,519 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 17:11:07,616 INFO - ServerIDSwap:ndscheck:
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:ExecutingCommand: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 17:17:25,527 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
Here is part from serverswap log:
2013-07-30 15:21:50,495 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 15:21:50,495 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 15:21:50,496 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 15:21:50,599 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 15:21:50,600 INFO - ServerIDSwap:ndscheck:
2013-07-30 15:21:50,600 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 15:21:50,600 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 15:21:50,600 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 15:21:50,602 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 15:21:50,602 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 15:21:50,603 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:50:37,147 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:50:37,159 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:56:46,871 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 16:56:46,872 INFO - ServerIDSwap:namconfig:/etc/nam.conf
file exists. Moving it to /etc/nam.conf.migsave
2013-07-30 16:56:46,887 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 16:56:46,887 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 16:57:39,239 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM Repair:
2013-07-30 16:57:39,239 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 16:57:56,595 INFO - ServerIDSwap:Repair:Starting repair
phase......
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Starting to
execute NDSRepair command
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsrepair:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndsrepair -U
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:57:56,595 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 16:58:23,257 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:04:33,314 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:04:34,314 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:04:34,447 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:04:34,448 INFO - ServerIDSwap:ndsconfig:Executing
Command: /opt/novell/eDirectory/bin/ndsconfig add -m sas -a
"admin.chatham" -w env:ADM_PASSWD --config-file
/etc/opt/novell/eDirectory/conf/nds.conf
2013-07-30 17:04:55,463 INFO - ServerIDSwap:LUM Repair:ndsconfig add
-m sas returned...
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing ndsd
restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd restart
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:Time taken to execute
this command depends on the size of the DIB and tree
2013-07-30 17:04:55,464 INFO - ServerIDSwap:ndsd:No log messages will
be updated during the execution
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:ndsd restart command
returned...0
2013-07-30 17:11:05,175 INFO - ServerIDSwap:ndsd:Waiting for ndsd to
restart
2013-07-30 17:11:06,175 INFO - ServerIDSwap:ndsd:Executing Command:
/etc/init.d/ndsd status
2013-07-30 17:11:06,315 INFO - ServerIDSwap:ndsd:ndsd status command
returned...
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
CN=utility.chathamhall.org, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:Owner:
OU=Organizational CA, O=CHATHAM
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:11:07,519 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
2013-07-30 17:11:07,519 INFO -
ServerIDSwap:ndsconfig:Servercertificate is updated correctly
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
ndscheck to check status of edirectory on this server
2013-07-30 17:11:07,519 INFO - ServerIDSwap:ndscheck:Executing
Command: LC_ALL=en_US.UTF-8 /opt/novell/eDirectory/bin/ndscheck -h
utility.chathamhall.org -a "admin.chatham" -w env:ADM_PASSWD -F
"/var/opt/novell/migration/NewProj1/ndscheck.log"
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
start**********************************
2013-07-30 17:11:07,616 INFO - ServerIDSwap:ndscheck:
2013-07-30 17:11:07,616 INFO -
ServerIDSwap:ndscheck:*****************Command output
end**********************************
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:ndscheck flagged
warnings
2013-07-30 17:11:07,616 WARN - ServerIDSwap:ndscheck:For more
information, check ndscheck.log located at
/var/opt/novell/migration/NewProj1
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
preferred-server from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Reading
alternative-ldap-server-list from
/var/opt/novell/migration/NewProj1/nam.conf.target
2013-07-30 17:11:07,617 INFO - ServerIDSwap:namconfig:Executing
nam-reconf.rb to create Unix Workstation object...
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:reading LUM
base name from /var/opt/novell/migration/NewProj1/nam.conf
2013-07-30 17:11:07,617 INFO - ServerIDSwap:LUM Repair:Executing
Command: ruby
/opt/novell/migration/sbin/serveridswap/scripts/repair/nam-reconf.rb -a
"cn=admin,o=chatham" -S "172.16.1.1" --ldap-port 636 -u "o=chatham"
2013-07-30 17:17:25,527 ERROR - ServerIDSwap:LUM Repair:Command failed
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
start**********************************
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Information:
executing command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l
636
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:Fatal: Failed
to execute the command: LC_ALL=en_US.UTF-8 /usr/bin/namconfig add -a
"cn=admin,o=chatham" -r "o=chatham" -w "O=Chatham" -S 172.16.1.1 -l 636
with result:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM Repair:
2013-07-30 17:17:25,527 INFO - ServerIDSwap:LUM
Repair:*****************Command output
end**********************************
jlewter
jlewter's Profile: https://forums.novell.com/member.php?userid=14321
View this thread: https://forums.novell.com/showthread.php?t=468831

DST issues? For OES2 to OES11 upgrade?

Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php?userid=75037
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!

Originally Posted by konecnya
Hi all
I have a client with DST working well on a couple of OES2 sp3 64-bit
servers on vSphere 5.0
Does anyone here have any experience with such upgrades?
I'd be pretty sure that the one upgrade path of just rebinding the NSS
volumes to new servers would be more grief than is worth it. I'd also
like to avoid the server migration option just because of how much data
is involved, not even sure if we have enough extra space to go this
route, plus from our experience with Migrating from NW6.5 to these
boxes in the beginning (OES2 sp1 at the time) did NOT understand DST on
the destination.
Andy of
KonecnyConsulting.ca in Toronto
Knowledge Partner
View Profile: konecnya - Novell Forums
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
We just went through a round of upgrades from OES2 SP3 (physical) with and without DST to OES11/SP1 on VMware
Now, given your particular setup, I'd think you could be fine with moving the disks. In our case, we needed to do ID transfers, and that could still be done. Setup your target OES11 SP1 VM, do your iPrint, DHCP, etc. migrate them (just not the file services). Do the ID transfer. Power off source VM. "move" the NSS disks (I'm ASSUMING the NSS disks are separate VMware virtual hard disks) to the new OES11 box and voila.
The only gotcha that I can think of:
I BELIEVE that if you stored the disks with the virtual machine (default I believe), you have to be VERY VERY careful to NOT "delete from disk" when you remove the OES2 Guest, as I think it'll delete the entire underlying directory which is now where your disks are
In other words, if you SCP or something to the ESXi host and look at the directory/file structure it'll be something like:
\OES2-Guest\bunch of .vmdk files
\OES11-Gust\bunch of .vmdk files
When you "move" the virtual disks from OES2-Guest to OES11-Guest, it's just pointing to the:
\OES2-Guest\nssdisk.vmdk files
You could manually move them around I believe if you want to maintain the proper directory structure.
Personally that would probably be the biggest time saver for you.
Otherwise you COULD migrate the file systems with DST but there's some scenarios/caveats involved with that.
Let me know if you choose the route to actually migrate the DST file systems and I'll explain further.
But, if it were me, and I had them on VMware, I'd just "move" the disks around.

OES2 to OES11 (upgrade or migrate?)

GW 2012 happily working on OES 2 SP3
Obviously there is a need to upgrade to OES 11
What is easier, upgrade with bootable media or migration?
If migration how does one move GW stuff to new server?
Seb

Originally Posted by Jose
Starting from an OES2 and GW2012 server in VMWare, is it better to
upgrade to GW2012 SP1 before or after the upgrade to OES11?
No, no update to the GW SP1 code is needed, you are already running 2012 code. So there are no upgrade steps here for GroupWise, just a move.
Originally Posted by Jose
For the migration to the new server, it seems you install OES11 and GW
and then bring that OS disk into the "old" OES2 server, is that correct?
Yes, that's about it.... but also, in my setups the OES2 OS disk is a separate disk from the data disk.
After first removing the original OES2 from the tree, the OES11 disk gets attached and set as first boot disk, if the OES2 OS disk is seperate... I leave it out of the new configuration.
Then start the OES11 server - which has all the needed elements but has not been configured yet (in other words: has not been added to the tree), set server name and ip equal to the one used for the OES2 server and configure eDir and NSS services. (I always first configure eDir and NSS services... make sure that's working, and then add any other OES services... *if needed*).
As the GroupWise install stuff and agents are already in there, all that is needed is to copy the GroupWise data to a new volume (or reuse the original volume, which saves the time needed to copy over the files), reconfigure the agents as needed and start them up.
Path changes on the Linux server (like when moving the GroupWise data from an ext3 mounted partition to an NSS volume, which by default has it's mount in /media/nss/..), that can easily be handled by using a symlink (symbolic link) to have the old "path" point to the new one on the NSS volume (e.g. #ln -a [/oldpath] [/media/nss/[NSS volume]/newpath]).
This is usually not needed, as you will be supplying the new agent dib paths during configuration of them anyway. It can ease things though when old paths are causing issues with some bits.
Hope that clarifies a little more.
Cheers,
Willem

Rolling Cluster Upgrade (OES2 to OES11) - GPT partition

We've got an OES2 SP3 cluster that we'll be rolling cluster upgrading to OES11 SP2.
We are currently at max capacity for several of the NSS volumes (2 TB).
If I'm reading/interpreting the OES11 SP2 docs correctly:
AFTER the cluster upgrade is complete, the only way I can get to larger volumes will be to create new LUNs on the SAN and intialize those with GPT. Then I could do the NSS Pool Move feature to get the existing 2 TB volumes to the larger setup?
Is that correct?
Or is there a better way that doesnt' require massive downtime?

Originally Posted by konecnya
In article <[email protected]>, Kjhurni wrote:
> We are currently at max capacity for several of the NSS volumes (2 TB).
I was on the understanding that you could bind multiple partitions to
create NSS volumes up to 8TB. But I'd be hesitant to do that for a
clustered volume as well.
> I could do the NSS Pool Move feature to get the existing 2 TB
> volumes to the larger setup?
> Or is there a better way that doesnt' require massive downtime?
My first thought is the migration wizard so that the bulk of the copy can
be done while system is live but in the quieter times. Then the final
update with down time should be much faster.
But then do you really need down time for the Pool Move feature?
https://www.novell.com/documentation...a/bwtebhm.html
Certainly indicates it can be done live on a cluster with the move
process being cluster aware.
Andy of
http://KonecnyConsulting.ca in Toronto
Knowledge Partner
http://forums.novell.com/member.php/75037-konecnya
If you find a post helpful and are logged in the Web interface, please
show your appreciation by clicking on the star below. Thanks!
Migration = pew pew (re-doing IP's/etc and copying 4 TB of data is ugly especially when it's lots of tiny stuff).
haha
Anyway, when I asked about a better way that doesn't require massive downtime what I meant was:
Is there a better way vs. Pool Move that doesn't require massive downtime (in other words, the "other way" having the massive downtime, not the Pool Move).
Choice A = Pool Move = No downtime
But let's say that's not a good option (for whatever reason) and someone says use Choice B. But Choice B ends up requiring downtime (like the data copy option).
I just didn't know if Pool Move required that you create the partition ahead of time (so you can choose GPT) or if it kinda did it all for you on the fly (I'll have to read up when I get to that point).
I'm not terribly keep on having multiple DOS partitions, although that technically would work. Just always scares me. It's just temporary for the next 8 months anyway while we migrate to NAS from OES, but I'm running out of space and am on an unsupported OS anyway.

OES2 Linux iPrint on VMWare

I am looking for pepole that are running OES2 or OES1 Linux iPrint on VMWare and if you have ANY iPrint issues and what they might be.
Thanks

I am in the process of migrating iprint from a NW6sp6 server to a OES2-L server running on esx 3.x. The OES2-L server is running the i manager, driver store, and manager. It has a copy of the partition that contains the print objects. It services about 250 printers. I used SCMT to migrate the objects.
I did have some problems after the migration. All the printers seemed to have migrated OK but after I made the DNS change to get the users printing through the new server, I started seeing stability issues with the manager and corruption of the gateway load strings of the printer objects. I had not checked the gateway load strings after the migration and for the first few days when I was seeing problems I thought that a few of the printers had not migrated properly. Finally after I had a problem with one of the printers twice I came to the conclusion that it was not a migration issue. I after fighting it for a few days I migrated the users back to the old server by changing the DNS.
TID (3006957) talks about ipsmd stability issues with the RPM dated April 22, 2008. That was the rpm I was using. I deleted all of the migrated print objects, and the migrated manager. I then upgraded to the newer RPM listed in the TID after I got it from Novell. I then remigrated the manager and all of the printers and am monitoring to see if the corruption reoccurs. At this point I am suspecting that it is. Note the � at the end of the gateway load string. iprintgw PORT=LPR HOSTADDRESS=10.70.4.50 PRINTERNAME=PASSTHROUGH� That shows up if I look at the properties of the printer object or if I look at the printer agent list on the Manager. It is not showing up in the load string if I run a report from the manager health monitor. I'm not sure if is is supposed to be there or not. I'm not seeing the partial or missing load strings I was before. The stability problems I had where the manager would just crash didn't show up over night or over the weekend so I think it occurs when the server is under load.
Other than scrapping OES2-L and loading a NW6.5sp7 server and migrating to it I'm not sure what the fix might me at this point.

Upgrade OES2 to OES11 Cluster

Hi all,
we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
version running on OES11SP1. The cluster provides GroupWise, File and iPrint
Services and is connected via QLogic iSCSI HBA to our SAN.
What would you recommend how the Upgrade could be done without major
trouble?
Thanks in advance
Alex

On 16.02.2014 14:54, Alexander Lorenz wrote:
> Hi all,
>
> we plan to upgrade our 2-node Cluster running on OES2SP3 x64 to current
> version running on OES11SP1. The cluster provides GroupWise, File and iPrint
> Services and is connected via QLogic iSCSI HBA to our SAN.
>
> What would you recommend how the Upgrade could be done without major
> trouble?
There should be no trouble at all. Move all ressources to one Node, then
update the free node to OES11 as documented, move ressources to the
upgraded server, test, then do the same with the other node. But I
suggest use SP2 instead of SP1. There's really not much special on a
cluster node vs a "normal" server.
One thing you may need to check into is iPrint. If it's fully clustered,
your weg data of iPrint will reside on a clustered volume, which however
will never be available on the node that's currently upgraded, so you
likely end up with the old iPrint stuff there. Yuo may want to re-run
the iprint cluster setup script again (or if you feel able to, copy the
local iPrint data over to the cluster volume).
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

GW8.0.3hp1 OES2 to OES11 migration

Leading up to migrating our GW8 to GW2012 I need to move our GW8 system to a GW2012 supported OS as the old one is running on SLES10.2 with OES2sp1.
(I've been putting this off far too long, its too easy to delay something when there is no urgency ;) )
Our old server runs an eDir replica and uses NCP to allow access to the GW domain for C1 and client software.
Our GW is a 1 POA/MTA system that is about 25-30GB in size running on a dual quadcore with 4gb ram and serving about 150-200 users at peak time
The new server is a single socket hexacore with 16gb ram, currently set up as a pre migration server running SLES 11.2 with OES11sp1.
How I was thinking of doing this:
-shut down GW on old server.
-dbcopy from old server to nfs mount that points to the same path on the new server as the PO or Domain on the old one.
-install GW803hp1 on new server.
-Copy (and check) GW config files from old to new server.
-Migrate system ID.
-put old GW server on new IP after shutting down eDir, config new server for old IP and see if eDir is smart enough to not need a restart.
-Start GroupWise agents.
-Test.
-Depending on smoothness of migration risk upgrade to 2012 right away.
-enjoy weekend.
Does that sound about right ?
As 'disaster recovery' after the system ID migration I was thinking of just decommissioning the new server, deleting it from eDir and just re-adding the old one. There are no file systems with user rights to worry about on it.
It's probably also possible to turn the new server into a normal server, then only migrate GW and change some DNS records but our GroupWise server is of the 'old faithful' kind so I'm not sure what all is pointing directly towards its IP when it comes to things like LDAP links. This is why I am currently opting for whole server migration unless anyone else has good arguments as why not to.

Conz,
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
Has your problem been resolved? If not, you might try one of the following options:
- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)
Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php
If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.
Good luck!
Your Novell Product Support Forums Team
http://forums.novell.com/

Recommended vmware settings for OES11

Are there any recommendations for virtualizing OES11 with vmware vsphere (ESXi 4.1 or 5)?
1. While installation (near at the beginning) there is a choice for the virtualization type.
The relevant choices are "physical Computer" or "paravirtualized Computer"
Is "physical" really the best choice for vmware, because thats also the setting for fully virtualized guests.
2. SLES11 SP1 support paravitualized drivers for harddisks and usually that is a big performance boost on a suitable server (RAID Controller, SAS Drives, etc.)
What's with OES11 here even if using NSS Volumes?
thanks
Tobi

The bit about the removing and readding the NIC as VMXNET3 is unnecessary:
SLES 11.1 distribution includes a VMXNET3 driver, so you can create the VM
with a VMXNET3 NIC to begin with and have it seen during installation and
before the tools are added.
Can't say I bother with pvscsi. You only see benefits under very high I/O
load. This is outweighed for me by the nuisance value of having disk
drivers that may fail after a kernel upgrade. VMware tools are not very
robust in this respect I find.
regards
Martin
"magic31" <[email protected]> wrote in message
news:[email protected]...
>
> TFe;2163217 Wrote:
>> Are there any recommendations for virtualizing OES11 with vmware vsphere
>> (ESXi 4.1 or 5)?
>>
>> 1. While installation (near at the beginning) there is a choice for the
>> virtualization type.
>> The relevant choices are "physical Computer" or "paravirtualized
>> Computer"
>> Is "physical" really the best choice for vmware, because thats also
>> the setting for fully virtualized guests.
>>
>> 2. SLES11 SP1 support paravitualized drivers for harddisks and usually
>> that is a big performance boost on a suitable server (RAID Controller,
>> SAS Drives, etc.)
>> What's with OES11 here even if using NSS Volumes?
>>
>> thanks
>> Tobi
>
> Hi Tobi,
>
> No official word on it yet that I've seen, but the way I'm setting up
> and which is looking good:
>
> 1) Install SLES 11 using the installers virtualization type option for
> : Physical Computer
>
> 2) After having installed OES11;
> - install the latest VMware tools
> - remove the eth0 entry in /etc/udev/rules.d/70-persistent-net.rules
> (assuming single nic setup)
> - shutdown the VM and configure the Vm's SCSI controller to run in
> paravirtual mode (pvscsi) and also remove net nic and readd as VMXnet3.
>
> Boot back up again and network and disk drivers should be running as
> optimal as possible.
>
> As a note, for SLES 11 SP1 and up this is a good idea... for SLES
> 10.OES2 (that uses an older kernel) this is not such a hot idea.
> Also make sure you are either running the latest vSphere 4.1 code or
> 5.
>
> Cheers,
> Willem
>
>
> --
> Novell Knowledge Partner (voluntary sysop)
>
> It ain't anything like Harry Potter.. but you gotta love the magic IT
> can bring to this world
> ------------------------------------------------------------------------
> magic31's Profile: http://forums.novell.com/member.php?userid=2303
> View this thread: http://forums.novell.com/showthread.php?t=449924
>

Migration from Oes2 32 bit to Oes11 64

Realized my groupwise mta/gwia/webaccess is running on a 32bit Oes2 machine. Obviously cant "upgrade" that to Oes11.. so creating a new pre-migration server for it.
Straight forward? Plan on using the Transfer ID wizard to accomplish this. but then expect I need to re-install groupwise modules after. Do I need to use the groupwise migration utility as well?

Originally Posted by joebrug
Realized my groupwise mta/gwia/webaccess is running on a 32bit Oes2 machine. Obviously cant "upgrade" that to Oes11.. so creating a new pre-migration server for it.
Straight forward? Plan on using the Transfer ID wizard to accomplish this. but then expect I need to re-install groupwise modules after. Do I need to use the groupwise migration utility as well?
Hi Joe,
We're in the process of doing the above (among other things)
You have two choices:
OES2 SP3 -> OES11/SP1 migration
or
the above, but WITH ID Transfer.
It's entirely up to you if you want to keep the same servername/IP.
We chose the ID transfer.
Groupwise is VERY straight forward to go from linux to linux, IMO
However:
While we have had issues using the Novell Client for Linux (included in OES11) to migrate (via dbcopy), we have NOT had issues using the ncpmount with dbcopy. However, other people have had issues OES2 -> OES11 with ncpcmount.
There were some other intracacies with the ID transfer when going from OES2 to OES11 that I'm in the process of documenting:
a) DHCP/DNS objects/migrations are a bit odd because you'll end up with a DHCP object with the "temporary" servername of the OES11 server.
b) You'll end up with the temporary server name of the OES11 server for the OESCommonPRoxy user if you're using it. I'm currently talking to the developers to discuss a way to fix/resolve that.
However, if all you have is an OES2 server that JUST runs Gwise, then it's fairly straightforward. No need to change the case since it was already done. You'll just have to remember to copy over your .poa/.mta and any other startup files and reinstall the GW agents AFTER the ID Transfer.
I'm paraphrasing here, of course.
I'm parially through scrubbing my OES11 SP1 migration guide for incriminating IP's, etc. so hopefully I"ll have something on cool solutions next week.

Uprade a DL385 G1 to OES11 ?

Hi all: I know from a previous post that it is possible (albeit not straight forward) to do a clean install of OES11 on an HP DL385 G1 server even though it is officially not supported by HP. But how about an upgrade of OES2 to OES11? Has anyone performed an upgrade of a DL385 G1 successfully?

Originally Posted by Chris
Can you elaborate on the steps you took? Which drivers / smartstart CD you used? etc.
>>> kjhurni<[email protected]> 5/23/2013 10:56 AM >>>
Chris;2264789 Wrote:
> Hi all: I know from a previous post that it is possible (albeit not
> straight forward) to do a clean install of OES11 on an HP DL385 G1
> server even though it is officially not supported by HP. But how about
> an upgrade of OES2 to OES11? Has anyone performed an upgrade of a DL385
> G1 successfully?
We've installed OES11 (not SP1) on a DL385 G1 without problem, so I
don't see any reason why OES11 SP1 wouldn't work.
The opinions expressed are my own.
Check out my OES2 Guides:
Installing OES2 SP2:
OES2 SP2 Installation Guide | Novell User Communities
Upgrading to OES2 with ID Transfer:
OES2 SP2 Migration Guide for Transfer ID Scenarios | Novell User Communities
GroupWise Migration with OES2 ID Transfer:
GroupWise Migration from NetWare to OES2 SP2 with Transfer ID | Novell User Communities
kjhurni's Profile: View Profile: kjhurni - Novell Forums
View this thread: Uprade a DL385 G1 to OES11 ?
My co-worker actually does all the HP stuff, but he's out until Tuesday. I'll see if he remembers.
We're replacing all our servers with G6/G7 models now, because of hardware supports reasons. Further, we're putting everything into VMware now as well because there's a very good chance we may need to either also install Windows servers in our regions or migrate to Windows in a few years.
Although that brings up a whole host of other issues (HP integration with VMware for monitoring, etc.) and then we have to rely upon NAGIOS to monitor the OES Guest stuff for disk space usage, etc.

SLES sp3 w/OES11 sp2 media upgrade reboot to cursor

Pre-upgrade
Sles 11 SP2, OES11 SP1, VMware 5.1 essentials on an Gen 8 HP Proliant DL380, plenty of RAM and CPU
I ran the upgrade media on a test server and everything seemed to go fine a couple of weeks ago. My school district is on spring break, so I decided to do some upgrades. I ran the update media on our one and only file storage production server. I left the upgrade options default, only updating existing packages (I checked to make sure what we are using was upgraded) and I received no errors during the install. Upon reboot, after the VMware splash screen, it just stays at a cursor in the upper left corner of the screen. I tried to use system repair from the disk. It wanted to reinstall grub, but it hung on installing grub for 20+ minutes. I'm rerunning the repair now. Any other suggestions? I have until Monday to get this fixed. I'm avoiding using my prepaid support hours, but I have them if I need them.

Originally Posted by elphantasmo
Got the problem fixed. Called in support, and they fixed the boot loader. Took them about 2 hours of tinkering. Then it got passed off to someone who did one thing different. He ran the unsupported grub install and that seemed to fix things, after all the other tinkering. Finished the update and rebooted a few time without incident.
So you originally did an offline upgrade from OES11sp1 to OES11sp2, right?
I'm curious.... do you maybe have a separate partition for /boot?
With what you are saying I can imagine something going wrong with the offline upgrade placing/upgrading boot files in the wrong location (in the /boot folder of the root partition instead of the boot partition), resulting in booting with an old kernel and thus having a mismatch with other files/drivers/libraries that did get updated properly.
Good to hear that you were able to finish the upgrade in good order after having gotten the server boot fixed!
Cheers,
Willem

Migrating server hardware replacement oes11 to oes11sp2

This summer I will be replacing server hardware at one of my schools. Currently it has sles11sp1 / oes11 -- put in in 2012. The patches are up to date for this version, but I have not upgraded/migrated it to a newer version yet. I have played in a test environment with the yast2 wagon migration from sles11sp1/oes11 to sles11sp2/oes11sp1 -- no problems. However trying to find notes on how to do a migration and identity transfer from source server hardware to new target server hardware. Found oes11sp2 migration tool administration guide. I haven't found anything telling me how to setup sles on the target server box ie server name etc. Once I have the target sles server setup, I realize I need to install OES and select the "Novell pre-migration server" option during this installation.
Current source server = sles11sp1/oes11 and has iPrint, Nss and netstorage installed. Installed in tree with oes11 and oes11sp1 servers.
The main tree server has sles11sp2/oes11sp1 on it. We will need to upgrade it to sles11sp3/oes11sp2 this summer. I'm fine with doing the yast2 wagon migration on that server. We just haven't done server hardware replacements for OES-L yet.
Looking for some good (step by step) instructions. ;-)
Thanks
Patty

Originally Posted by amdsbnovell
Thanks Thomas. Just printed the document now. If my current sles11sp1/oes11 server is called testfs for instance, then I need to install the new target server as a sles11sp3 server called tempfs. Then install oes11sp2 into the tree in a temporary location in the tree as a premigration server (for the installation). Then I should be able to follow the instructions. When I do the identity transfer, I'm assuming it renames the sles11sp3 server from tempfs to testfs as well (as that is where oes gets the file server name from)?
Um, sorta. Let's pretend your server name is: OLD and the new one is NEW (temporary NEW name and temporary NEW IP)
OLD: OES11
NEW: OES11 SP2 (assuming you want latest stuff).
Do all your data transfer/consolidations/etc
Then when you do the ID transfer, it will literally transfer the eDir databases (well copy is more correct) from OLD to NEW, you shut off OLD, I think it restarts NEW and renames/changes the servername and IP to what OLD had.
You can choose to install the NEW server with the .ISO separately (ie: Install SLES11 SP3, then after you're done, Add On the OES11 SP2 .ISO), or you may choose to use the integrated DVD and do it all at once, or use the 2 separate ISO and do them at once (but depending upon your installation method, you may not be able to do the 2 separate ISO).
I hope that helps.
I'm about halfway through editing my docs for OES11 SP1 (of course, SP2 is out now) for migrations from OES2 SP3, but the same setup steps basically apply. I think the only things that changed from NW To OES (ie: OES2 to OES11) are DHCP and iPrint migration procedures.
--Kevin

Does GW needs SP1 before upgrade to OES11.1

Currently GW 2012 on OES 2 (SLES 10 SP2)
Do I need to upgrade GW first to SP1 or OES2 to OES11 SP1
I hate the confusion with OES numbers for SP !!!
Seb

On 20.02.2013 03:36, deborahshields wrote:
>
> mrosen;2237005 Wrote:
>> On 19.12.2012 22:06, spgsitsupport wrote:
>>>
>>> Currently GW 2012 on OES 2 (SLES 10 SP2)
>>> Do I need to upgrade GW first to SP1 or OES2 to OES11 SP1
>>
>> Not necessarily first, but immediately afterwards. 2012 without SP1
>> doesn't work well on SLES11SP2 (which is the foundation of OES11SP1)
>>
>> CU,
>> --
>> Massimo Rosen
>> Novell Knowledge Partner
>> No emails please!
>> 'Untitled Document' (http://www.cfc-it.de)
>
> What about running GW2012 sp1 on OES11 that is fully patched, but not
> at sp1 ?
>
>
That should be fine, but do note that SLES11 without SP1 is or will soon
be unsupported, and receive no further patches.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
http://www.cfc-it.de

OES2.3 to OES11.1 on VMware

Similar Messages

Maybe you are looking for