+5Hi
how can i identify which users impersonate to SQL backup for logshipping job?
(Subclient - CvFailoverLogShipping)
its suppose to be in the SQL the installed on the Comserve itself? if so, i can identify it?
i want to switch the user that do this backup, i created a specific user that cannot lock...just need to configure it in SSMS :)
Thanks
Best answer by Brian Bruno
Hi
Apologies that I misunderstood your original question. The User will need to be configured in SQL Under Security > Logins. You don’t need to worry about doing any specific User Mappings to any particular database, as you will need to grant this user the ‘sysadmin’ role. This role gives it access to all databases in the instance with all permissions that we require, so there’s no need to configure anything more granular.
If you’ve not done so already, create the new user here:
Assuming that this is for a Windows-based MSSQL Server Instance, we will need to leverage an account that meets 2 criteria on the server:
Once you have ensured that your new user has appropriate permissions both within Windows as well as the sysadmin role within SQL Server, you should now be able to define that account in Commvault in the locations I shared in my previous response and the backup should work as expected.
-Brian Bruno
Hi
This can be changed at the Instance level of SQL Clients that are performing the Log Shipping.
For the Java GUI:
For Command Center:
Make sure that the account in question has ‘sysadmin’ role on the SQL Instance, and you should be good to go.
Please let me know if you have any further questions.
-Brian Bruno
+5Hi
Thanks for the response
but this is not what i asked…
i created a new user...so i need to configure it somewhere on the SQL Studio,,,in the logins….right?
my question is:
i need to configure the user on the comserve database? or somewhere else?
and another thing..i tried to do what u suggest..on other sql client:
Hi
Apologies that I misunderstood your original question. The User will need to be configured in SQL Under Security > Logins. You don’t need to worry about doing any specific User Mappings to any particular database, as you will need to grant this user the ‘sysadmin’ role. This role gives it access to all databases in the instance with all permissions that we require, so there’s no need to configure anything more granular.
If you’ve not done so already, create the new user here:
Assuming that this is for a Windows-based MSSQL Server Instance, we will need to leverage an account that meets 2 criteria on the server:
Once you have ensured that your new user has appropriate permissions both within Windows as well as the sysadmin role within SQL Server, you should now be able to define that account in Commvault in the locations I shared in my previous response and the backup should work as expected.
-Brian Bruno
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
