One of the differences between using a NetWorker server initiated backup vs client initiated backup is "who" is actually running the backup. i.e. What user account is being used when running the backup commands on the NetWorker client?
When you are on the NetWorker client and starting a backup manually, (eg: using the commands save or nsrsqlsv, savefs, etc) you are running these commands using the privileges that is assigned to the account you used to log into the host.
With server initiated backups, the NetWorker server contacts the client's nsrexecd process and tells it to run the commands on behalf of the server. The default account credentials used is the same account that is used to start up nsrexecd. This start up account can be determined by either going into Windows Services, and looking at the NetWorker Remote Exec properties, or from command line using: sc qc nsrexecd | findstr /i service_start
The account used to start server initiated backups can be changed by specifying the remote user in the NetWorker client resource.
"we also trying to take backup from client side & it was completed successful."
Please elaborate on how this was done? you mean that you ran this savefs command on the client side?
savefs -s ig-emc-nwkr.x.com -c abc.x.com -g TEST -p -l full -R -v -F MSSQL$PCTXCO02:'
Please check the following:
What is the NMM version?
What is the SQL version?
Are the NetWorker client and NMM software installed on all SQL nodes?
The output refers to this file for additional information. Did you look at this file? What additional information did it provide? "D:\Program Files\nsr\logs\sg\TEST\9117"
In the NetWorker client resources for these SQL servers, what are the:
backup command
remote user
Application information
If you are reluctant to share the information in this public forum, then please open a service request so that NetWorker support may assist you in detail.
In a SQL Server mirror relationship, two SQL Server instances are involved where
Server 1 instance 1 has the primary database, (think of this as "active" )
Server 2 instance 2 has the mirror database, (think of this as "standby" or the mirror copy of the primary)
You must create client resources for both server 1 and 2. but You cannot perform backups
of the mirror databases on server 2. You can only perform backups of primary databases on server 1.
You can perform backups of non mirror databases on server 2 any time. But not the mirror copy.
On the server 1 you can do level full and incremental backups of the primary database.
Lastly,
/-i. check the service account of SQL Server service on both SQL Servers.
Make sure the same Domain account is used. Does not have to domain admin.
During a scheduled backup, savefs contacts the primary SQL server, and Networker Remote exec service must be able to authenticate sql server on both nodes. The only way is to make the servce accounts of sqlserver the same.
/-ii. check Remote user field of the client resource ;
If any of the following is true then Remote User field needs the following permissions
--- must be a domain user with local windows administrator privileges, and SQL sysadmin rights on both SQL Servers.
• SQL Server is a clustered instance,
• SQL Server databases are involved in a mirroring relationship or replicated in SQL AlwaysOn Avail. Group
• SQL Server is version 2012 or higher (in any sense whether standalone or clustered)
One of the causes of no error is : on the client properties remove the user and password (since you already started the networker client service with the right account on the client)
wlee
263 Posts
0
March 30th, 2017 08:00
One of the differences between using a NetWorker server initiated backup vs client initiated backup is "who" is actually running the backup. i.e. What user account is being used when running the backup commands on the NetWorker client?
When you are on the NetWorker client and starting a backup manually, (eg: using the commands save or nsrsqlsv, savefs, etc) you are running these commands using the privileges that is assigned to the account you used to log into the host.
With server initiated backups, the NetWorker server contacts the client's nsrexecd process and tells it to run the commands on behalf of the server. The default account credentials used is the same account that is used to start up nsrexecd. This start up account can be determined by either going into Windows Services, and looking at the NetWorker Remote Exec properties, or from command line using: sc qc nsrexecd | findstr /i service_start
The account used to start server initiated backups can be changed by specifying the remote user in the NetWorker client resource.
"we also trying to take backup from client side & it was completed successful."
Please elaborate on how this was done? you mean that you ran this savefs command on the client side?
savefs -s ig-emc-nwkr.x.com -c abc.x.com -g TEST -p -l full -R -v -F MSSQL$PCTXCO02:'
Please check the following:
In the NetWorker client resources for these SQL servers, what are the:
If you are reluctant to share the information in this public forum, then please open a service request so that NetWorker support may assist you in detail.
mgennacc
13 Posts
0
May 3rd, 2017 13:00
In a SQL Server mirror relationship, two SQL Server instances are involved where
Server 1 instance 1 has the primary database, (think of this as "active" )
Server 2 instance 2 has the mirror database, (think of this as "standby" or the mirror copy of the primary)
You must create client resources for both server 1 and 2. but You cannot perform backups
of the mirror databases on server 2. You can only perform backups of primary databases on server 1.
You can perform backups of non mirror databases on server 2 any time. But not the mirror copy.
On the server 1 you can do level full and incremental backups of the primary database.
Lastly,
/-i. check the service account of SQL Server service on both SQL Servers.
Make sure the same Domain account is used. Does not have to domain admin.
During a scheduled backup, savefs contacts the primary SQL server, and Networker Remote exec service must be able to authenticate sql server on both nodes. The only way is to make the servce accounts of sqlserver the same.
/-ii. check Remote user field of the client resource ;
If any of the following is true then Remote User field needs the following permissions
--- must be a domain user with local windows administrator privileges, and SQL sysadmin rights on both SQL Servers.
• SQL Server is a clustered instance,
• SQL Server databases are involved in a mirroring relationship or replicated in SQL AlwaysOn Avail. Group
• SQL Server is version 2012 or higher (in any sense whether standalone or clustered)
l.walid
26 Posts
1
May 4th, 2017 07:00
Hi,
One of the causes of no error is : on the client properties remove the user and password (since you already started the networker client service with the right account on the client)