Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

EV FSA agent and Veritas Cluster Server

Updated: 03 Mar 2012 | 3 comments
Richard Sendall1's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello,

I have a 2 file servers that are clustered together using Veritas Cluster Server (VCS) storage foundation for windows HA.  In this VCS cluster, I have created a single service group to hold the virtual file server with its own IP address and host name.  Or in other words, I have a single virtual file server that is hosted on 2 physical nodes in Active/Passive mode using VCS.  Note this is VCS and not MSCS.

I would like to install the EV FSA agent into the virtual file server.  There are instructions to do this in section 3 of the "Setting up File System Archiving (FSA)" guide, however, I am not able to follow the steps in the sub section "Authenticating the Administration Console with VCS - Authenticating the Administration Console when SPAS is not used".  This is becuase the service account we use for Enterprise Vault contains a name which is not valid in VCS.  The service account name we use is _lonevlondon which has an underscore at the front - VCS will not accept underscores in usernames.  So I cannot execute step 3 on page 95 of the above mentioned guide.

Therefore, I would like to know how I can manually add the EV FSA agent to VCS so that it fails over with the file server service group.

I have tried adding it as a generic service, but this does not work, I guess there are extra things that need to be added to types.cf and main.cf that a generic service does not do.

I am using EV version 9 on a Windows 2008 Enterprise (not R2) cluster, the VCS version is 5.1 SP1.

Many thanks.

Richard.

Comments

Maverik's picture
02
Dec
2011
0 Votes 0
Login to vote

The question for me here is

The question for me here is why VCS cannot accept this?  Do you know the reason?  Sounds more like a bug to me that needs addressing as with any ligitimate character that can be used in an account.  

TonySterling's picture
06
Dec
2011
1 Vote +1
Login to vote

Unless you can convince the

Unless you can convince the VCS folks to change their software I would recommend changing the Vault Service Account to meets the criteria for VCS.

Changing the Vault Service account

Article: HOWTO37157         Article URL http://www.symantec.com/docs/HOWTO37157

Tony Sterling
www.bluesource.net or www.bluesource.co.uk
Offices in the US and the UK

abhishin86's picture
07
Dec
2011
1 Vote -1
Login to vote

Manual installation of FSA agent

You can go for manual installation of FSA agent on each active & passive node separately instead of push install. Use EV installed folder path to copy the setup files to file share server.

 e.g. C:\Enterprise Vault\evpush\Agent