01-22-2016 06:49 AM
I have a problem running sharepoint backup.
Error 69, invalid filelist specification.
I followed all the steps of the guide;
I checked everything: https://www.veritas.com/support/en_US/article.HOWTO73100
Could you please help me solve this problem?
Solved! Go to Solution.
02-22-2016 07:20 AM
oh sorry, start over
send_start_msg(): BPRESOLVER has executed on server (EPM2013WEBDES)
...
getaddrinfo() failed RV=10109 NAME=EPM2013WEBDES SVC=bpspsserver
===========
EPM2013WEBDES is not the same thing as vm25145_epm2013webdes
01-22-2016 07:04 AM
another technote to check
https://www.veritas.com/support/en_US/article.000021121
01-22-2016 08:16 AM
I checked all these techs;
Disabling granular recovery has error 71, "(71) none of the files in the file list exist"
https://www.veritas.com/support/en_US/article.TECH215772
https://www.veritas.com/support/en_US/article.TECH203759
http://www.symantec.com/connect/blogs/sharepoint-backups-fail-status-71
https://www.veritas.com/support/en_US/article.000021005
https://www.veritas.com/support/en_US/article.000020044
https://www.veritas.com/support/en_US/article.TECH202327
https://www.veritas.com/support/en_US/article.TECH124810
01-22-2016 10:57 AM
This may help:
https://www.veritas.com/community/downloads/sharepointcheckexe-configuration-checker
01-24-2016 01:57 AM
Too few details.. OS & NBU version? How does your job details look like and what is the policy details (bppllist <sharepoint_policy> -L) ?
02-18-2016 04:45 AM
Hi sdo,
following the result of the sharepoint_check:
========================================
Initializing NBU Sharepoint Agent Configuration Check.
Checking for status of NFS Service - It is needed for granular backup and restore
Client for NFS service is installed and Running.
Checking for account credentials for Netbackup Client Service
The Netbackup Client Service on host vm25145_epm2013webdes is running as : epm2013d_FARMAdmin@d02.prodemge.gov.br
Checking Host Porperties for this client - vm25145_epm2013webdes
Host Properties for host vm25145_epm2013webdes is set as : d02-prodemge\epm2013d_FARMAdmin
Checking for SharePoint version compatibility With .net framework version
SharePoint 2013 is installed on this machine, version : 15.0.4569.1506
Looking for minimum required .net version (4.0)
Minimum required .net version is installed
Checking for Replace Process Level Token privilege for account - d02-prodemge\epm2013d_FARMAdmin.
Replace a Process Level Token : ENABLED
Checking for Debug Programs privilege for account - d02-prodemge\epm2013d_FARMAdmin.
Debug Programs : ENABLED
Checking for Publisher's Certificate Revocation in Internet Explorer.
Publisher's Certificate Revocation is : UNCHECKED
Checking for Server Certificate Revocation in Internet Explorer.
Server Certificate Revocation is : UNCHECKED
NBU Sharepoint Agent Configuration Check Complete.
========================================
02-18-2016 04:47 AM
Hi watsons,
follows the policy:
[root@sn02001-bkp admincmd]# bppllist P_WIN_SHP_D -L
Policy Name: P_WIN_SHP_D
Options: 0x0
template: FALSE
audit_reason: ?
Names: (none)
Policy Type: MS-SharePoint (8)
Active: yes
Effective date: 11/19/2015 15:58:23
Mult. Data Stream: no
Perform Snapshot Backup: no
Snapshot Method: (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup: no
Backup Copy: 0
Use Data Mover: no
Data Mover Type: -1
Use Alternate Client: no
Alternate Client Name: (none)
Use Virtual Machine: 0
Hyper-V Server Name: (none)
Enable Instant Recovery: no
Policy Priority: 0
Max Jobs/Policy: Unlimited
Disaster Recovery: 0
Collect BMR Info: no
Keyword: (none specified)
Data Classification: -
Residence is Storage Lifecycle Policy: no
Client Encrypt: no
Checkpoint: no
Residence: sn06003-bkp_disk_staging
Volume Pool: Pool_FS
Server Group: PRODEMGE
Granular Restore Info: yes
Exchange Source attributes: no
Exchange DAG Preferred Server: (none defined)
Application Discovery: no
Discovery Lifetime: 0 seconds
ASC Application and attributes: (none defined)
Generation: 154
Ignore Client Direct: no
Use Accelerator: no
Client/HW/OS/Pri/CIT: vm25145_epm2013webdes Windows-x64 Windows 0 0 0 ?
Include: Microsoft SharePoint Resources:\AllWebs
Schedule: Full
Type: FULL SSharePoint Portal (0)
Calendar sched: Enabled
Included Dates-----------
No days of week entered
Excluded Dates----------
No specific exclude dates entered
No exclude days of week entered
Retention Level: 20 (4 hours)
u-wind/o/d: 0 0
Incr Type: DELTA (0)
Alt Read Host: (none defined)
Max Frag Size: 0 MB
PFI Recovery: 0
Maximum MPX: 1
Number Copies: 1
Fail on Error: 0
Residence: (specific storage unit not required)
Volume Pool: (same as policy volume pool)
Server Group: (same as specified for policy)
Residence is Storage Lifecycle Policy: 0
Daily Windows:
Day Open Close W-Open W-Close
Sunday 000:00:00 000:00:00
Monday 000:00:00 000:00:00
Tuesday 000:00:00 000:00:00
Wednesday 000:00:00 000:00:00
Thursday 000:00:00 000:00:00
Friday 000:00:00 000:00:00
Saturday 000:00:00 000:00:00
02-18-2016 04:55 AM
yet the error.
see the job details up:
18/02/2016 10:32:54 - Info nbjm (pid=3314) starting backup job (jobid=1096646) for client vm25145_epm2013webdes, policy P_WIN_SHP_D, schedule Full
18/02/2016 10:32:54 - Info nbjm (pid=3314) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1096646, request id:{BB9F85F8-D63B-11E5-AB9F-05565D36C938})
18/02/2016 10:32:54 - requesting resource sn06003-bkp_disk_staging
18/02/2016 10:32:54 - requesting resource sn02001-bkp.NBU_CLIENT.MAXJOBS.vm25145_epm2013webdes
18/02/2016 10:32:54 - requesting resource sn02001-bkp.NBU_POLICY.MAXJOBS.P_WIN_SHP_D
18/02/2016 10:32:54 - granted resource sn02001-bkp.NBU_CLIENT.MAXJOBS.vm25145_epm2013webdes
18/02/2016 10:32:54 - granted resource sn02001-bkp.NBU_POLICY.MAXJOBS.P_WIN_SHP_D
18/02/2016 10:32:54 - granted resource MediaID=@aaaa9;DiskVolume=/nbu;DiskPool=sn06003-bkp_disk_staging;Path=/nbu;StorageServer=sn06003-bkp;MediaServer=sn06003-bkp
18/02/2016 10:32:54 - granted resource sn06003-bkp_disk_staging
18/02/2016 10:32:54 - estimated 0 kbytes needed
18/02/2016 10:32:54 - begin Parent Job
18/02/2016 10:32:54 - begin Sharepoint Granular Resolver: Start Notify Script
18/02/2016 10:32:54 - Info RUNCMD (pid=46129) started
18/02/2016 10:32:54 - Info RUNCMD (pid=46129) exiting with status: 0
Operation Status: 0
18/02/2016 10:32:54 - end Sharepoint Granular Resolver: Start Notify Script; elapsed time 0:00:00
18/02/2016 10:32:54 - begin Sharepoint Granular Resolver: Step By Condition
Operation Status: 0
18/02/2016 10:32:54 - end Sharepoint Granular Resolver: Step By Condition; elapsed time 0:00:00
18/02/2016 10:32:54 - begin Sharepoint Granular Resolver: Read File List
Operation Status: 0
18/02/2016 10:32:54 - end Sharepoint Granular Resolver: Read File List; elapsed time 0:00:00
18/02/2016 10:32:54 - begin Sharepoint Granular Resolver: Resolver Discovery
18/02/2016 10:32:55 - started process bpbrm (pid=18974)
18/02/2016 10:32:55 - Info bpbrm (pid=18974) vm25145_epm2013webdes is the host to restore to
18/02/2016 10:32:55 - Info bpbrm (pid=18974) reading file list for client
18/02/2016 10:32:56 - Info bpresolver (pid=10488) start
18/02/2016 10:32:56 - Info bpbrm (pid=18974) from client vm25145_epm2013webdes: TRV - BPRESOLVER has executed on server (EPM2013WEBDES)
18/02/2016 10:33:04 - Info bpresolver (pid=10488) done. status: 0
18/02/2016 10:33:04 - Info bpresolver (pid=10488) done. status: 0: the requested operation was successfully completed
Operation Status: 0
18/02/2016 10:33:04 - end Sharepoint Granular Resolver: Resolver Discovery; elapsed time 0:00:10
18/02/2016 10:33:04 - begin Sharepoint Granular Resolver: Policy Execution Manager Preprocessed
Operation Status: 69
18/02/2016 10:33:12 - end Sharepoint Granular Resolver: Policy Execution Manager Preprocessed; elapsed time 0:00:08
18/02/2016 10:33:12 - begin Sharepoint Granular Resolver: Stop On Error
Operation Status: 0
18/02/2016 10:33:12 - end Sharepoint Granular Resolver: Stop On Error; elapsed time 0:00:00
18/02/2016 10:33:12 - begin Sharepoint Granular Resolver: End Notify Script
18/02/2016 10:33:12 - Info RUNCMD (pid=47515) started
18/02/2016 10:33:12 - Info RUNCMD (pid=47515) exiting with status: 0
Operation Status: 0
18/02/2016 10:33:12 - end Sharepoint Granular Resolver: End Notify Script; elapsed time 0:00:00
Operation Status: 69
18/02/2016 10:33:12 - end Parent Job; elapsed time 0:00:18
invalid filelist specification (69)
02-18-2016 05:07 AM
Create the NetBackup "bpresolver" log folder on the client. Set the NetBackup client logging to level 5. Restart NetBackup Client services. Re-run backup. Check "bpresolver" log.
02-18-2016 05:24 AM
see if you can identify a problem!!!
02-18-2016 05:26 AM
Master Server NBU: RedHat, Netbackup 7.7.1
SharePoint 2013, Windows2012
02-18-2016 05:31 AM
I did!
# egrep -i "<16>|fail|error|seve|criti" ALL_ADMINS.021816_00001.log | egrep -v "\ INF\ -\ "
02-18-2016 06:14 AM
<16> db_begin: db_startrequest() failed: operation requested by an invalid server
Is sn02001-bkp in vm25145_epm2013webdes SERVER list ?
02-18-2016 11:34 AM
Will Restore,
sn02001-bkp is master server Netbackup
vm25145_epm2013webdes is front end Share Point
* vm25145_epm2013webdes performs backup of other types successful.
02-18-2016 11:50 AM
Understood. You still have to add the Master to the client's Server list.
02-19-2016 04:45 AM
already, always.
As I said:
performs backup of other types successful.
02-22-2016 05:39 AM
Odd. Check ouput of these commands on the client
bpclntcmd -pn
bpclntcmd -hn sn02001-bkp
bpclntcmd -ip <master server ip>
02-22-2016 07:20 AM
oh sorry, start over
send_start_msg(): BPRESOLVER has executed on server (EPM2013WEBDES)
...
getaddrinfo() failed RV=10109 NAME=EPM2013WEBDES SVC=bpspsserver
===========
EPM2013WEBDES is not the same thing as vm25145_epm2013webdes
02-22-2016 08:33 AM
@Heron - we haven't heard from you for a few days...
What myself (with the command I gave you above), and Will, are trying to do is to steer you towards learning how to identify "naming" issues for yourself. Or, do you still need a hand going through this in minute low level detail? We could give you a process which will identify any naming issues (if you understand the output), and if you are still unable to resolve it yourself, then you would need to show us undoctored output of commands, if any one of us are to help you any further.
You clearly have a server and/or client naming issue, so it's it to you how you want to progress this. What do you want to do next?
03-04-2016 08:13 AM
Resolved friends !!!
Look:
I have a specific Ethernet network for backup.
Do not use DNS for that network, so I set the hosts file of each server, and the master server as well.
For error 69: reconfigured hosts files, Master Server and Sharepoint, using its hostname.
And for error 71: set up the properties of the default clients (with anything)
thank you guys