Forum Discussion
Merv
14 years agoLevel 6
No that my production env is working more or less - i found out I had to enter FQDN hostnames in my hosts file as my backup server is not properly using DNS, but i still have an error 42 on some files on my index server.
9/14/2010 23:21:36 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\Global Settings (index)\Global Settings (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:06 - Error bptm (pid=29906) system call failed - Connection reset by peer (at child.c.1296)
09/14/2010 23:23:06 - Error bptm (pid=29906) unable to perform read from client socket, connection may have been broken
09/14/2010 23:23:06 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\RegistryBlob.reg (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:06 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:06 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config\noiseara.txt (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:06 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config\noiseben.txt (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:07 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config\noisebul.txt (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:07 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config\noisecat.txt (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
09/14/2010 23:23:07 - Warning bpbrm (pid=29894) from client frontend: WRN - can't open object: Microsoft SharePoint Resources:\SharedServices\Shared Search Index\Index files 1 (indexserver/334811bd-31d9-4cbb-a43a-02c8d4850bdc)\Config\noisechs.txt (BEDS 0xE000FEA9: The Backup Exec data store encountered a problem during the operation. See the job log for details.)
GRT also fails with a error 130 - snapshot error...i'm stumped..it cannot freeze the DB's for some reason..
On my test environment GRT is also not working properly
getting below errors:
Begin writing
09/11/2010 21:56:03 - Error bpbrm (pid=6843) from client frontendtest: ERR - Error encountered while attempting to get additional files for Microsoft SharePoint Resources:\WSS_Administration\WebApplication\Content-DB 1 (backendserver/SharePoint_AdminContent_2cea52c4-c864-46f4-95f1-47c09a1070cc)\_Granular_Devices_
09/11/2010 21:56:09 - end writing; write time: 3:50:51
the requested operation was partially successful (1)
For error 42:
make sure you enable bpresolver,beds,bpbkar,bpcd and in my case with the snapshot error when doing GRT - bpfis.
Also check that you can connect on(using telnet) bpcd/vnetd ports between frontend and backend both ways..and also the rpc ports i mentioned earlier.
you can use bpclntcmd -pn ,bplcntcmd -hn,bpclntcmd - ip to check through all the connectivity but bpresolver logs should show some errors.
Related Content
- 2 years ago
- 3 months ago
- 13 years ago
- 5 months ago