New to AD NSM

I am new to NSM for AD. I am migrating from Edir. After I moved the user volumes from Edir to AD the volumes started changing from the username to My Documents. We have found the microsoft fix (//server/volume/%username%/my documents). The current Edir home directory is treating the //server/volume/home directory as the my documents and not renaming it. So is there anyway to use NSM to get the current data in the home directory into a my documents folder under the home directory.
I know that I am rambling a bit but any help is appreciated.

Mvarazlic,
The migration wizard has the ability to migrate the storage into a sub
folder of the users new AD home directory. See section 8.5 of the Admin
Guide for more details. Specifically look at the target sub folder field
information.
http://www.novell.com/documentation/...r_ad_admin.pdf
thanks,
NSM Development
On 2/25/2011 2:36 PM, Mvarazlic wrote:
>
> I am new to NSM for AD. I am migrating from Edir. After I moved the
> user volumes from Edir to AD the volumes started changing from the
> username to My Documents. We have found the microsoft fix
> (//server/volume/%username%/my documents). The current Edir home
> directory is treating the //server/volume/home directory as the my
> documents and not renaming it. So is there anyway to use NSM to get the
> current data in the home directory into a my documents folder under the
> home directory.
>
> I know that I am rambling a bit but any help is appreciated.
>
>

Similar Messages

New Install of NSM 3.1.1.1 error creating NSMProxy and group

Unable to create NSMProxy or NSMProxyRights. Error is: The specified domain does not exist, or no domain controllers are available for the domain. This is a test environment. NSM server is a member server of the TEST domain. It doesn't matter if I run the admin tool on the member server or on the domain controller, same error is generated.

lressel,
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://www.novell.com/support 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 Forums Team
http://forums.novell.com

NSM 3.1 Agent Heartbeat

Hello,
i'm testing a new install of NSM 3.1 on a new Windows 2008 R2 installation to see if we can migrate from 3.0.3 to 3.1
But as soon as i Authorize the (local) agent i get a "Warning: A heartbeat has not been received for more then 5 minutes."
i have put login on the agent en engine to debug but the only usefull info is from the agent log:
Successfully performed a heartbeat communication
Received a "ACK" HB response
Received an "Authorized" HB response, nStatus = 0.
there is noting in the engine log.
Hope you can help me,
Niels van de Haar

On 4/24/2013 6:26 AM, nvdhaar wrote:
>
> Hello,
>
> i'm testing a new install of NSM 3.1 on a new Windows 2008 R2
> installation to see if we can migrate from 3.0.3 to 3.1
>
> But as soon as i Authorize the (local) agent i get a "Warning: A
> heartbeat has not been received for more then 5 minutes."
>
> i have put login on the agent en engine to debug but the only usefull
> info is from the agent log:
>
> Successfully performed a heartbeat communication
> Received a "ACK" HB response
> Received an "Authorized" HB response, nStatus = 0.
>
>
> there is noting in the engine log.
>
> Hope you can help me,
>
> Niels van de Haar
>
>
Niels,
This is a cosmetic UI issue we recently discovered in NSM 3.1 (and in
Novell File Reporter 2.0.0 as well.) The Agent is actually heartbeating
just fine and will work without issue. However, when the Engine and
Agent are in timezones between UTC+1 and UTC+14, the UI incorrectly
calculates the time between heartbeats and displays this error.
A fix for this problem has already been implemented for forthcoming
releases of Storage Manager and File Reporter. Our apologies for the
confusion it creates!
- NFMS Support Team

Schema extension problem

Hi,
I have installed a new domain with NSM. The 'NSM Schema Utility' is showing:
Screenshot.png
But in the NSM Admin I have the message: "Schema Not Extended"
Can I verify with for ex. the mmc 'Active Directory Schema' if the all required extensions are done? Or is it only a problem with the NSMA which doesn't detect correctly the extension?
Best regards,
Christian

Christian,
What's the domain and forest functional level in this domain?
-- NFMS Support Team
On 3/7/2014 5:36 AM, goebelch wrote:
>
> Hi,
> I have installed a new domain with NSM. The 'NSM Schema Utility' is
> showing:
>
> 5042
>
> But in the NSM Admin I have the message: "Schema Not Extended"
>
> Can I verify with for ex. the mmc 'Active Directory Schema' if the all
> required extensions are done? Or is it only a problem with the NSMA
> which doesn't detect correctly the extension?
>
> Best regards,
>
> Christian
>
>
> +----------------------------------------------------------------------+
> |Filename: Screenshot.png |
> |Download: https://forums.novell.com/attachment...achmentid=5042 |
> +----------------------------------------------------------------------+
>

NSM 3.1.1, New users not managed.

When new users are added to a context with a User Home Folder policy the new users are unmanaged.
This is a new 3.1.1.15 install. If I right-click the user and select User Actions -> Manage it will create the storage and set the rights per the policy.
What am I missing?
Thanks,
David.

So it was a simple over-site ( read as a dumb mistake ) the Event Servers and Agent Servers on the Configure tab were not Authorized...
Thanks for your help,
David.
Originally Posted by dbenjamin
# ls /var/opt/novell/storagemanager/event/data/
.cacheindex
I then stop the engine.
Create a new user using iManager.
# ls /var/opt/novell/storagemanager/event/data/
.cacheindex event.dat
I start the engine.
Wait a little bit, a minute or less.
# ls /var/opt/novell/storagemanager/event/data/
.cacheindex
Log into Novell Storage Manager Admin 3.1.1.15
Select Storage Management
Select the container that has the new user
Click the check by Users to see the new user
Right click the user and select Object Properties
Properties tab:
-FDN CN=testuser,OU=Students,O=TreeName
-GUID {big long guid here}
-Type 1
-Create Time Friday, August 8, 2014 8:19:54 AM
Effective Policies tab:
-Effective Policy Students
-Policy Type User
-Managed Path Type Home Folder
-Managed Path <blank>
Associated Polices tab:
-Policy Students
-Policy Type User
-Managed Path Type Home Folder
Transactions tab:
-Eligible <blank>
-Deferred <blank>
-Active Error, Unable to service the request at this time.
History tab:
-FDN History, Name; Error Processing Results - 1792: The requested record could not be located in the Global Statistics Reporting database. Date / Time; Not available
I run the Consistency Check and the Management Status is Not Managed.

NSM Engine Start and Stops

I have installed NSM 3.0.4.4 on a SLES 11 SP1, OES 11 SP1. After doing battle with certificates and other issues, I had finally got it up and running. The problem comes when I attempt to complete the migration process from the previous Netware server. The NSM engine stops running and shows its running state as unused. Restarting the engine via nsmengine-config starts the engine, but it inevitably stops. I have been able to get it to start and continue to run by renaming the /var/opt/novell/storagemanager/engine/data folder and creating an empty one, which triggers a new setup wizard.
I resigned myself to recreating the policies, so I ran through the wizard and did not import the old policies. I left the GSR Collecter running overnight and found that the engine had once again stop and I am unable to get it to stay up. I have included the last lines of the nsmengined.log. I am at my wits end.
Thank You,
Kenneth
01 2012-08-07 08:00:02 -14400 3 0001 30152 7ff78be7c710 ML: Called LoadStorageResourcesFromCache(), Result = 45.
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called LoadStorageResourcesFromDS(false), bResult = 1.
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called LoadAgentManager(), Result = 0.
01 2012-08-07 08:00:02 -14400 5 0006 30152 7ff78be7c710 AM: Starting Delegation Subsystem...
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called AgentManager().ResumeDelegating(), Result = 0.
01 2012-08-07 08:00:02 -14400 5 8008 30152 7ff7896a2710 CCStorageResources::WorkerThreadFunction() - Rebuild is in initial state.
01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff78be7c710 Sched: Attempted initial Database initialization, Result = 0.
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called LoadScheduler(), Result = 0.
01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff78be7c710 Sched: Starting Scheduler Subsystem...
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called Scheduler().ResumeSchedules(), Result = 0.
01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called LoadEventMonitorListFromCache(), Result = 0.
01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 ML: Loading saved SR state information...
01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 GL: Failed to load the SR state information, nResult = 53.
01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 ML: Loading SR proxy information...
01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 GL: Attempted to load the SR proxy information, nResult = 0.
01 2012-08-07 08:00:02 -14400 5 0004 30152 7ff7763b3710 PC: No policies currently available
01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff7773b5710 Sched: Loaded 0 tasks scheduled for the next 57598 seconds, Result = 0.
01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff7773b5710 Sched, ST: No Scheduled tasks set to execute today. Scheduled Tasks for tomorrow will be loaded in 57598 seconds.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Policy Cache Rebuild complete.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding Managed Path Cache...
01 2012-08-07 08:00:03 -14400 5 0004 30152 7ff78be7c710 MPC: Loading 0 path entries into cache...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Managed Path Cache Rebuild complete.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding Event Cache...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Event Cache Rebuild complete.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding Event Processor Data...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Event Processor Data Rebuild complete.
01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Base schema appears to be properly extended.
01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Action Object schema appears to be extended.
01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Legacy Collaborative Homedirectory attribute cccFSFactoryGroupHomedir is available.
01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Legacy Quota Manager attribute cccFSFactoryHomeDirectoryQuota is available.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting the Task Manager subsystem...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Completed starting the Task Manager subsystem, bResult = 1.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting the HTTPx Server subsystem...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Completed starting the HTTPx Server subsystem, bResult = 1.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting Incoming Event Parser subsystem...
01 2012-08-07 08:00:03 -14400 2 0001 30152 7ff78be7c710 ML: Completed initialization. Engine is now running.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 WD: Engine mainline thread is entering the Watch Dog function...
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 WD: Engine is running...
01 2012-08-07 08:00:03 -14400 3 0001 30152 7ff78be7c710 WD: Detected that the Incoming Event Parser has terminated.
01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting Incoming Event Parser subsystem...
01 2012-08-07 08:00:03 -14400 5 8006 30152 7ff75fb86710 TM: TaskManagerThread() - Thread has started.

On 8/7/2012 8:56 AM, krite wrote:
>
> I have installed NSM 3.0.4.4 on a SLES 11 SP1, OES 11 SP1. After doing
> battle with certificates and other issues, I had finally got it up and
> running. The problem comes when I attempt to complete the migration
> process from the previous Netware server. The NSM engine stops running
> and shows its running state as unused. Restarting the engine via
> nsmengine-config starts the engine, but it inevitably stops. I have
> been able to get it to start and continue to run by renaming the
> /var/opt/novell/storagemanager/engine/data folder and creating an empty
> one, which triggers a new setup wizard.
>
> I resigned myself to recreating the policies, so I ran through the
> wizard and did not import the old policies. I left the GSR Collecter
> running overnight and found that the engine had once again stop and I am
> unable to get it to stay up. I have included the last lines of the
> nsmengined.log. I am at my wits end.
>
> Thank You,
> Kenneth
>
> 01 2012-08-07 08:00:02 -14400 3 0001 30152 7ff78be7c710 ML: Called
> LoadStorageResourcesFromCache(), Result = 45.
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> LoadStorageResourcesFromDS(false), bResult = 1.
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> LoadAgentManager(), Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0006 30152 7ff78be7c710 AM: Starting
> Delegation Subsystem...
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> AgentManager().ResumeDelegating(), Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 8008 30152 7ff7896a2710
> CCStorageResources::WorkerThreadFunction() - Rebuild is in initial
> state.
> 01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff78be7c710 Sched:
> Attempted initial Database initialization, Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> LoadScheduler(), Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff78be7c710 Sched: Starting
> Scheduler Subsystem...
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> Scheduler().ResumeSchedules(), Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0001 30152 7ff78be7c710 ML: Called
> LoadEventMonitorListFromCache(), Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 ML: Loading
> saved SR state information...
> 01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 GL: Failed to
> load the SR state information, nResult = 53.
> 01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 ML: Loading SR
> proxy information...
> 01 2012-08-07 08:00:02 -14400 5 0002 30152 7ff78be7c710 GL: Attempted
> to load the SR proxy information, nResult = 0.
> 01 2012-08-07 08:00:02 -14400 5 0004 30152 7ff7763b3710 PC: No
> policies currently available
> 01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff7773b5710 Sched: Loaded 0
> tasks scheduled for the next 57598 seconds, Result = 0.
> 01 2012-08-07 08:00:02 -14400 5 0009 30152 7ff7773b5710 Sched, ST: No
> Scheduled tasks set to execute today. Scheduled Tasks for tomorrow will
> be loaded in 57598 seconds.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Policy
> Cache Rebuild complete.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding
> Managed Path Cache...
> 01 2012-08-07 08:00:03 -14400 5 0004 30152 7ff78be7c710 MPC: Loading 0
> path entries into cache...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Managed
> Path Cache Rebuild complete.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding
> Event Cache...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Event
> Cache Rebuild complete.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Rebuilding
> Event Processor Data...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Event
> Processor Data Rebuild complete.
> 01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Base
> schema appears to be properly extended.
> 01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Action
> Object schema appears to be extended.
> 01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Legacy
> Collaborative Homedirectory attribute cccFSFactoryGroupHomedir is
> available.
> 01 2012-08-07 08:00:03 -14400 5 0002 30152 7ff78be7c710 GL: Legacy
> Quota Manager attribute cccFSFactoryHomeDirectoryQuota is available.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting
> the Task Manager subsystem...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Completed
> starting the Task Manager subsystem, bResult = 1.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting
> the HTTPx Server subsystem...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Completed
> starting the HTTPx Server subsystem, bResult = 1.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting
> Incoming Event Parser subsystem...
> 01 2012-08-07 08:00:03 -14400 2 0001 30152 7ff78be7c710 ML: Completed
> initialization. Engine is now running.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 WD: Engine
> mainline thread is entering the Watch Dog function...
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 WD: Engine is
> running...
> 01 2012-08-07 08:00:03 -14400 3 0001 30152 7ff78be7c710 WD: Detected
> that the Incoming Event Parser has terminated.
> 01 2012-08-07 08:00:03 -14400 5 0001 30152 7ff78be7c710 ML: Starting
> Incoming Event Parser subsystem...
> 01 2012-08-07 08:00:03 -14400 5 8006 30152 7ff75fb86710 TM:
> TaskManagerThread() - Thread has started.
>
>
Kenneth,
Please send us an email at [email protected] so we can look into
this issue further. If you could attach your latest Engine log file from
/var/opt/novell/storagemanager/engine/log, that would be helpful -- the
excerpt you've posted doesn't seem to provide much information about the
problem. Thanks!
- NFMS Support Team

Ovi ... Store? - Let's go back to NSM...

Nokia and/or Ovi team,
I know Ovi Store launched recently, and there are lots of things you are probably working on to get it going the right way.
I love looking for the best price when buying software. When I heard of Ovi Store, I knew there would be some software at a really tempting price, and so it is: Smartphoneware apps are really cheap (there may be other developers/apps as well, but I kept focus on Smartphoneware).
Having lots of previous purchases in other online stores (Handango, SymbianGear, Mobihand, SmartSym, Nokia Software Market, etc) I thought it would be similar... I was way WRONG!
Although there was not mention on how the new Ovi Store works, I decided to try it by buying an app and see how it worked. I chose a cheap, yet useful one: Smartphoneware Best Taskman.
I already had an old version (1.0) installed in my device, in trial mode.
What comes below is a list of things that shocked me and are definitely not properly implemented... at all!!
There should be an option to buy from a PC, like there was in Nokia Software Market (NSM).
How come the app is automatically installed? What if I did not wanted to install it right away? (In fact, in my case I wanted to keep the old version and try the serial number once purchased, which leads to...)
There are options to choose where to install the app (Phone memory or memory card); there should also be an option to install automatically or download for installing later.
I got an e-mail with my purchase information, but there was no serial #. What if I want/need to reset the phone and reinstall the app? Or what if I want to install a new version and it requests the serial? As far as I've read, many users reported you can't even re-download/install the app; you have to purchase it again (or place a complaint and wait until you hear back from support, which, as a customer experience, sucks!)
Even though I searched everywhere, there was no mention in the site or app about how the store works (the fact that it installs apps automatically, the fact that it doesn't give you a serial number, etc). This kind of information should be posted somewhere in the ovi store site and/or app so users are aware (I know, this would kill your business...). Should I had known it worked this way, I would have spent a little bit more and make sure I got a serial number.
Hope you guys are working already (or start) on these issues ASAP, else I can assure you Ovi Store won't last too long... and won't make much profit for the company.
Let's see it the other way as well: Maybe I'm a very dumb customer who is used to other "standard" online stores. Ovi Store is quite different.
Suggestion: Create and promote a tutorial on how to use it and which options it has (including, if available, how to recover the software and or serial number(s)).
A very frustrated customer.
Gonzo
Message Edited by pool7 on 06-Jun-2009 04:55 AM

It's great to know how things work first-hand. If anyone wants to know how the store purchase process works, you can read this blog entry (among other similar blog postings) to get an overview:
Buying through the Ovi store
Lumia 920, Lumia 800
Nokia N8-00 (NAM, Product Code: 059C8T6), Symbian Belle, Type RM-596, 111.030.0609
Nokia 5800 XpressMusic (NAM, Product Code: 0577454) Software v51.2.007, Type RM-428

NSM 3.1.1 server reguallry becomes unresponsive

We run NSM 3.1.1 for AD and I find that regularly for periods of several hours it is not possible to connect with NSMadmin, this also occurs if the NSM server is restarted. This is particularly annoying now that I am devolving administration of home drive quotas to our servicedesk using quota manager because while the server is in this condition, they cannot update quotas and receive a message that they are not members of the quota manager group. I also notice that our database (ecache.db) is approaching 25Gb, is there any housekeeping that can be carried out to prune this or is this normal?. I cannot find any guidance on tuning my environment for best performance. Being a University, we have a great deal of change in our environment with approximately 15,000 new students per year (and also 15,000 leaving).
Any help or advice would be appreciated,
Dave
Apologies for not being able to spell "regularly" :)

On 11/7/2013 7:36 AM, Davey1 wrote:
>
> We run NSM 3.1.1 for AD and I find that regularly for periods of several
> hours it is not possible to connect with NSMadmin, this also occurs if
> the NSM server is restarted. This is particularly annoying now that I am
> devolving administration of home drive quotas to our servicedesk using
> quota manager because while the server is in this condition, they cannot
> update quotas and receive a message that they are not members of the
> quota manager group. I also notice that our database (ecache.db) is
> approaching 25Gb, is there any housekeeping that can be carried out to
> prune this or is this normal?. I cannot find any guidance on tuning my
> environment for best performance. Being a University, we have a great
> deal of change in our environment with approximately 15,000 new students
> per year (and also 15,000 leaving).
> Any help or advice would be appreciated,
>
> Dave
>
> Apologies for not being able to spell "regularly" :)
>
>
Davey1,
The large ecache.db file is definitely one reason the Engine is slow to
respond upon restart. Is your ecache.db file not growing any larger? In
the Pending Events panel of the Admin client, in the bottom-right
corner, is the "cached events" counter at 0? If so, it's safe to perform
the following steps:
- stop accepting events
- double-check that the "cached events" counter is still at 0
- stop the engine
- rename the ecache.db file
- start the engine - it should create a new ecache.db (and your engine
should load much faster)
- start accepting events again
- if everything looks right, you can delete the old ecache file
-- NFMS Support Team

How do you change pending event path post mig to new server?

We upgraded from NSM 2.5 to 3 which necessitated a change of server. I migrated my polices (50+) so as not to have to recreate them as well as my pending events. The new users point to a new vault and I copied the old vaulted users there also. My issue is that my migged pending events (delete user after X days) still point to a server that no longer exists. Is there a way to modify the path to point of the old pending events to the new storage?

jlauzon,
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/

NSM Event Agent for AD location - Best practice

Hello,
We are currently designing our NSM 3.1 for AD implementation and would like some guidance with regard to installing the NSM Event Agent. We have come up with two options:
The first option is to install the NSM Event Agent on a Domain Controller where new user accounts are provisioned.
The second option is to install the NSM Event Agent on a server with the other NSM components.
The argument for option 1 is that NSM will be notified as soon as an account is created.
The argument for option 2 is that MS best practice is that no other software should be installed on a DC and that the NSM Event Agent will perform a network request to talk to the nearest domain controller to obtain a list of changes since it last connected.
Is there any preferred option, or does it not matter?
Regards,
Jonathan

On 10/28/2013 7:16 AM, JonathanCox wrote:
>
> Hello,
>
> We are currently designing our NSM 3.1 for AD implementation and would
> like some guidance with regard to installing the NSM Event Agent. We
> have come up with two options:
>
>
> - The first option is to install the NSM Event Agent on a Domain
> Controller where new user accounts are provisioned.
> - The second option is to install the NSM Event Agent on a server with
> the other NSM components.
>
>
>
> The argument for option 1 is that NSM will be notified as soon as an
> account is created.
> The argument for option 2 is that MS best practice is that no other
> software should be installed on a DC and that the NSM Event Agent will
> perform a network request to talk to the nearest domain controller to
> obtain a list of changes since it last connected.
>
> Is there any preferred option, or does it not matter?
>
> Regards,
>
> Jonathan
>
>
Jonathan,
Unlike eDirectory event monitoring, Active Directory event monitoring is
accomplished with a polling mechanism. Therefore putting your Event
Monitor on the domain controller will not significantly increase
performance. As long as the Event Monitor is in a site with a domain
controller, it should pick up events as quickly as it can.
For further reading on AD sites and domain/forest topology we recommend
reviewing http://technet.microsoft.com/en-us/l.../cc755294.aspx.
Remember that for AD, NSM requires only one Event Monitor per domain
(and in fact you'll only be able to authorize one Event Monitor per
domain through the NSM Admin client.) However, deploying a second Event
Monitor as a backup may be helpful. When the AD Event Monitor is
installed and configured for the first time, it first has to build a
locally-cached replica of the domain it resides in. In a large domain
this can take a long time, so having a second EM already running, which
can be authorized immediately if the primary EM goes down, will ensure
that you catch up with events in AD more quickly.
-- NFMS Support Team

NSM 3.0.4 Agent Not Starting

Hi,
I've just installed NSM 3.0.4 Agents (from the 3.0.4 iso) on OES11 (with all updates), and the agent is failing to start properly.
Here's what nsmagentd.log says:
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Initializing Logger, re-opening existing log file "/var/opt/novell/storagemanager/agent/log/nsmagentd-20
120709-154311.log".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This Logger class instance [0xa0b0f0] was initialized at 2012:07:09:16:57:44 in Process ID # 1408.
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 OS Version Info = "Kernel Name: Linux, Architecture: x86_64, Kernel Release: 2.6.32.59-0.3-default, Kern
el Version: #1 SMP 2012-04-27 11:14:44 +0200, Machine HW Name: x86_64", OS Bits = 64, Application binary file spec = "/opt/novell/storagemanager/agent/bin/ns
magentd", Application Bits = 64, Application Version = "v3.0.4.11".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This is the first time that a Logger thread has been started for this class instance.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Thread has started.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase I]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent's instance name = "".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting configuration path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting configuration path information, Result = 0, bOK = 1, path = "/etc/opt/novel
l/storagemanager/agent/config".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting program path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting program path information, bOK = 1, path = "/opt/novell/storagemanager/agent
/bin".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase I], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Initializing the Configuration...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Validating data path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed validating data path information, Data Path = "/var/opt/novell/storagemanager/agent/data"
, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Configuring the Logging subsystem [Phase II]...
82 2012-07-09 16:57:44 3600 0 ff04 1408 7f180acb5700 <CONFIG><LOGPATH>/var/opt/novell/storagemanager/agent/log</LOGPATH></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700 <CONFIG><LOGFILEBASENAME/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700 <CONFIG><LOGFILEBASENAME>nsmagentd</LOGFILEBASENAME></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff07 1408 7f180acb5700 <CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMA
X></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed configuring the Logging subsystem [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase II]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the XML Message Signature object...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed setting the XML Message Signature object, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the SSL/TLS certificate file...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed setting the SSL/TLS certificate file, sCertFileSpec = "/etc/opt/novell/storagemanager/age
nt/config/server.pem", bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is determining its own FQDN node name...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed determining its own FQDN node name, Result = 0, bOK = 1, Name = "zeus".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting O.S. version information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting O.S. version information, Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is getting file version information for itself ["/opt/novell/storagemanager/agent/bin/nsmagen
td"]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent completed getting file version information for itself ["/opt/novell/storagemanager/agent/bin/
nsmagentd"], Version = "3.0.4.11", Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading saved state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading the Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loaded the Salt state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed loading saved state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting Operational Data [Phase III]...
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Completed getting Operational Data [Phase III], bOK = 0.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 3 0001 1408 7f180b4b6700 ML: Called LoadStorageResourcesFromCache(), Result = 53.
01 2012-07-09 16:57:44 3600 1 0001 1408 7f180b4b6700 ML: Failed to initialize 1 or more components and/or subsystems. Agent is switching to stop-pending st
ate.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700 <CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is shutting down...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving the Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saved the Salt state information, bResult = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed saving state information, bOK = 1.
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Agent has shut down. Thread is terminating...
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Shutting down the Logger. Closing log file "/var/opt/novell/storagemanager/agent/log/nsmagentd-20120709
-154311.log".
81 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 <LOGFILECLOSE/>
Hope you can help!
Anthony

Did you run the agent-config? With 3.0.4 you need to generate a new server security certificate.
NSM Support
>>> psc<[email protected]> 7/9/2012 12:06 PM >>>
Hi,
I've just installed NSM 3.0.4 Agents (from the 3.0.4 iso) on OES11
(with all updates), and the agent is failing to start properly.
Here's what nsmagentd.log says:
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Initializing
Logger, re-opening existing log file
"/var/opt/novell/storagemanager/agent/log/nsmagentd-20
120709-154311.log".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This Logger class
instance [0xa0b0f0] was initialized at 2012:07:09:16:57:44 in Process ID
# 1408.
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 OS Version Info =
"Kernel Name: Linux, Architecture: x86_64, Kernel Release:
2.6.32.59-0.3-default, Kern
el Version: #1 SMP 2012-04-27 11:14:44 +0200, Machine HW Name: x86_64",
OS Bits = 64, Application binary file spec =
"/opt/novell/storagemanager/agent/bin/ns
magentd", Application Bits = 64, Application Version = "v3.0.4.11".
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 This is the first
time that a Logger thread has been started for this class instance.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Thread has
started.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase I]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent's
instance name = "".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting configuration path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting configuration path information, Result = 0, bOK = 1,
path = "/etc/opt/novel
l/storagemanager/agent/config".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting program path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting program path information, bOK = 1, path =
"/opt/novell/storagemanager/agent
/bin".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase I], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Initializing
the Configuration...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Validating
data path information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
validating data path information, Data Path =
"/var/opt/novell/storagemanager/agent/data"
, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Configuring
the Logging subsystem [Phase II]...
82 2012-07-09 16:57:44 3600 0 ff04 1408 7f180acb5700
<CONFIG><LOGPATH>/var/opt/novell/storagemanager/agent/log</LOGPATH></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700
<CONFIG><LOGFILEBASENAME/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff05 1408 7f180acb5700
<CONFIG><LOGFILEBASENAME>nsmagentd</LOGFILEBASENAME></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff07 1408 7f180acb5700
<CONFIG><ROLLOVERTYPE>2</ROLLOVERTYPE><FILESTORETAIN>10</FILESTORETAIN><FILESIZEMAX>10485760</FILESIZEMA
X></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
configuring the Logging subsystem [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase II]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the
XML Message Signature object...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
setting the XML Message Signature object, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Setting the
SSL/TLS certificate file...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
setting the SSL/TLS certificate file, sCertFileSpec =
"/etc/opt/novell/storagemanager/age
nt/config/server.pem", bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
determining its own FQDN node name...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed determining its own FQDN node name, Result = 0, bOK = 1, Name
= "zeus".
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting O.S. version information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting O.S. version information, Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
getting file version information for itself
["/opt/novell/storagemanager/agent/bin/nsmagen
td"]...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent
completed getting file version information for itself
["/opt/novell/storagemanager/agent/bin/
nsmagentd"], Version = "3.0.4.11", Result = 0, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase II], bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading saved
state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loading the
Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Loaded the
Salt state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
loading saved state information, bOK = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Getting
Operational Data [Phase III]...
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Completed
getting Operational Data [Phase III], bOK = 0.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 3 0001 1408 7f180b4b6700 ML: Called
LoadStorageResourcesFromCache(), Result = 53.
01 2012-07-09 16:57:44 3600 1 0001 1408 7f180b4b6700 ML: Failed to
initialize 1 or more components and/or subsystems. Agent is switching
to stop-pending st
ate.
82 2012-07-09 16:57:44 3600 0 ff08 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
82 2012-07-09 16:57:44 3600 0 ff09 1408 7f180acb5700
<CONFIG><LEVEL>5</LEVEL><CATEGORY/></CONFIG>
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Agent is
shutting down...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving state
information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saving the
Salt state information...
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Saved the
Salt state information, bResult = 1.
01 2012-07-09 16:57:44 3600 5 0001 1408 7f180b4b6700 ML: Completed
saving state information, bOK = 1.
01 2012-07-09 16:57:44 3600 2 0001 1408 7f180b4b6700 ML: Agent has
shut down. Thread is terminating...
01 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 Shutting down the
Logger. Closing log file
"/var/opt/novell/storagemanager/agent/log/nsmagentd-20120709
-154311.log".
81 2012-07-09 16:57:44 3600 0 8001 1408 7f180acb5700 <LOGFILECLOSE/>
Hope you can help!
Anthony
psc
psc's Profile: http://forums.novell.com/member.php?userid=6819
View this thread: http://forums.novell.com/showthread.php?t=457694

NSM 3.0.4 "Enforce Policy Path" problem

Hi,
I have run into a big problem using "Enforce Policy Path"
Due to some SAN changes we have created new USER volumes
And we are using "enforce policy path" for the user move proccess.
The problem is that if i run enforce policy path on say 200 users.
Every user will end up in the eliglible que wating for the policy to alow moves, so far so good.
When the policy eventualy alow moves the NSM engine will decide where to put the homedirs.
The problem is that NSM will loock at the volume list and pick the one volume whit most free space
and then the engine will send all my 200 users to that volume, even if its about to run full.
The engine will not change desination during the run even if the run will take 10 houers.
This is a realy big problem. I have filld volumes a cuple of times and it is not plessent to sort out that mess afterwards.
The dicison where to put the user shuld be made when the copying is begining, not when the policy alow moves.
Is this work as design or have i missed somthing?
The system:
NSM ENgine: NSM 3.0.4 running on SLES11 sp1 OES11
User volumes: OES11 cluster on SLES11 sp1
we are not using any kind of quota at this custumer
Best Regads
Johan

On 9/13/2012 4:16 PM, jkullberg wrote:
>
> Hi,
> I have run into a big problem using "Enforce Policy Path"
>
> Due to some SAN changes we have created new USER volumes
> And we are using "enforce policy path" for the user move proccess.
>
> The problem is that if i run enforce policy path on say 200 users.
> Every user will end up in the eliglible que wating for the policy to
> alow moves, so far so good.
>
> When the policy eventualy alow moves the NSM engine will decide where
> to put the homedirs.
> The problem is that NSM will loock at the volume list and pick the one
> volume whit most free space
> and then the engine will send all my 200 users to that volume, even if
> its about to run full.
>
> The engine will not change desination during the run even if the run
> will take 10 houers.
> This is a realy big problem. I have filld volumes a cuple of times and
> it is not plessent to sort out that mess afterwards.
>
> The dicison where to put the user shuld be made when the copying is
> begining, not when the policy alow moves.
>
> Is this work as design or have i missed somthing?
>
> The system:
> NSM ENgine: NSM 3.0.4 running on SLES11 sp1 OES11
> User volumes: OES11 cluster on SLES11 sp1
>
> we are not using any kind of quota at this custumer
>
> Best Regads
> Johan
>
>
Johan,
I believe we've addressed your concerns directly through our Support
team, but for anyone else experiencing similar behavior:
NSM calculates target path distributions when an event is put on the
queue. For large management actions, like an "Enforce Policy Path"
action with multiple target paths, using an "Available free space"
distribution method may well mean that all queued events are given the
same target path, since that path had more free space when the event was
initially created.
Therefore, if even or nearly-even distributions across multiple target
paths are desired, using the "Random" distribution method may be the
better choice for a large management action.
- NFMS Support Team

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

Qlogin , Sles 10 sp1 new disk LUN 7

new disk , Lun 7 ,/dev/sdh is not visibile , why?
The storage is configurated correct
ql-dynamic-tgt-lun-disc.sh, disk is not visibile
In the /var/log/messages
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:0:1:0 Cmnd failed-retry the same path. vcmnd SN 5020996424 pdev H2:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:0:0:0 Cmnd failed-retry the same path. vcmnd SN 5020996425 pdev H1:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:41 emmdbserver1prod kernel: 99 [RAIDarray.mpp]DS4700_EMM:1:0:6 mpp status 7
Jun 11 20:08:41 emmdbserver1prod kernel: 7 [RAIDarray.mpp]DS4700_EMM:1:0 Path Failed
Jun 11 20:08:46 emmdbserver1prod kernel: 495 [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry on a new path. vcmnd SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
Jun 11 20:08:46 emmdbserver1prod kernel: 493 [RAIDarray.mpp]DS4700_EMM:0:1:0 Cmnd failed-retry the same path. vcmnd SN 5020996424 pdev H2:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
"/var/log/messages" 23059L, 2158204C
Ciao e grazie
Mirco

This is not the right forum for this type of question, please try one of
the OES forums.
thanks,
NSM Development
On 6/13/2011 8:06 AM, eutile wrote:
>
> new disk , Lun 7 ,/dev/sdh is not visibile , why?
> The storage is configurated correct
>
> ql-dynamic-tgt-lun-disc.sh, disk is not visibile
>
> In the /var/log/messages
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry the same path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:0:1:0 Cmnd failed-retry the same path. vcmnd
> SN 5020996424 pdev H2:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:0:0:0 Cmnd failed-retry the same path. vcmnd
> SN 5020996425 pdev H1:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:41 emmdbserver1prod kernel: 99
> [RAIDarray.mpp]DS4700_EMM:1:0:6 mpp status 7
> Jun 11 20:08:41 emmdbserver1prod kernel: 7
> [RAIDarray.mpp]DS4700_EMM:1:0 Path Failed
> Jun 11 20:08:46 emmdbserver1prod kernel: 495
> [RAIDarray.mpp]DS4700_EMM:1:0:6 Cmnd failed-retry on a new path. vcmnd
> SN 5020996423 pdev H1:C0:T1:L6 0x00/0x00/0x00 0x00080000 mpp_status:7
> Jun 11 20:08:46 emmdbserver1prod kernel: 493
> [RAIDarray.mpp]DS4700_EMM:0:1:0 Cmnd failed-retry the same path. vcmnd
> SN 5020996424 pdev H2:C0:T0:L0 0x00/0x00/0x00 0x00080000 mpp_status:7
> "/var/log/messages" 23059L, 2158204C
>
> Ciao e grazie
> Mirco
>
>

Migration process...can't login to new server

Hello all,
I am on page 30 of the migration process where I need to login into the new
server running the NSMEngine. I put in a username and password, like I had
before...and it just hangs.
I read where it said that I may have to be a member of the NSMAdmins
group...there isn't any such group in eDirectory. I have migrated my
policies over and don't want to remove or reinstall anything for fear of
losing my policies.
Any thoughts?
Tom

Tom,
I need more information if I am going to be of assistance.
I need to know what version and platform your running.
thanks,
NSM Development
On 8/3/2011 1:35 PM, Tom Hafemann wrote:
> Hello all,
>
> I am on page 30 of the migration process where I need to login into the new
> server running the NSMEngine. I put in a username and password, like I had
> before...and it just hangs.
>
> I read where it said that I may have to be a member of the NSMAdmins
> group...there isn't any such group in eDirectory. I have migrated my
> policies over and don't want to remove or reinstall anything for fear of
> losing my policies.
>
> Any thoughts?
>
> Tom
>
>
>

New to AD NSM

Similar Messages

Maybe you are looking for