Error when i trie to backup sql

Question

Hello i have a issue when i trie backup instance sql: TL_Windows_SQL_Semanal_04S -p -l full -R -v -F MSSQL$DATACARD:' for client 'servername' exited with return code 1103/07/2023 04:45:53 p.m. servername:savefs unexpectedly exited.03/07/2023 04:45:53 p.m. servername:savefs will retry 2 more time(s). Job 10070145 host: 'servername' savepoint: MSSQL$DATACARD: had ERROR indication(s) at completionClient 'servername' is being skipped because no savesets of this client have been backed up as part of the backup action.Action backup traditional 'backup' with job id 10070141 is exiting with status 'failed', exit code 1 It is a server that I did not backup, so I installed the client from 0, with the account that is used in networker has sysadmin permissions in the sql. thank you very much for your help I have checked the vss writers and they are all error free. Thank you very much for your help

Matias.A · Accepted Answer

Thanks for your help, but I've already solved it, and in case it helps others.
When we go to the local services of the vm (SQL) to which we wanted to backup, we see that it was with the system account, and when trying to change it, we see that it is grayed out, then there we realized that this account is not as local administrator of the team, we request to add the account with which Networker makes the backup, put it in local administrators, and that solved the problem.

Thanks for your help

Regards

crazyrov · Answer

Hey @Matias.A ! Was this client configured manually or using the client creation wizard. Can you please check what the backup command is set for the client instance that you are trying to backup with.

Matias.A · Answer

Hello @crazyrov Thanks for you reply the comand is: nsrsqlsv -k -u, the command was copied from the job with another sql that does work, otherwise it was originally: nsrsqlsv Regards

crazyrov · Answer

Was this client created manually or using the wizard. If manually done can you doing this via the wizard, you might get a better error that we can work with.

NetWorker

Was this post helpful?