HP Dataprotector 7.0 on OES11

is there somebody who made HP Dataprotector 7.0 work on a server running SLES11-SP1 + OES11 (64-bit) ?
After several days of trying and consulting HP Support, I could not make it work to see the nss volumes, only Linux files could be backed up.
The big problem is that the "hplogin" utility" is not installed, so no login through SMS possible (tsafs). During install, there were no options to choose, so what could I do wrong ? According to HP support I should read the manual more carefully.
HP claims HP Dataprotector works on OES11, but I have my doubts, maybe it works on OES2. It is however listed on: Partner Products | Novell Open Enterprise Server
Thanks,
Job Koopman

Originally Posted by magic31
My bad, as I realize having to include the '-t nssvol' is the old way of doing things as it also does not utilize TSA and metadata needs to be backed up separately.
The hplogin login should have auto installed during agent install AFAIK. If it's not there it would seem the agent install is not "seeing" this is OES instead of regular SLES.
Just checked the HP DP 7.00 installation guide, all it says about OES is this:
Originally Posted by HP DP 7.00 Install guide
Installing Linux clients
Linux client systems can be installed remotely using the Installation Server for UNIX, or locally by using the UNIX installation DVD-ROM (for HP-UX or Linux).
<snip>
Novell Open Enterprise Server (OES)
On Novell OES systems, Data Protector automatically installs the OES aware Disk Agent. However, there are some Novell OES specific aspects:
If you install Novell OES on 32-bit SUSE Linux Enterprise Server 9.0 (SLES), after installing a Data Protector Linux client on a system, you have to upgrade the Data Protector client as well.
Note that the new Novell OES aware Disk Agent will be remotely installed to the client system during the upgrade.
If you remove the Novell OES component from SLES, you have to reinstall the Data Protector client.

Similar Messages

Strange directory behaviour on NSS volume OES11 SP1

Hi All,
A couple of months ago we installed an OES11 SP1 server with an NSS volume (VOL1:) for all our installation files.
In the root of the VOL1: volume, we created a directory named _Install (yes, underscore)
In this directory we created a lot of subdirectories with installation files for several applications, to keep things short, let's say DIR-A, DIR-B, DIR-C DIR-D DIR-E etc.
So if we opened VOL1:, we just saw the _Install direcory in the root of VOL1:, and if we opened the _Install directory, we saw the DIR-A, DIR-B etc.
But today, we opened the VOL1:, saw, the _Install directory, but also the DIR-A, DIR-B, DIR-C etc. in the folowing manner:
_Install (normal)
_Install\DIR-A
_Install\DIR-B
_Install\DIR-C
etc.
If we doubleclick on one of the directories in the root of VOL1:, we actually open the directory below the _Install directory. It's just like we have a kind of symbolic links, or shortcut's to the real directories in our root.
Never seen this before.
Anybody a clue for this?
regards,
Mark

On 29/10/2013 14:46, MarkHofland wrote:
> A couple of months ago we installed an OES11 SP1 server with an NSS
> volume (VOL1:) for all our installation files.
> In the root of the VOL1: volume, we created a directory named _Install
> (yes, underscore)
> In this directory we created a lot of subdirectories with installation
> files for several applications, to keep things short, let's say DIR-A,
> DIR-B, DIR-C DIR-D DIR-E etc.
> So if we opened VOL1:, we just saw the _Install direcory in the root of
> VOL1:, and if we opened the _Install directory, we saw the DIR-A, DIR-B
> etc.
>
> But today, we opened the VOL1:, saw, the _Install directory, but also
> the DIR-A, DIR-B, DIR-C etc. in the folowing manner:
>
> _Install (normal)
>
> _Install\DIR-A
> _Install\DIR-B
> _Install\DIR-C
>
> etc.
>
> If we doubleclick on one of the directories in the root of VOL1:, we
> actually open the directory below the _Install directory. It's just like
> we have a kind of symbolic links, or shortcut's to the real directories
> in our root.
>
> Never seen this before.
>
> Anybody a clue for this?
Having seen your other replies, you're opening VOL1: in Windows Explorer?
What do you see if you do a DIR from a Command Prompt window?
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

NW66SP8 ClusterRessource to OES11 ClusterRessource - miggui duplicatesone folder and appends a 0 (zero) at the end of the folders name

Hi to all,
while migrating from NW to OES, one clustered volume with one (and
always the same) folder is duplicated with an trailing zero at the
folders name.
Source is
USER:\Abteilung\Edv\
Destination is
/media/nss/USER/Abteilung/EDV0/
while
/var/opt/novell/migration/user2/log/filesystem.success.log
shows the correct destination
Copying USER:Abteilung/EDV/... to /media/nss/USER/Abteilung/EDV/...
But in fact a new folder ../EDV0/ (in capitals) ist created, even if the
folder ../Edv/.. exists. This behaviour ist just with this folder, all
other volumes and folders worked fin.
One thing here is special:
I have *copied* the files to the destination volume because of the need
to have loaded tsafs.nlm, which nback will use for miggui, with the
option /nocluster for IBM TSM purposes. After that, I triggered a
regular consolidation as described above and later I plan to synch files
and trustees using miggui.
Any hints on that silly thing?
TIA
Tom

Originally Posted by mrosen
Tom,
On 04.03.2013 09:17, bwisupport wrote:
> But I think, your questions led me to the solution:
> The destination folder, copied with TotalCommander, was named 'Edv' (as
> TC shows the sources name too). Miggui sees a source called EDV, and at
> the destination a folder called 'Edv' and decides that these are two
> different folders. Because it is not possible having to folders with the
> same name (despite capitals) at the same place, a new Folder with
> trailing zero is created.
>
> I've deleted the 'EDV0', renamed the destination to EDV (cross-checked
> with Explorer and CLI) and restart a synch.
Hmmmm.... Something's very strange here anyways. Miggui *should* not
care about the case when the destination is NSS set to long namespace.
Either there's a bug in your version of miggui, or something else is
weird about that folder. It's also strange that TC and Windows Explorer
disagree on the capitalization. That again would lead me to the
assumption that something's broken originally with the source, like the
DOS and LONG namespaces on the source disagreeing somehow.
CU,
Massimo Rosen
Novell Knowledge Partner
No emails please!
Untitled Document
It sorta does. Apparently there's a bug in the miggui code that does this (although we only have it happen on OES2 SP3 to OES11 and it doesn't add a "0" at the end, it just stops processing after the main directory).
I've been waiting for NTS to file a bug report for over a month now.
anyway, Ramesh (the guy who kinda owns miggui) acknowledged there's a bug.
You can either:
1) use the migfiles command apparently instead of miggui
or
2) Rename the directory so that it matches, but with NSS you'll have to rename it twice. Like:
EdvX and then again to: EDV
Problem is with nbackup apparently that miggui uses.

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.

NCS on OES11 SP1 needs eDir 8.8.7 or later. With a replica?

We have 3 replicas running, one NW 6.5SP8 and two OES2SP3 (eDir 8.8 SP6). These 3 servers are 32bit.
I'm about to test NCS in the lab (we've not used it before) and see on page 50 (4.6.3) of "clus_admin_lx.pdf" that eDir 8.8.7 is required for managing cluster objects.
Is it okay if we keep our existing replicas and not yet add a replica to our OES11SP1 servers?
I interpret that requirement as saying that we need to manage cluster objects using iManager on one of our OES11 SP1 servers which run eDir 8.8.7. No replica required, correct?
Thanks,
Marc

In article <[email protected]>, Ohico wrote:
> I'm about to test NCS in the lab (we've not used it before) and see on
> page 50 (4.6.3) of "clus_admin_lx.pdf" that eDir 8.8.7 is required for
> managing cluster objects.
That would be for the specific version of NCS you are using that would
also have a say in which version of OES it runs on that should have that
version of eDir running on it.
> Is it okay if we keep our existing replicas and not yet add a replica
> to our OES11SP1 servers?
Well since your new OES11sp1 servers will be the only ones with the
newer eDir on them (unless you are upgrading eDir on the older boxes) it
would be a good thing to have a replica on at least one of these eDir
8.8.7 boxes in case there happen to be any 8.8.7 specific objects or
attributes in the newer eDir. I don't know of any, but that doesn't mean
the developers haven't come up with some.
> I interpret that requirement as saying that we need to manage cluster
> objects using iManager on one of our OES11 SP1 servers which run eDir
> 8.8.7. No replica required, correct?
Technically yes. But I would still like to have at least one 8.8.7
hosted replica of the partition(s) containing the new boxes.
Andy Konecny
Knowledge Partner (voluntary SysOp)
KonecnyConsulting.ca in Toronto
Andy's Profile: http://forums.novell.com/member.php?userid=75037

OES11 SP2 - Linux File System and NSS Pools & Volumes

Planning to install our first OES11 SP2 server into an existing tree - the
idea is to run this new OES11 server virtualized on VMware ESXi 5.5
The existing tree has two physical NW6.5SP8 servers running eDirectory
Version 8.7.3.10b (NDS Version 10554.64). One of the existing Netware
servers is used for DHCP/DNS, File Sharing from three NSS volumes and
Groupwise 7.0.4 whilst the second server is used for FTP services and
eDirectory redundancy. Ultimately the plan is to have two virtualized OES11
SP2 server with one for file sharing and the other for making the move from
GW7 to GW2012. And we're planning to stick with NSS for file sharing on the
new OES11 SP2 server.
I've come across a couple of posts for earlier versions of OES which
recommended not to put the Linux Native OS File System and NSS storage
pools/volumes on the same hard drive. Apparently the advice was a result of
needing to allow EVMS to manage the drive which could be problemmatic.
I've read the OES11 documentation which says that "The Enterprise Volume
Management System (EVMS) has been deprecated in SLES 11, and is also
deprecated in OES 11. Novell Linux Volume Manager (NLVM) replaces EVMS for
managing NetWare partitions under Novell Storage Services (NSS) pools."
So I'm wondering if there is still a compelling requirement to keep the
Linux Native File System and NSS pools/volumes on separate hard drives or
can they both now safely co-exist on the same drive without causing
headaches or gotchas for the future?
Neil

Hi Willem,
Many thanks for the further reply.
So we can just use the VMWare setup to "split" the one physical drive into
two virtual drives (one for the OS and the second for the pools).
And I've seen posts in other forums about the need for a decent battery
backed cache module for the P410i controller so I'll make sure we get one
(probably 512Mb module + battery).
Can I ask what is the advantage of configuring each VM's virtual disk to run
on it's own virtual SCSI adapter (by setting disk1 to scsi 0:0, disk2 to
scsi 1:0, and so on)?
Cheers,
Neil
>>> On 9/5/14 at 12:56, in message
<[email protected]>,
magic31<[email protected]> wrote:
> HI Niel,
>
> xyzl;2318555 Wrote: >
>> The new installation will run on a Proliant ML350 G6 with P410i>
> controller
>> so we can use the raid capability to create two different logical drives>
> as
>> suggested.
>
> As you will be using ESXi 5.5 as host OS, it's not needed to split
> thehost server storage into two logical drives... unless that's what
> youwant in perspective for "general performance" or redundancy reasons.
> Italso depends on the options that P410i controller has.
>
> On a side note, I'm not too familiar with the P410i controller... domake
> sure you have a decent battery backed cache module installed, asthat will
> greatly help with the disk performance bit.
> If the controller can handle it and the controller can handle it, go
> forraid 10 or raid 50. That might be too big a space penalty but will
> helpwith disk performance.
>
> Once you have your VMware server up and running, you can configure
> thetwo VM's with each two or more drives attached (on for the OS,
> thesecond or others for your pools).
> I usually create a virtual disk per pool+volume set (e.g. DATAPOOL
> &DATAVOLUME on one vm virtual disk, USERPOOL & USER volume on an other
> vmvirtual disk).
> With VMware you can than also configure each VM's virtual disk to run
> onit's own virtual SCSI adapter (bij setting disk1 to scsi 0:0, disk2
> toscsi 1:0, and so on).
>
>
> xyzl;2318555 Wrote: > Do you have any suggestions for the disk space that
> should be reserved> or
>> used for the Linux Native OS File System (/boot, /swap and LVM)?
>>
>
> Here's one thread that might be of interest (there are more
> throughoutthe SLES/OES
>
forums):https://forums.novell.com/showthread...rtitioning-%28
> moving-from-NW%29
>
> I still contently follow the method I choose for back in 2008, justwith
> a little bigger sizing which now is:
>
> On a virtual disk sized 39GB:
>
> primary partition 1: 500 MB /boot , fs type ext2
> primary partition 2: 12GB / (root), fs type ext3
> primary partition 3: 3 GB swap , type swap
>
> primary partition 4: LVM VG-SYSTEM (LVM partition type 8E), takes up
> therest of the disk **
> LVM volume (lv_var): 12 GB /var , fs type ext3
> LVM volume (lv_usr-install): 7GB /usr/install, fs type ext3
> * there's still a little space left in the LVM VG, in case var needs
> toquickly be enlarged
>
> One thing that's different in here vs what I used to do: I replaced
> the/tmp mountpoint with /usr/install
>
> In /usr/install, I place all relevant install files/IOS's
> andinstallation specifics (text files) for the server in question. Keeps
> itall in one neat place imo.
>
> Cheers,
> Willem-- Knowledge Partner (voluntary sysop)
> ---
> If you find a post helpful and are logged into the web interface,
> please show your appreciation and click on the star below it.
>
Thanks!---------------------------------------------------------------------
---magi
> c31's Profile: https://forums.novell.com/member.php?userid=2303View this
> thread: https://forums.novell.com/showthread.php?t=476852

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.

DHCP on OES11 Cluster

Hello,
I have some problems to get DHCP Service running in a Cluster Evironment (OES11 SP1, NSS Volume). The Ressource is up and running, but the DHCP Service wont load.
LDAPS session successfully enabled to 10.0.181.36:636
Error: Cannot find LDAP entry matching (&(objectClass=dhcpServer)(cn=DHCP_CLUSTER-DNSDHCP-SERVER))
Configuration file errors encountered -- exiting
The standard command rcnovell-dhcp start did work. So it looks like the rights or seomthing else is missing on the cluster volume /media/nssDHCP...
Maybe I am misunderstanding the doc as well. It states in the DHCP Linux Guide:
8.3.3. hot wo use a different user - it states that it would use the dhcpd user , but no such user was created. Do I need to create it manually?
Thanks for your help!
Regards Jrgen

Hi,
If I recall correctly from my setup, I had to create a user and LUM enable it, and match the UID to the local account.
See here: http://www.novell.com/documentation/...a/bbe81cc.html
Let us know how it goes.
Cheers,

OES11 install of NSM3.04 and Java

Slight problem encountered at a client. Upgraded the NSM engine server from
OES2SP3 to OES11: the 3.0.3 engine carried on working fine. And I could also
upgrade to 3.04 with no problem by adding the CD repository.
However, I go to install a 2nd event agent on a *freshly* installed OES11
server, and yast2 software management complains:
Nothing provides java-1_5_0-ibm needed by
novell-storagemanager-event-3.0.4-10.x86_64
This is fair: SLES11.1/OES11 repos only have java 1.6, but the upgraded
server retained Java 1.5 from OES2
I run "rpm -ivh" against the module instead to install the event server, and
I get no dependency issue. And hey presto the event server works

