Skip to main content
Solved

Live sync Log Failover logshipping SQL error 30:436


Forum|alt.badge.img+14

Hello,

On a fresh installed LAB, I am trying to test my failover

 

I have followed this r good detailed procedure.

https://documentation.commvault.com/commvault/v11/article?p=102845.htm

 

I got an error message in the job controller when the cv failover logshipping start.

Error Code: [30:436] Description: Instance validation failed: Insufficient SQL Server role. To configure the instance, the user must be a member of the SYSADMIN SQL server role. Source: commserve, Process: JobManager 

 

which user should have the sysadmin rights ?

on the SQL management studio,

sqladmin_cv has sysadmin role and sqlexec_cv has only public

 

 

Thanks !

Best answer by Mike Struening RETIRED

@Bloopa is there any chance you have another account specified?

https://documentation.commvault.com/commvault/v11_sp20/article?p=18204.htm

View original
Did this answer your question?

6 replies

Forum|alt.badge.img+8
  • Byte
  • 57 replies
  • March 9, 2021

Hi,

Did you also check the database on the Standby CommServe?

__

Jeremy


Forum|alt.badge.img+14
  • Author
  • Byte
  • 115 replies
  • March 9, 2021

Hi @Jeremy,

Yes it is exactly the same config on the standby Commserve.

 


Mike Struening
Vaulter
Forum|alt.badge.img+23

 


Forum|alt.badge.img+14
  • Author
  • Byte
  • 115 replies
  • March 9, 2021

Hi @Mike Struening,

Thanks for your help.

On the two commserves PROD and standby, the NT AUTORITY\SYSTEM has the sysadmin role

here is the exact error message.

 


Mike Struening
Vaulter
Forum|alt.badge.img+23

@Bloopa is there any chance you have another account specified?

https://documentation.commvault.com/commvault/v11_sp20/article?p=18204.htm


Forum|alt.badge.img+14
  • Author
  • Byte
  • 115 replies
  • March 9, 2021

Thanks to all. 

On each instance I had to specify this.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings