Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

hastop -local -noautodisable vs hastop -local

Created: 11 May 2011 • Updated: 11 May 2011 | 1 comment
This issue has been solved. See solution.

What exactly is the difference between "hastop -local" and "hastop -local -noautodisable" ?

By that I mean, the scenario is: 

  • stop VCS and the service groups running locally on the server,
  • reboot the server,
  • after the reboot, make sure the service groups that were running before are online on the rebooted server

So does the "-noautodisable" really do anything in this scenario or is this option not needed?

Comments 1 CommentJump to latest comment

mikebounds's picture

Without "noautodisable", if you offline a service group that can run on the node that you run hastop on, then you cannot online that service group unless you autoenable it.  This is because VCS cannot be certain that the service group has not been brought up on the node you have run hastop on.

So for example if you have SysA and SysB and SG1 which can run on SysA and SysB and you run hastop -local on SysA where SG1 is online.  If you now try to online SG1 on SysB, this will only work if you ran "hastop -local" with "-noautodisable".  If you did not, then you would need to run "hagrp -autoenable SG1 -sys SysA" in order to then be able to run "hagrp -online SG1 -sys SysB".

So in your scenario, it looks like you don't need "noautodisable" flag.

Mike

UK Symantec Consultant in VCS, GCO, SF, VVR, VxAT on Solaris, AIX, HP-ux, Linux & Windows

If this post has answered your question then please click on "Mark as solution" link below

SOLUTION