On 8/3/2012 5:30 AM, Martin Farrer wrote:
> Slight problem encountered at a client. Upgraded the NSM engine server
> from OES2SP3 to OES11: the 3.0.3 engine carried on working fine. And I
> could also upgrade to 3.04 with no problem by adding the CD repository.
>
> However, I go to install a 2nd event agent on a *freshly* installed
> OES11 server, and yast2 software management complains:
> Nothing provides java-1_5_0-ibm needed by
> novell-storagemanager-event-3.0.4-10.x86_64
> This is fair: SLES11.1/OES11 repos only have java 1.6, but the upgraded
> server retained Java 1.5 from OES2
>
> I run "rpm -ivh" against the module instead to install the event server,
> and I get no dependency issue. And hey presto the event server works
>
>
Martin,
There are actually two repositories on our NSM 3.0.4 ISO. One is named
SLES10 and one is named SLES11. If you follow the instructions in the
HTML pages on the ISO you'll mount the correct one just fine. However,
if you let SLES11 attempt to automatically mount the ISO image and find
the repository, it picks the first ISO on the image. Since "SLES10"
comes first alphanumerically, before "SLES11", you're actually mounting
the SLES10 repository with that ISO image.
Long story short - remove that repository and follow the directions on
the ISO image, and you should have no trouble.
-- NFMS Support Team
- NFMS Support Team

Tomcat running high utilization on OES11 SP2

I have Groupwise 2014 with webaccess and calendar publishing host installed on the same OES 11 SP2 in virtual environment. Tomcat is slowly eating up available CPUs until the system becomes unstable. Rcnovell-tomcat6 restart will temporarily clear the problem. The problem is described in TID 7010072 however, the document specifically says that the fix is not for OES11. Does anyone know how to address this on OES11?

Originally Posted by smflood
On 08/07/2014 20:46, bobodajdaj wrote:
> I have Groupwise 2014 with webaccess and calendar publishing host
> installed on the same OES 11 SP2 in virtual environment. Tomcat is
> slowly eating up available CPUs until the system becomes unstable.
> Rcnovell-tomcat6 restart will temporarily clear the problem. The problem
> is described in TID 7010072 however, the document specifically says that
> the fix is not for OES11. Does anyone know how to address this on OES11?
Firstly I'm not aware of an equivalent TID specific to OES11 so I'll ask
my Novell contacts.
OES11 uses novell-tomcat6 rather than tomcat6 as used with SLES11 with
configuration file at /etc/opt/novell/tomcat6/conf/novell-tomcat6.conf
so in the meantime perhaps make the same change as noted in TID 7010072
for SLES11 to the OES11 file.
Note there is more than one line (re)defining CATALINA_OPTS so I'd be
tempted to add the following line below the last CATALINA_OPTS line:
CATALINA_OPTS="$CATALINA_OPTS -Xthr:minimizeUserCPU -Xms800m -Xmx900m"
Restart the OES11 tomcat process via "rcnovell-tomcat6 restart".
HTH.
Simon
Novell Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
We are experiencing the same issue on our OES GroupWise 2014 server. Restarting novell-tomcat6 fixes temporarily, but always returns. Anyone find anything further with this? Just downloaded (1/12/15) and installed latest available hotpatches for GW2014 and SLES/OES, but did not resolve issue.

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

LVM and NSS in OES11

I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
Chris

Originally Posted by cmosentine
I am building out a replacement server which will be the target for a server migration. The server will host an NSS volume. In the past I have always created an array-level logical drive for my NSS partiton/volume. Rather than doing this, I would rather just have one logical drive and partition the space using LVM (except for /boot and swap). Once I create the LVM and add /, /home, /var, /tmp to it, I will have a lot of extra space which I want to use for the NSS volume.
So, is it possible to use the unused space in LVM for NSS? Or should I stick which a separate logical partition for NSS?
Chris
With OES11 it's possible and quite easy to use the left free space on the system disk for NSS.
It also does not have the potential for havoc as was the case with OES2 (as with OES2 this was also possible, it just meant using EVMS on the system disk device, which could lead to issues booting after patching of updating due to needed missing kernel modules for EVMS within initrd).
Still, even with it being possible and supported to do so, if you can house the OS bits and data (be it on NSS and other filesystems) on different disk devices.. that would always be what I'd opt for. It makes certain maintenance/recovery and update tasks easier/more flexible/reliable as OS and data partitions are not within one and the same "container".
Cheers,
Willem

