Re: secondary control station

This is expected with the dual control station as the second control station is working as a standby to the primary control station, The NAS service runs only on one Control Station which is the active one at that time. So in normal case, primary CS is the active one and the secondary CS is the standby.

You may run /nas/sbin/getreson command on the active CS – which will tell you slot 0 is primary CS and slot 1 is secondary.

Primary CS has all NAs volumes mounted and NAS service available – standby CS is only having its internal volumes.

In case Primary (Active) CS fails or administrator fails over the CS functionality manually (/nas/sbin/cs_standby command) – then the secondary CS becomes the Primary or active one.

On Celerra Manager – if you go to the Control Station property page – it should show that “standby ready“. Similarly the /nass/sbin/getreason command will tell you whether the standby CS is available or not. If so, there is no action needed from your end.

Hope this helps,




  • No Related Posts

Re: parsing error uemcli create snapshot


I’m not an engineer, but I’m looking into this from a documentation perspective. This switch has changed a couple of times since Unity came out, so because it could depend on your OE, I’d recommend running the -h option on /prot/snap create to get the correct info.

I believe the switch should be -replicateSnap and you should drop the “yes” after it.

/prot/snap create [ -async ] -source <value> [ -name <value> ] [ -descr <value> ] [ -access { ckpt | share } ] [ { -keepFor <value> | -allowAutoDelete { yes | no } } ] [ -replicateSnap [ { -keepSameAsSource | -keepRemotelyFor <value> | -allowRemoteAutoDelete { yes | no } } ] ]

Hopefully I can confirm this shortly with Engineering and get the document updated for our next release.




Re: Extending VNX NAS Checkpoint Retention

I was just asked to retain some specific snapshots/checkpoints on our VNX hosted NAS file system, that will hit their expiration date in a couple of days. I suspect this is a command line process, which I am not very familiar with. I have been reviewing EMC docs and online resources, but not making much progress.

Is this an “fs_ckpt” command or a “naviseccli -h SPA snap -modify” command?

I am getting very concerned about the expiration of these before I figure it out.

I would greatly appreciate some guidance and examples on this, please.

Thank you



  • No Related Posts

DLO 2010 storage change

I need a solution

We are using symantec DLO 2010 (looking into replacement) I’m replacing our nas so I need to move the storage location to the new nas.
This has been setup by my predecesor and from the console you can’t configure the storage location on a nas.

I think it should be posible to change this in the sqldb itself but i’m not entirely sure how to go about it.
Is there anyone here that has experience with this and might be able to explain to me how to do this?

Best regards, 



  • No Related Posts

Unable to rollout the installed application.

I have installed “MAXIMO” application with edition name(build_20171026_1151) and tried to rollout the installed edition , But rollout failed with below error message:

**SystemOut.log :**
[10/25/17 19:15:11:728 UTC] 00000534 ApplicationEd E Multiple Rollouts not allowed!!
[10/25/17 19:15:11:729 UTC] 00000534 ApplicationEd I WPVR0011E: Rollout of edition build_20171026_1151 of application MAXIMO failed. Check the log for details.

Gone through the logs but unable to find any clue on the error message.

AdminTask.rolloutEdition(‘[-appName MAXIMO -edition build_20171026_1151 -params “{rolloutStrategy grouped}{resetStrategy soft}{groupSize 1}{drainageInterval 60}”]’)

![alt text][1]

Please help me to resolve this issue.
Thanks in advance!

[1]: /answers/storage/temp/18170-770bfb0bd8770965.jpg