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

Similar Messages

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.

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

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

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

What is the difference between upgradation and migration.

Hi Guru's
what is the difference between upgradation and migration.
actuallly i involved in upgradation project, here my role is
1. first i check the query's in 3.5 save the query and transport the query. and check the query in bex analyzer also.
2. go to BI .7 find the query;s ,give the query name and save the query ,
3. once save the query, again will come to 3.5 open the query , it will not open. this is my job here,
come to 7.0 check the query in analyzer also.
i am having littile bit confusion, how it will comes query in 7.0, why are u saving the query's in 3.5 and 7.0
query's already available in 7.0 why are u doing this work?
can i know the upgrades those objects, is it neccessary, if necessary how can i upgrade.
infoobje , transferrules, transferstructure ,infosoure, datasoure,updaterules, ods, cubes.
Points will be Assingned ,
Thanks & Regards
prabhavathi

Hi,
I was talking in a general sense not on a query level.
If your taling about migration in that level meaning as a part of larger upgradation (in your case 3.x to 7) there may be many places where you need to do this kind of activities.
Fr eg migration into new data flow, Migration of Web templates from BW 3.x to Netweaver 2004s, etc
Hope this helps.
Thanks,
JituK

How can I determine what sites are being referenced within Central Admin Upgrade and Migration Manage Databases Upgrade Status?

When I go to Central Admin > Upgrade and Migration > Manage Databases Upgrade Status, I have 2 content databases which have the status:
Database is up to date, but some sites are not completely upgraded.
How can I determine which sites are not completely upgraded?

Manage Databases Upgrade Status will provide you all active and offline DB details, you can get same result
using below PowerShell cmdlet.
Get-SPDatabase and Get-SPContentDatabase will provide all active database/Content DB in Farm which include Service application db, central admin DB.
Get-SPDatabase | Format-Table Name, ID
Coming back to your question, if you find that there are some site are not completely upgraded then run below command and understand the cause if issue on specific DB.
Test-SPContentDatabase WSS_ContentDB_Name
If you find any missing file issue in DB then resolve these issue to upgrade content database.
(verify all customizations referenced within the content database are also installed in the web application. This cmdlet can be issued
against a content database currently attached to the farm, or a content database that is not connected to the farm )
Use the Upgrade-SPContentDatabase cmdlet
to resume a failed database upgrade or begin a build-to-build database upgrade against a SharePoint content database
Upgrade-SPContentDatabase WSS_Content
reference:
http://technet.microsoft.com/en-us/library/ff607813(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ff607941(v=office.15).aspx
If my contribution helps you, please click Mark As Answer on that post and
Vote as Helpful
Thanks, ShankarSingh(MCP)

What are the consultant roles in Upgradation or migration project

Hello ,
Would you please any dody help me to provide the role & responsibilities of consultant in SAP upgradation or migration project.Thanks.
Regards,
Sampally

Dear Sampally,
SAP defined a roadmap for upgrade.
1) Project Preparation
Analyze the actual situation
Define the objectives
Create the project plan
Carry out organizational preparation for example identify the project team
2)Upgrade Blueprint
The system and components affected
The mapped business processes
The requirements regarding business data
3)Upgrade Realization -- In this phase the solution described in the design phase is implemented in a test environment. This creates a pilot system landscape, in which the processes and all their interfaces can be mapped individually and tested on the functional basis.
4)Final Preparation for Cutover -- Testing, Training, Minimizing upgrade risks, Detailed upgrade planning
5)Production Cutover and Support
The production solution upgrade
Startup of the solutions in the new release
Post processing activities
Solving typical problems during the initial operation phase.
SAP expects at least 2 to 3 months for Upgrade and that again depends on project scope and complexity and various other factors.
STEPS IN TECHNICAL UPGRADE
Basis Team will do the prepare activities. (UNIX, BASIS, DBA).
Developer need to run the Transaction SPDD which provides the details of SAP Standard Dictionary objects that have been modified by the client. Users need to take a decision to keep the changes or revert back to the SAP Standard Structure. More often decision is to keep the change. This is mandatory activity in upgrade and avoids data loses in new system.
After completing SPDD transaction, we need to run SPAU Transaction to get the list of Standard SAP programs that have been modified. This activity can be done in phases even after the upgrade. Generally this will be done in same go so that your testing results are consistent and have more confident in upgrade.
Run SPUMG Transaction for Unicode Conversion in non-Unicode system. SPUM4 in 4.6c.
Then we need to move Z/Y Objects. Need to do Extended programming check, SQL trace, Unit testing, Integration testing, Final testing, Regression Testing, Acceptance Testing etc.,
The main Category of Objects that needs to be Upgraded is
Includes
Function Groups / Function Modules
Programs / Reports
OSS Notes
SAP Repository Objects
SAP Data Dictionary Objects
Domains, Data Elements
Tables, Structures and Views
Module Pools, Sub Routine pools
BDC Programs
Print Programs
SAP Scripts, Screens
User Exits
Also refer to the links -
http://service.sap.com
http://solutionbrowser.erp.sap.fmpmedia.com/
http://help.sap.com/saphelp_nw2004s/helpdata/en/60/d6ba7bceda11d1953a0000e82de14a/content.htm
http://www.id.unizh.ch/dl/sw/sap/upgrade/Master_Guide_Enh_Package_2005_1.pdf
Hope this helps you. Please let me know in case of any specific queries.
Regards,
Rakesh

Diff between Upgrade and migration

hi All,
Can you please explain as to what is the difference between upgradation and migration. Also can you please explain as to when would a company go for a upgrade and when it would go for migration.
My another question is, What does it mean when a company says that they are going to perform a new installation of BI 7.0. Does that mean that they do not have any previous versions of BW
Thanks

hi,
Upgrade - the user might be already using any of the BW version and he wants the new version thats upgradation
How to upgrade to BI7.0
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/2e8e5288-0b01-0010-2ea8-bcd4df5084a7
Prerequisites for BI7.0
http://help.sap.com/bp_biv170/index.htm
chk the above links for upgrade related queries.
Migration - working in new version with older version dataflow and whenever required the data flow is changed to newer version.
New Installation- the user might be using someother datawarehouse tool and he wants the new SAP data ware house(BI) that new installation.
Ramesh

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.

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/

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

Upgrade and migration from Netware to Linux best practice

Hi folks,
We've been running NSM 2.5 for a few years on Netware and have been very satisfied with the product and performance. We are planning to migrating to SLES11 with OES11 very soon to finally move away from Netware and I have some issues I can't seem to find answers to. Of course I want to use NSM to move my home directories from my Netware to my SLES so I want this working well when we migrate.
I've searched but not found a good resource to show how to move the NSM engine from a Netware server to a Linux server with best practices. Anyone have experience with this and any gottchas?
The other question is of course is to upgrade NSM to a new version before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want to move to the latest version. Upgrade procedure and best practices would be handy.
The last of course is NSM compatible with SLES/OES11? I presume it is and certainly hope so because we want to move all of our users to SLES11 NSS.