OES11 - NDSD 100% CPU

Running in a mixed Netware/OES tree and have set-up a server specifically to take over the file services from Netware. I have a 1TB NSS volume, the system is running on vmware esxi 5 with the tools installed. I've moved one persons home directory onto the new volume, but every so often when accessing the volume the NDSD process goes to 100% and never drops back down until either NDSD is restarted or the server is restarted. I've been through a lot of the tuning and other suggestions from the forum, without any success, the system is fully patched OES11.
Any suggestions on what I can do next.

A lot of OES services (like LUM) access eDirectory via LDAP. You
mentioned "a lot of the tuning and other suggestions" which you have
tried; please specify exactly what was done so we do not duplicate those
suggestions again. As you've done these I assume you didn't see anything
in ndstrace watching LDAP traffic, but confirmation would be nice.
Watching the ndstrace output with the RECM output may also be interesting
in case your system is accessing something that's not indexed.
Good luck.

OES11 miggui fails on cross-tree migration

Maybe Ramesh will see this:
Doing a cross-tree migration, and choosing to create the trustee users on the destination tree.
This is what the file system log shows for failures:
(oh, the SOURCE server is OES2 SP3)
Code:
2012-01-27 11:22:34,197 INFO - FILESYSTEM:Information:****************Migrating files and/or trustees****************
2012-01-27 11:22:34,197 INFO - FILESYSTEM:mls:Scanning APPS1:Documentation for rights, trustees and quotas using mls
2012-01-27 11:22:34,199 INFO - FILESYSTEM:mls:Executing command: /opt/novell/migration/sbin/mls --source-server 10.10.1.11 --source-path "APPS1:Documentation" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.session" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:33,097 INFO - FILESYSTEM:mls:Successfully scanned trustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Mapping users and groups from APPS1:Documentation to /media/nss/APPS1/Documentation using maptrustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Executing command: /opt/novell/migration/sbin/maptrustees --source-server 10.10.1.11 --destination-ldap-container "o=abc" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.yaml" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:39,153 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,563 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,569 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,553 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,557 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:54,063 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:56,095 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:03,139 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,827 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,832 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,583 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,744 INFO - FILESYSTEM:maptrustees:Successfully mapped trustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Creating users and groups existing on APPS1:Documentation to /media/nss/APPS1/Documentation using migtrustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Executing command: /opt/novell/migration/sbin/migtrustees --destination-server 10.10.1.12 --verbose --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_migtrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.yaml" --progress --progress-interval 1 --destination-unsecure-ldap --destination-ldap-port 389
2012-01-27 11:24:10,035 FATAL - FILESYSTEM:migtrustees:Fatal: Caught exception: syntax error on line 366, col 14: ` givenName: 'Brenda''
2012-01-27 11:24:10,107 ERROR - FILESYSTEM:migtrustees:migtrustees command failed!
2012-01-27 11:24:10,108 INFO - FILESYSTEM:Information:****************End****************
2012-01-27 11:34:05,713 ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby /opt/novell/migration/sbin/volmount.rb -s 10.10.1.11 -a "cn=admin,o=dec" -c Not Applicable -f "/var/opt/novell/migration/OESSP1-APPS1/fs/mnt/source" -m -t OES20
So I'm not sure if it's the logintime stuff that's making it fail (I see a TID with no update) or the odd part about having a problem with a given name

$(UThe loginallowedtimemap and networkaddressrestriction attributes are stored as double byte encryption encoded strings, which are not read by the current maptrustees script.
For OES11 we have documented the workaround in the Trouble Shoot section 16.7.3 @ http://www.novell.com/documentation/....html#bookinfo
-Ramesh
>>> kjhurni<[email protected]> 01/27/2012 10:26 PM >>>
Maybe Ramesh will see this:
Doing a cross-tree migration, and choosing to create the trustee users
on the destination tree.
This is what the file system log shows for failures:
(oh, the SOURCE server is OES2 SP3)
Code:
2012-01-27 11:22:34,197 INFO - FILESYSTEM:Information:****************Migrating files and/or trustees****************
2012-01-27 11:22:34,197 INFO - FILESYSTEM:mls:Scanning APPS1ocumentation for rights, trustees and quotas using mls
2012-01-27 11:22:34,199 INFO - FILESYSTEM:mls:Executing command: /opt/novell/migration/sbin/mls --source-server 10.10.1.11 --source-path "APPS1ocumentation" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.session" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:33,097 INFO - FILESYSTEM:mls:Successfully scanned trustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Mapping users and groups from APPS1ocumentation to /media/nss/APPS1/Documentation using maptrustees
2012-01-27 11:23:33,098 INFO - FILESYSTEM:maptrustees:Executing command: /opt/novell/migration/sbin/maptrustees --source-server 10.10.1.11 --destination-ldap-container "o=abc" --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_mls.yaml" --progress --progress-interval 1 --source-unsecure-ldap --source-ldap-port 389
2012-01-27 11:23:39,153 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,563 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:45,569 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,553 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:50,557 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:54,063 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:23:56,095 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:03,139 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,827 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:07,832 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,583 ERROR - FILESYSTEM:maptrustees:UTF-8 conversion failed for: loginAllowedTimeMap: '_decoded_'
2012-01-27 11:24:09,744 INFO - FILESYSTEM:maptrustees:Successfully mapped trustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Creating users and groups existing on APPS1ocumentation to /media/nss/APPS1/Documentation using migtrustees
2012-01-27 11:24:09,744 INFO - FILESYSTEM:migtrustees:Executing command: /opt/novell/migration/sbin/migtrustees --destination-server 10.10.1.12 --verbose --session-file "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_migtrustees.session" "/var/opt/novell/migration/OESSP1-APPS1/fs/APPS1_Documentation_maptrustees.yaml" --progress --progress-interval 1 --destination-unsecure-ldap --destination-ldap-port 389
2012-01-27 11:24:10,035 FATAL - FILESYSTEM:migtrustees:Fatal: Caught exception: syntax error on line 366, col 14: ` givenName: 'Brenda''
2012-01-27 11:24:10,107 ERROR - FILESYSTEM:migtrustees:migtrustees command failed!
2012-01-27 11:24:10,108 INFO - FILESYSTEM:Information:****************End******** ********
2012-01-27 11:34:05,713 ERROR - FILESYSTEM:volmount.rb:Command to mount source: ruby /opt/novell/migration/sbin/volmount.rb -s 10.10.1.11 -a "cn=admin,o=dec" -c Not Applicable -f "/var/opt/novell/migration/OESSP1-APPS1/fs/mnt/source" -m -t OES20
So I'm not sure if it's the logintime stuff that's making it fail (I
see a TID with no update) or the odd part about having a problem with a
given name
The opinions expressed are my own.
Check out my OES2 Guides:
Installing OES2 SP2:
http://www.novell.com/communities/no...allation-guide
Upgrading to OES2 with ID Transfer:
http://www.novell.com/communities/no...r-id-scenarios
GroupWise Migration with OES2 ID Transfer:
http://www.novell.com/communities/no...p2-transfer-id
kjhurni's Profile: http://forums.novell.com/member.php?userid=734
View this thread: http://forums.novell.com/showthread.php?t=451439

HP Dataprotector 7.0 on OES11

Similar Messages

Maybe you are looking for