Unsolved
This post is more than 5 years old
17 Posts
0
1827
nsrsnap_vss_save -? would not list application save sets
We are having SharePoint 2010 Env farm, which needs to be backed up by NMM 8.2.
When I am trying to list the valid save sets in SharePoint Web/App servers with nsrsnap_vss_save -? it is exiting with success without listing the Application save sets.
Though the SPwriter and Osearch14 writers are in stable and running state. Below is the sample output of the error....
PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN> nsrsnap_vss_save.exe -? -D5
01/23/15 16:26:38.278196 Running in a non-cluster environment
NMM .. current installed NetWorker version for client Webserver is 8.2. Using _nt version to check for cluster status.
NMM .. changing backup name Webserver to primary name Webserver for multi NIC client.
NMM .. started RM session with client.
List of valid saveset entries for APPLICATIONS on client Webserver ...
Initializing data to display...
NMM .. created RM deposit path C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\Task Scheduler Writer23162640399.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\VSS Metadata Store Writer23162640992.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\Performance Counters Writer23162641585.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\System Writer23162642178.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\ASR Writer23162643504.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\SharePoint Services Writer23162644112.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\OSearch14 VSS Writer2316264973.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\COM+ REGDB Writer23162649666.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\IIS Metabase Writer23162650259.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\Shadow Copy Optimization Writer23162650867.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\Registry Writer23162651444.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\NPS VSS Writer2316265253.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\WMI Writer23162652661.xml.
NMM .. RM deposited WMD -- C:\Users\SVC_SP~1\AppData\Local\Temp\RMDir_23162638527\IIS Config Writer23162653238.xml.
01/23/15 16:26:53.862696 lgto_auth for `nsrexec' succeeded
NMM .. writer ASR Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:53.909496 lgto_auth for `nsrexec' succeeded
NMM .. Supported writer COM+ REGDB Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
01/23/15 16:26:53.971897 lgto_auth for `nsrexec' succeeded
NMM .. Supported writer IIS Config Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
01/23/15 16:26:54.018697 lgto_auth for `nsrexec' succeeded
NMM .. Supported writer IIS Metabase Writer vss type System Service - NMM saveset type SYSTEM COMPONENTS.
01/23/15 16:26:54.065497 lgto_auth for `nsrexec' succeeded
NMM .. writer NPS VSS Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.127898 lgto_auth for `nsrexec' succeeded
NMM .. Informational .. writer OSearch14 VSS Writer has no components.
NMM .. Supported writer OSearch14 VSS Writer vss type User Data - NMM saveset type APPLICATIONS.
01/23/15 16:26:54.190298 lgto_auth for `nsrexec' succeeded
NMM .. writer Performance Counters Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.237098 lgto_auth for `nsrexec' succeeded
NMM .. Supported writer Registry Writer vss type Bootable System State - NMM saveset type SYSTEM COMPONENTS:\BootableSystemState.
01/23/15 16:26:54.283899 lgto_auth for `nsrexec' succeeded
NMM .. writer Shadow Copy Optimization Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.330699 lgto_auth for `nsrexec' succeeded
NMM .. Informational .. writer SharePoint Services Writer has no components.
NMM .. Supported writer SharePoint Services Writer vss type User Data - NMM saveset type APPLICATIONS.
01/23/15 16:26:54.564701 lgto_auth for `nsrexec' succeeded
NMM .. writer System Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.611501 lgto_auth for `nsrexec' succeeded
NMM .. writer Task Scheduler Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.658301 lgto_auth for `nsrexec' succeeded
NMM .. writer VSS Metadata Store Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
01/23/15 16:26:54.705101 lgto_auth for `nsrexec' succeeded
NMM .. writer WMI Writer is not supported and will not participate in the replica. Writers files will be skipped during backup.
102332:nsrsnap_vss_save:Exiting with success.
PS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN>
Any help is much appreciated.....
CarlosRojas
1.7K Posts
0
January 23rd, 2015 03:00
Hi Santhana
First of all please try to run the command with the -v option on the WFE:
nsrsnap_vss_save -v -?
If still not working please make sure the WSS writer is registered and also that the required permissions have been granted on the SQL side.
Can you please describe a bit the SP farm topology?
Also as always with NMM, please check the Application and System event logs in case there is any issue with SharePoint itself.
Thank you,
Carlos
CarlosRojas
1.7K Posts
0
January 23rd, 2015 04:00
I assume we are talking about SP 2010, correct?
If so, have you registered the WSS writer in ALL the WFE servers?
Ensure all prerequisites are met:
Ensure that the following prerequisites are taken care of before performing SharePoint Server scheduled backups:
◆ The NetWorker client and NMM are installed on hosts with data that needs to be backed up.
◆ The SharePoint services Writer is registered, so that the save sets can be browsed and backed up successfully.
◆ The nsrsnap_vss_save command runs under the security context of SYSTEM user. So that the SYSTEM user can run SharePoint PowerShell, provide the required permission:
•For SharePoint Server 2010 and SharePoint Server 2013, perform both the following steps:
–Use the command: Add-SPShellAdmin -UserName " \ $"
This command must be used on each web front-end server and the Search server.
Verify that the SYSTEM account is added to SPShellAdmin by using the commandGet-SPShellAdmin.
–In the SQL Management Studio > Security > Login > Login Properties page, grant the SQL Server system dbcreator, public, and sysadmin permissions to the Windows login account, as shown in the following figure. Provide these permissions to the NTAUTHORITY\SYSTEM user on a stand-alone farm and to the DOMAIN\HOSTNAME$ user on a distributed farm. ç
•For SharePoint Server 2007, grant the SQL Server system dbcreator, public, and sysadmin permissions to the Windows login account. Provide these permissions to the NTAUTHORITY\SYSTEM user on a stand-alone farm and to the DOMAIN\HOSTNAME$ user on a distributed farm.
◆ Ensure that all the SharePoint Server databases are mounted before backing up the application server. Unmounted SharePoint Server databases are not backed up.
◆ Do not move or change the Admin component of Search inside the same SharePoint Server after installation.
◆ If any major change is made to the SharePoint Server configuration or database structure, perform a fresh backup. For example, if you have performed a farm backup on Monday, and have added a new content database on Tuesday, then perform a fresh backup of the complete farm to keep the backup up-to-date.
◆ Configure the SharePoint Server farm with the SQL Server using FQDN or shortname of the SQL Server and not the SQL Server IP. An alias should not exist for a dependent SQL Server when using the Client Backup Configuration wizard to create a client resource.
An error occurs, when some web applications in the SharePoint farm are configured with SQL Server IP and other web applications are configured with SQL Server shortname.
If a SharePoint farm is configured with an SQL Server using the IP of the SQL Server and client resources for the SharePoint farm are created by using the Client Backup Configurationwizard, the SQL cluster virtual client resource summary displays both the IP and shortname in “other client” resource. Subsequently, the client resources created for the SharePoint Server and the SQL Server fail with the error “ shortname> is already an alias of the ”.
Thank you,
Carlos
Santhana1
17 Posts
0
January 23rd, 2015 04:00
Please find the output of nsrsnap_vss_save -v -?
The sharepoint writer is registered already and is started with full farm permissions.. the command above is also run with the same privilege level..
I am not able to see any errors related to SP servies and NMM services in the App and System logs.
Can you please describe a bit the SP farm topology?
The farm contain.. 2 web servers (query and index, web services), 3 application servers (runnig crawl and service app) and 1 SQL server as backend to hold the farm config and other content DBs.
Santhana1
17 Posts
0
January 27th, 2015 04:00
I assume we are talking about SP 2010, correct?
yes, Its a SP 2010 Env
If so, have you registered the WSS writer in ALL the WFE servers?
Yes, the Writers are registered in the WFE server..
The prerequsite are met with. What is confounding is.. despite the farm account having full access to the farm and that is used to run the backup successfully from NMM 8.2 has stopped listing the save sets after a webapp restore that was done recently.
CarlosRojas
1.7K Posts
0
January 28th, 2015 04:00
Hi Santhana
If a web app was restored that means that most likely the SQL DB was also restored, so please check if the permissions are set correctly on the SQL side.
Also check with the SP admin to find out the changes done, and what changes that changes were committed in the DB based on the PIT selected.
Thank you,
Carlos