03-16-2016 03:51 AM
Hello all!
Got NBU 7.6.0.4 server on Win 2008 R2 and Sharepoint farm on Win 2012 R2(web and database servers)
Tryin to configure SP DB backups by manuals like that:
https://www.veritas.com/support/en_US/article.TECH146218
But after all manipulations still not able to view SP objects in the GUI when pointin backup objects
Also same trouble on SP server when launch BAR GUI like pointed in manual URL above "Check if you can view the objects under Microsoft SharePoint Resources:\"
Can u provide me how to fix it, please ?
Screenshots attached
03-16-2016 05:21 AM
I think you should first check with the bplist command if able to see the details.. if not then check what is error message and then look for bprd and bpdbm logs on the master server
https://www.veritas.com/support/en_US/article.000093140
03-16-2016 09:20 AM
First doublecheck all items listed in the guide.
Increase client verbosity in host properties on BAR gui.
Create vnted and bpcd log.
Restart services.
Check vnetd and bpcd logs for impersonation issues.
Set the client services from step 3 from the specified user to localsystem and restart services to see if that resolves the issue. (It can display but may not be able to back up like this.)
Only the FE really needs to be able to see this so while it is nice to have some of the other servers able to enumerate SP objects, it is not always necessary.
03-16-2016 11:47 AM
Most likely permissions issue ( don't ask me how I know )
Download sharepoint_check utility and run on each SharePoint server in the Farm (web, app, database)
https://www.veritas.com/community/downloads/sharepointcheckexe-configuration-checker
03-16-2016 04:29 PM
The technote you followed is old. There is a better one which covers more steps (for GRT) and permissions required:
03-30-2016 10:18 PM
Hello all!
Thanks for your reply.
In logs no information about job IDs or client name i needed(or need to search by another criteria)
Settin services to local system and back-than in client GUI sharepoint tab apperas
sharepoint_check utility shows what:
Replace a Process Level Token : DISABLED(but its enabled in secpol)
Debug Programs : DISABLED(but its enabled in secpol)
Publisher's Certificate Revocation is : CHECKED(but its unchecked in IE options)
Now backups fails with code 71, and errors like below:
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Warning 398151 Backup from client infosec.eub.kz: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\User Profile Service Application/Proxy (KZWSSQL01/8fc08b77-ffe9-407c-9c6f-3d0427ea9d56)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Error 398151 Backup socket operation failed - 10054 (at child.c.1304)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Warning 398151 Backup from client infosec.eub.kz: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\Visio Graphics Service/Proxy (KZWSSQL01/c30397e1-89f0-4351-914e-734b1e0ce0c5)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Error 398151 Backup unable to perform read from client socket, connection may have been broken
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Warning 398151 Backup from client infosec.eub.kz: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\Word Automation Services/Proxy (KZWSSQL01/29158f90-2a43-47df-910a-7f8fc6f18511)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Warning 398151 Backup from client infosec.eub.kz: WRN - object not found for file system backup: Microsoft SharePoint Resources:\Shared Services\Shared Services Proxies\Work Management Service Application/Proxy (KZWSSQL01/de565ecc-e5df-4a8b-b279-1f105436183d)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Warning 398151 Backup from client infosec.eub.kz: WRN - object not found for file system backup: Microsoft SharePoint Resources:\WSS_Administration\WebApplication\Content-DB 1 (KZWSSQL01/KZWSSQL_DB/SharePoint_AdminContent_a702c758-55b1-482f-af3a-1ae08b25901a)
30.03.2016 17:07:51 kzwnb01.eub.kz infosec.eub.kz Error 398151 Backup could not send server status message
30.03.2016 17:07:53 kzwnb01.eub.kz infosec.eub.kz Error 398151 Backup backup of client infosec.eub.kz exited with status 71 (None of the files mentioned in the file list exist or may not be accessible)
30.03.2016 17:07:54 kzwnb01.eub.kz infosec.eub.kz Error 398149 Backup backup of client infosec.eub.kz exited with status 71 (None of the files mentioned in the file list exist or may not be accessible)
All services were restarted(servers rebooted too)
Is it any idea to do next?
Thanks a lot
04-01-2016 12:42 AM
Hello!
SP servers were rebooted and in sharepoint_check utility now shows "all green" (passes all the checks)
But backups still fails with error 71
04-01-2016 07:16 AM
If your SQL Servers are in an HA configuration, that is a problem... I got the 71 exit error also (I was on 7.6.1.2), opened up a ticket with Symantec (at the time) and after several log dumps and checks and such, I was told that this version (so I would assume 7.6.0.4 would be the same) does not support backing up Sharepoint objects if the SQL servers are in an HA configuration.
04-03-2016 10:32 PM
Do u mean "AlwaysOn High Availability" ? Its not configured
04-03-2016 11:50 PM
04-04-2016 06:50 AM
Hello,
maybe it would be more effective to log a support call for this. Sharepoint issues are sometimes too complex to solve them on the forum.
However, double-check using the same account for both NBU/SPS configuration and local testing of visibility of Sharepoint objects in BAR. This is my suspicion because sharepoint_check.exe reported "DISABLED" for group policy account checks.
Note that bpdbm and bprd logs won't be useful for this issue. These are NBU server-side logs. bpcd is a client-side logs but very general for Sharepoint troubleshooting. Maybe bpresolver log from web frontend will be most useful.
Regards
Michal
04-04-2016 09:54 AM
And yet another possibility: http://www.veritas.com/docs/000095083
There's so many things that can go wrong with SharePoint configuration.
04-04-2016 01:47 PM
Hello EUB,
can you please check if the following regestry keys exists on your server: https://www.veritas.com/support/en_US/article.TECH203759
The Farms key or values are not created during the first SharePoint backup most commonly caused by permission issues.
2. Open a command prompt and run the following (replace <clientname> with the name of your FEWS used in the backup policy):
<install_path>\veritas\netbackup\bin\bpresolver.exe query -c <clientname> -ct 8 -init_beds "Microsoft SharePoint Resources:\*"
If FEWS is Windows 2008 or later, you may have to right-click on the command prompt and choose Run as Administrator when running the command.
To verify the command properly published the registry key, open your registry on your Frontend and SQL servers and navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\NetBackup\BEDS\Engine\SharePoint\Farms.
You should have a String Value with the Name set to the <SQL server Name>\<Instance Name, if applicable>\<Config Database Name> and the Data is the <Frontend Web Server Name> in parenthesis (). If you have multiple FEWS they will all be listed and separated by commas. If you have multiple Farms using the same SQL server, the SQL server should have multiple entries for each Farm (see Figure for example).
Note: If the <SQL server Name>\<Instance Name, if applicable>\<Config Database Name> key is not present on the Front-end server, then manually copy this key from the database node to the Front-end server.
best regards,
Cruisen
04-04-2016 02:20 PM
Different link but points to the same article.
04-04-2016 02:32 PM
Sorry Will Restore,
was really not my intention, thank you for pointing this out.
04-05-2016 12:46 AM
Hello all!
Thanks for your comments.
sharepoint_check utility shows what all is good, as i pointed above.
bpresover were started and then i checked up registry keys: on sql-prestents, app server-empty(added manually)
restartin services
Backup still fails with error 71
04-05-2016 06:04 AM
OK, now take a look at the bpresolver log or attach the file to your post.
04-06-2016 12:11 AM
Hello!
Here it is, kinda 87 error
13:08:09.010 [9972.3524] <2> logparams: bpresolver.exe query -c infosec.eub.kz -ct 8 -init_beds Microsoft SharePoint Resources:\*
13:08:09.010 [9972.3524] <4> send_start_msg(): INF - RESOLVER START 9972
13:08:09.010 [9972.3524] <4> send_start_msg(): BPRESOLVER has executed on server (KZWNB01)
13:08:09.010 [9972.3524] <4> process_filelist_rec: processing directive:<Microsoft SharePoint Resources:\*>
13:08:09.010 [9972.3524] <4> process_filelist_rec: formatted directive:<Microsoft SharePoint Resources:\*>
13:08:09.010 [9972.3524] <4> bpresolver_main(): dbext_object_type = 210000
13:08:09.088 [9972.3524] <2> set_sharepoint_impersonation: SE_IMPERSONATE_NAME is already enabled
13:08:09.088 [9972.3524] <16> set_sharepoint_impersonation: Login failed for user: with error 87.
13:08:09.088 [9972.3524] <4> ubs_GetSPSv2Topology: return code from ubsMapFarm is 00
13:08:09.088 [9972.3524] <4> ubs_GetSPSv2Topology: directive <Microsoft SharePoint Resources:\*> properly resolved
13:08:09.104 [9972.3524] <4> bpresolver_main(): INF - return code 0
13:08:09.104 [9972.3524] <4> bpresolver_main(): INF - EXIT STATUS 0
04-06-2016 09:22 AM
Well that certainly looks like bad credentials. Back to the basics.
Permissions - **All Sharepoint (frontend, index, central admin servers) and SQL backend servers must have the same permissions**
- The Netbackup Client Service, Netbackup Legacy Client Service, and Netbackup Legacy Network Service (if using Netbackup 7.0.1. and higher) on each server must run as a Domain account
- Must be a Local Administrator on each server
- Must have the following on each server (Administrator Tools - Local Security Policy - User Rights Assignment)
- **Even though the account is a local admin to the server, the account must be specified to work properly.
- Allow log on locally
- Debug Programs
- Log on as a Service
- Replace a process level token
- Must be a Sharepoint Farm Administrator
- Must have Site Collections Administration rights
- Must have System Administrator role in SQL
- In the Netbackup Admin console:
- Expand Host Properties - clients
- This must be done on EVERY server in the Sharepoint farm as well as SQL. If SQL is clustered, you must check the clustered name as well as the node names
- If a server is NOT listed in the clients, you can go to Actions - Configure Clients
- In the properties of each client, expand Windows Client and highlight Sharepoint
- Add the account (DOMAIN\username) and password
- Expand Host Properties - Master Server - open the properties of the master server
- Highlight Distributed Application Restore Mapping
- Specify the name of the Sharepoint server in the backup policy as the application host (either a Front End Web server or the Central Admin Server - see 7-a to determine the appropriate name)
- Specify the name of the SQL server as the component host
- If SQL is clustered, you will need entries for the SQL cluster name and each node.
04-11-2016 10:56 PM
Hello!
Thanks a lot for yours help
Checked all settings few times
Reinstallin agents on SP servers
Makin new NBU policy
Same error(71) if backed up by alias name(DNS record) of SP server
Error 13 if backed up by hostname(SP aplication server)
bpresolver:
11:52:32.149 [10368.2432] <2> logparams: bpresolver.exe query -c infosec.eub.kz -ct 8 -init_beds Microsoft SharePoint Resources:\*
11:52:32.165 [10368.2432] <4> send_start_msg(): INF - RESOLVER START 10368
11:52:32.165 [10368.2432] <4> send_start_msg(): BPRESOLVER has executed on server (KZWNB01)
11:52:32.165 [10368.2432] <4> process_filelist_rec: processing directive:<Microsoft SharePoint Resources:\*>
11:52:32.165 [10368.2432] <4> process_filelist_rec: formatted directive:<Microsoft SharePoint Resources:\*>
11:52:32.165 [10368.2432] <4> bpresolver_main(): dbext_object_type = 210000
11:52:32.243 [10368.2432] <2> set_sharepoint_impersonation: SE_IMPERSONATE_NAME is already enabled
11:52:32.243 [10368.2432] <16> set_sharepoint_impersonation: Login failed for user: with error 87.
11:52:32.243 [10368.2432] <4> ubs_GetSPSv2Topology: return code from ubsMapFarm is 00
11:52:32.243 [10368.2432] <4> ubs_GetSPSv2Topology: directive <Microsoft SharePoint Resources:\*> properly resolved
11:52:32.259 [10368.2432] <4> bpresolver_main(): INF - return code 0
11:52:32.259 [10368.2432] <4> bpresolver_main(): INF - EXIT STATUS 0