On 5/9/2012 11:06 AM, jlauzon wrote:
>
> Hi folks,
> We've been running NSM 2.5 for a few years on Netware and have been
> very satisfied with the product and performance. We are planning to
> migrating to SLES11 with OES11 very soon to finally move away from
> Netware and I have some issues I can't seem to find answers to. Of
> course I want to use NSM to move my home directories from my Netware to
> my SLES so I want this working well when we migrate.
> I've searched but not found a good resource to show how to move the NSM
> engine from a Netware server to a Linux server with best practices.
> Anyone have experience with this and any gottchas?
The NSM 3.0.x Engine setup process actually handles the migration from
NSM 2.5 fairly easily. Our 3.0 Installation Guide (available at
http://www.novell.com/documentation/storagemanager3 ) includes all the
information you should need regarding migration, including the
suggestions I'll list here.
You'll want to leave NSM 2.5 running during the migration so that the
NSM 3.0 setup wizard can connect to that Engine and import its policies
and pending events. You'll also want to have as few pending events as
possible in NSM 2.5 -- deferred deletes are fine, but all pending events
will slow down the migration process, since they'll have to be
transferred over.
> The other question is of course is to upgrade NSM to a new version
> before or after the move to Linux/OES11? We are at Ver 2.5.0.43 and want
> to move to the latest version. Upgrade procedure and best practices
> would be handy.
Again, this information is available in the 3.0 Installation Guide. To
migrate from 2.5 to 3.0.x, you'll have to have at least one OES11 server
in your tree to install it on; but you'll also have to leave the NSM 2.5
Engine running on its Netware host long enough to migrate from it.
> The last of course is NSM compatible with SLES/OES11? I presume it is
> and certainly hope so because we want to move all of our users to SLES11
> NSS.
We are about to release version 3.0.4 of NSM, which provides full
support for OES11 on SLES11. The NFMS Support Team can also provide you
with builds of NSM 3.0.3 which support OES11; if you need those for
early testing, please send an email to storagemanager[at]novell[dot]com.
Hope this helps!
- NFMS Support Team

Items greyed out after upgrading and migrating to Sharepoint 2013 - Open and Check Out + Manage Document Option

Hi there,
Following a migration to SharePoint 2013, the follow options have been disabled (Open and Check out + Manage) (see below). These are critically important functions and make it very hard to make SharePoint a useable interface. Any guidance on how to resolve
these issues is greatly appreciated. This is not a branded website, and there has been no changes made to the standard interface.
Kind regards
Jarrad Koppen

I'm not sure what the easiest way is either. First, I would try to create a new site collection with a new library and see if you get the same behavior. If not, then its something in the upgrade process. If it does that also would point
to something being wrong in the way that javascript is being executed.
If it is happening everywhere I suspect you'll have to start tracing javascript using something like IE developer's toolbar to see why the status on those buttons isn't changing when you select a document. I'm not sure what else to suggest.
Paul Stork SharePoint Server MVP
Principal Architect: Blue Chip Consulting Group
Blog: http://dontpapanic.com/blog
Twitter: Follow @pstork
Please remember to mark your question as "answered" if this solves your problem.

What's the best way to upgrade and migrate to SSD and HDD

Was hoping to get some advice on my pendIng upgrade to a new HD and SSD in my mid-2010 13" MacBook Pro. I'm very confident in my installation abilities but I'm a novice when it comes to moving software and programs.
Here's the set-up ill be working with:
Mid-2010 13" MacBook pro (1.7)
New 750gb 7200 rpm HDD in original bay
New 128gb SSD in old optical drive bay
What I want to do is run OS X (lion for now) and applications off of the SSD while keeping 'data hogs' on the 750gb. I've read probably 10 different ways to do this from cloning HDD to SSD while keeping the user folder on the HDD, or clean install of lion on the SSD then using migration assistant to pull the apps over.
I want to make sure I'm moving the right stuff over to the SSD so that I can take full advantage of it. I also dont want excess crap on the 750 especially since I'll have a bootable copy on my old drive.
What should I put on the SSD? How should I get it there? If I do a clean install of lion on the SSD do I just migrate the applications using the migration assistant from my original HDD and then migrate whatever's left onto the new HDD?
So many questions.
Any help would be greatly appreciated. The drives and enclosures are showing up tomorrow and I'm looking forward to getting them up and running.
Thanks

When you upgrade it will use your existing user data including bookmarks, passwords, cookies and browsing history.
I have been using Firefox Sync since it was in an early development stage about 2 years ago. I have gone through a few upgrades to Firefox since then with no problems during the upgrades. I recommend going to Firefox 4 first because Firefox Sync is built into it so there will be no need to install the add-on.
If required you can downgrade to Firefox 3.6.16

OES2 to OES11 (upgrade or migrate?)

Similar Messages

Maybe you are looking for