Video Screencast Help
Search Video Help Close Back
to help

VCS Cluster 4.1 - hasnap utility : change configuration before starting up imported snapshot

Created: 22 May 2012 | 1 comment
krisofe's picture
0 0 Votes
Login to vote

Hi All,

 

I have to migrate a vcs from an oldproduction environment to the newone.

All configurations are identical except @IP, mounting filer and all traditionnals parameters.

I have never used this command but just a try to backup and I doesn't know in detail the technical architecture.

 

So, with a hasnap -backup and restore from the old to the know,

I want to change the main.cf before all and so start vcs on the newone (with temporarely endpoints filer whichs attack other filer).

 

But I DO NOT want vcs starts automaticaly because the endpoint filer are reachable since both vcs.

If the newcluster automaticaly starts, it will make a disaster with the real old vcs environement which is in production.

 

Any help about this tool pls ?

 

Thks a lot,

 

Christophe, FR

Comments 1 CommentJump to latest comment

mikebounds's picture

There are several things you can do to stop VCS starting automatically:

  1. Move llttab and gabtab out of the way
  2. Disabled LLT and GAB startup scripts.
  3. Set AutoStart to zero for all service groups
  4. Permanently freeze all service groups.

1 or 2 is sufficient, but I often do more being paranoid.  I don't think hasnap is really suitable as this is for taking snapshot so that you can restore back to snapshot of you make changes and then want to undo changes.  I would just copy main.cf to new cluster and amend if you need to.

Mike

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

If this post has helped you, please vote or mark as solution

0
Login to vote
  • Actions