cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

full-diff restores of ms-sql database fails with 2809 status code

DavidE31
Level 4

‎12-27-2013 12:50 AM

Hello,

we are facing a problem with full-diff restores of ms-sql database using MOVE scripts

Master Server is W2008 R2 with NBU 7.5.0.6, media servers as well

MS-SQL server : sql server 2008 on Windows 2003 R2 64bit SP2 with NBU 7.5.0.6, netbackup MS-SQL client installed


Here are the steps to backup and restore databases :

- source and dest clients are the same
- in the MOVE script, database is renamed and restored to another volume disk of the same source server
- the backup script is placed in a MS-SQL policy with "Perform snapshot backups" activated (snapshot method "auto")


What happens :

- full + diff backups are OK
- the full restore job is OK, but the diff restore fails with 2809 status code
- the restored database stays in "Restoring ..." mode

What I have been able to check :

- recovery model of ms-sql database is SIMPLE (we do not backup/restore transaction logs)
- account used to run the backup is the account that start Netbackup client service. This is a domain account which is
local administrators of the sql client server
- permissions and roles on the ms-sql database are correct

It behaves as if once files are restored from the full backup, when we run the diff restore access to files are not OK
(the restore fails right from the start) but ACLs on the restored files seem to be correct (I set everyone/full control just
after the full restore in my second test to try and prevent the diff restore to fail, but this doesnt work)

Do you have an idea of how to fix the issue ?
Here is the MOVE script I used :

#   
#  This is a template for the database MOVE command.
#   
OPERATION RESTORE
OBJECTTYPE DATABASE
RESTORETYPE MOVE
#   
#  Replace the database name in the following line with the name of the database that you
#  want to move to. Also remove the hash mark <#> which precedes the keyword <DATABASE>.
#   
DATABASE "N_Portal_Site_Content_104"
#  
#  Replace the file path <S:\CONTENT101\local\sqlserver\data\VM370SEAR\Portal_Site_Content_104_1.mdf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "Portal_Site_Content_104_1".  
MOVE  "Portal_Site_Content_104_1"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_1.mdf"
#  
#  
#  Replace the file path <S:\CONTENT101\local\sqlserver\data\VM370SEAR\Portal_Site_Content_104_2.mdf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "Portal_Site_Content_104_2".  
MOVE  "Portal_Site_Content_104_2"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_2.mdf"
#  
#  
#  Replace the file path <S:\CONTENT101\local\sqlserver\data\VM370SEAR\Portal_Site_Content_104_3.mdf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "Portal_Site_Content_104_3".  
MOVE  "Portal_Site_Content_104_3"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_3.mdf"
#  
#  
#  Replace the file path <S:\CONTENT101\local\sqlserver\data\VM370SEAR\Portal_Site_Content_104_4.mdf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "Portal_Site_Content_104_4".  
MOVE  "Portal_Site_Content_104_4"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_4.mdf"
#  
#  
#  Replace the file path <N:\local\sqlserver\data\VM370SEAR\Portal_Site_Content_104_log.ldf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "Portal_Site_Content_104 _log".  
MOVE  "Portal_Site_Content_104 _log"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_log.ldf"
#  
# The following image is type: Full
NBIMAGE "fr0-ccssql-v02.MSSQL7.FR0-CCSSQL-V02\VM370SEAR.db.Portal_Site_Content_104.~.7.001of001.20131213205413..C"
SQLHOST "fr0-ccssql-v02"
SQLINSTANCE "VM370SEAR"
NBSERVER "FR0-SFSNBMA01"
BROWSECLIENT "fr0-ccssql-v02"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RESTOREOPTION REPLACE
BACKUPMODEL SNAPSHOT
RECOVEREDSTATE NOTRECOVERED
TRACELEVEL MAX
NUMBUFS 2
ENDOPER TRUE
 
OPERATION RESTORE
OBJECTTYPE DATABASE
DUMPOPTION INCREMENTAL
DATABASE "Portal_Site_Content_104"
# The following image is type: Full database differential
NBIMAGE "fr0-ccssql-v02.MSSQL7.FR0-CCSSQL-V02\VM370SEAR.inc.Portal_Site_Content_104.~.7.001of001.20131226151449..C"
SQLHOST "fr0-ccssql-v02"
SQLINSTANCE "VM370SEAR"
NBSERVER "FR0-SFSNBMA01"
BROWSECLIENT "fr0-ccssql-v02"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
RESTOREOPTION REPLACE
RECOVEREDSTATE RECOVERED
TRACELEVEL MAX
NUMBUFS 2
ENDOPER TRUE

20 REPLIES 20

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

‎12-27-2013 01:49 AM

by anychance did you see the check the below technote

http://www.symantec.com/business/support/index?page=content&id=TECH147036

0 Kudos

DavidE31
Level 4

‎12-27-2013 02:31 AM

Hello Nagalia,

 

thank you for the technote

NBU logs seem to reveal a problem with a virtual device he can't mount or access when doing the diff restore :

2/23/2013 6:17:24 PM - Info dbclient(pid=732) INF - Created VDI object for SQL Server instance <VM370SEAR>. Connection timeout is <300> seconds.
12/23/2013 6:17:47 PM - Info dbclient(pid=732) ERR - Error found executing <restore database "New_Portal_Site_Content_43" from VIRTUAL_DEVICE='VNBU0-732-1424-1387819044' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery>.

then

12/23/2013 6:17:57 PM - Info dbclient(pid=732) ERR - Error in DBthreads::dbclient: 6.       
12/23/2013 6:17:57 PM - Info dbclient(pid=732)     CONTINUATION: - The system cannot find the file specified

Is it possible to follow the way NBU create this Virtual_device when backing up, and mounting this device when restoring ?

I'm going to check again SQL server logs to see wether it's tracking this or not

 

0 Kudos

DavidE31
Level 4

‎12-27-2013 04:06 AM

Checked back from another restore that failed, on the SQL server I got some error in the Windows Events viewer such :

Event ID 18456 for the user account that runs the SQL Server and SQL Server Agent services, description : (...) Reason : Failed to open the explicitely specified database

-> not sure it's really a problem as these events appear for a long time, even during full snapshot backups of databases

But these one may help much as they were logged straight right when the diff backup ended with a 2908 status code :

Source : SQLVDI

Desc : Loc=TriggerAbort Instance : the SQL instance used to connect, VD=Global\VNBU0xxx -> the VNBU used for backup with the backup image ID

and another one SQLVDI Loc=SignalAbort Desc=Client initiates abort

 

0 Kudos

rookie11
Moderator
Moderator
   VIP   

‎01-01-2014 09:14 AM

please share complete script. I can see .mdf files new location but where is .ldf files location.

P:\local\TEMP_Restore\N_Portal_Site_Content_104_1.mdf, 

P:\local\TEMP_Restore\N_Portal_Site_Content_104_2.mdf, 

P:\local\TEMP_Restore\N_Portal_Site_Content_104_3.mdf, 

P:\local\TEMP_Restore\N_Portal_Site_Content_104_4.mdf and P:\local\TEMP_Restore\N_Portal_Site_Content_104_log.ldf. What about remaining .ldf files.

0 Kudos

DavidE31
Level 4

‎01-02-2014 12:46 AM

Hello rookie,

 

there is only one ldf file either in the script or in the server :

MOVE  "Portal_Site_Content_104 _log"
TO  "P:\local\TEMP_Restore\N_Portal_Site_Content_104_log.ldf"

0 Kudos

DavidE31
Level 4

‎01-03-2014 03:41 AM

Hello,

I have been able to create a very light database (recovery model simple, 3 tables with a few columns), and I can back it up and restore full/diff

I've checked properties of this database and compared them with databases I can't restore, I've seen no much difference between them. There is no matter of database size as another light database created a few times ago can't be restored as well.

I'm going to check log files for the successful / unsuccessful backups and try to find something that would tell me where is the problem

In the meantime,when I run the Netbackup SQL agent restore GUI, and select filter dates from Dec4 to today on the "Restore Microsoft SQL Server Objects", I can see some database backups with "*DATABASE IMAGE PLACEHOLDER*", except the one I created yesterday. Changing filters with start date to Nov29 drops this "*DATABASE IMAGE PLACEHOLDER*". I tried to run a full-diff backup image at Nov29 is still unscuccessful. I don't think there is any issue with this "*DATABASE IMAGE PLACEHOLDER*", but does anyone now what is this ?

 

Thank you

0 Kudos

quebek
Moderator
Moderator
   VIP    Certified

‎01-03-2014 04:18 AM

Do you have all backup images available for this restore??

Can you see all backups in this output: are the incremental there?

bpimagelist -client client-name -d Full-backup_date -U -pt MS-SQL-Server

### EDIT ###

Please also enable verbose logging by creating such folders on client, if not yet done:

install_path\NetBackup\logs\dbclient
install_path\NetBackup\logs\bpbkar (Snapshot Client)
install_path\NetBackup\logs\bpfis (Snapshot Client)
install_path\NetBackup\logs\bppfi (instant recovery)

 

To set the maximum trace level in the NetBackup SQL Client GUI
1 Open the NetBackup SQL Client.
2 Select File > Set NetBackup client properties.
3 In the Client Trace Level group, select Maximum.
To set the maximum trace level in the batch file
1 Open the NetBackup SQL Client.
2 Select File > Manage script files.
3 Select the batch file you want to change and click Open File.
4 Add the following line:
TRACELEVEL MAX
5 Save the file.

0 Kudos

DavidE31
Level 4

‎01-03-2014 04:59 AM

I can see all the full bacup images and there following diff backups for the client

I've created the log directories that were missing, set TRACELEVEL MAX on restore bch file and restarted Netbackup Client Service

Another restore is running now

0 Kudos

DavidE31
Level 4

‎01-03-2014 05:27 AM

bppfi didnot create anything

only dbclient logs are uptodate on the client

I don't know what extract from this log file may help

Here are some lines from this file :

(...)

13:58:53.648 [7492.6976] <4> ReadBatch: INF - <OPERATION> <RESTORE>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <OBJECTTYPE> <DATABASE>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <DUMPOPTION> <INCREMENTAL>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <RESTORETYPE> <MOVE>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <DATABASE> <N2_Portal_Site_Content_01>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <NBIMAGE> <fr0-ccssql-v02.MSSQL7.FR0-CCSSQL-V02\VM370SEAR.inc.Portal_Site_Content_01.~.7.001of001.20140103133045..C>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <SQLHOST> <fr0-ccssql-v02>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <SQLINSTANCE> <VM370SEAR>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <NBSERVER> <FR0-SFSNBMA01>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <BROWSECLIENT> <fr0-ccssql-v02>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <TRACELEVEL> <MAX>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <MAXTRANSFERSIZE> <6>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <BLOCKSIZE> <7>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <RESTOREOPTION> <REPLACE>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <RECOVEREDSTATE> <RECOVERED>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <NUMBUFS> <2>
13:58:53.648 [7492.6976] <4> ReadBatch: INF - <ENDOPER> <TRUE>
13:58:53.648 [7492.6976] <4> CGlobalInformation::SetCurrentHostInstance: INF - Current Host/Instance has been set to fr0-ccssql-v02/VM370SEAR
13:58:53.648 [7492.6976] <4> CGlobalInformation::GetCurrentHostInstance: INF - Current Host/Instance is fr0-ccssql-v02/VM370SEAR
13:58:53.648 [7492.6976] <4> CGlobalInformation::GetCurrentHostInstance: INF - Current Host/Instance is fr0-ccssql-v02/VM370SEAR
13:58:53.648 [7492.6976] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server>
13:58:53.648 [7492.6976] <4> CGlobalInformation::CreateDSN: INF - SQLConfigDataSource: SQL Server
13:58:53.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DSN=NBMSSQL_7492_6976_2
13:58:53.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DESCRIPTION=NetBackup MS SQL Server
13:58:53.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : SERVER=fr0-ccssql-v02\VM370SEAR
13:58:53.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : TRUSTED_CONNECTION=YES
13:58:53.664 [7492.6976] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7492_6976_2>, SQL userid <RES-V\SA-Q850-NBU> handle <0x01a23380>.
13:58:53.664 [7492.6976] <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <fr0-ccssql-v02\VM370SEAR> has been made using standard security with DSN <NBMSSQL_7492_6976_2>
13:58:53.664 [7492.6976] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x01a23380>
13:58:53.679 [7492.6976] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7492_6976_2>, SQL userid <RES-V\SA-Q850-NBU> handle <0x01a23380>.
13:58:53.679 [7492.6976] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x01a23380>
13:58:53.679 [7492.6976] <4> CDBMStype::SetDetailedType: INF - parsing SQL Server version 2008 (SP3) - 10.0.5500.0 (X64)

Sep 21 2011 22:45:45

Copyright (c) 1988-2008 Microsoft Corporation

Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)
13:58:53.679 [7492.6976] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7492_6976_2>, SQL userid <RES-V\SA-Q850-NBU> handle <0x01a23380>.
13:58:53.695 [7492.6976] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x01a23380>
13:58:53.695 [7492.6976] <4> CDBbackcat::GetVirtualServer: INF - Accessing database instance <fr0-ccssql-v02\VM370SEAR> on virtual server <fr0-ccssql-v02>.
13:58:54.804 [7492.4180] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_7492_6976_2>, SQL userid <RES-V\SA-Q850-NBU> handle <0x01a23380>.
13:58:54.820 [7492.4180] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x01a23380>
13:58:54.820 [7492.4180] <4> Dbbackrec::PerformNBOperation: INF - RESTORE STARTED USING

Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (X64)

Sep 21 2011 22:45:45

Copyright (c) 1988-2008 Microsoft Corporation

Enterprise Edition (64-bit) on Windows NT 5.2 <X64> (Build 3790: Service Pack 2)

Batch = D:\Program Files\Veritas\NetBackup\DbExt\MsSql\Resto_Content_01_03jan.bch, Op# = 2.

(...)

13:59:10.773 [7492.6024] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO fr0-sfsnbma01 10.122.1.91 bprd VIA pbx
13:59:10.773 [7492.6024] <2> logconnections: BPRD CONNECT FROM 10.122.3.141.4831 TO 10.122.1.91.1556 fd = 880
13:59:10.773 [7492.6024] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
13:59:12.336 [7492.4180] <16> Dbbackrec::PerformNBOperation: ERR - Error found executing <restore database "N2_Portal_Site_Content_01" from VIRTUAL_DEVICE='VNBU0-7492-4180-1388753934' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery>.
13:59:12.336 [7492.4180] <4> VxBSALogJobInfo: INF - entering VxBSALOgJobInfo.

(...)

13:59:12.336 [7492.4180] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
13:59:12.398 [7492.4180] <4> KillAllThreads: INF - entering KillAllThreads <2>
13:59:12.398 [7492.4180] <4> KillAllThreads: INF - Killing group #0
13:59:12.398 [7492.4180] <4> KillAllThreads: INF - Issuing SignalAbort to MS SQL Server VDI
13:59:12.398 [7492.4136] <4> DBthreads::dbprocessbufs: INF - DBBUFPROCESS ENDED. NumClientIOs 3. Total Client Bytes 196608, NumLoops 54
13:59:12.398 [7492.7108] <16> DBthreads::dbclient: ERR - Internal error. See the dbclient log for more information.
13:59:12.398 [7492.4136] <4> KillAllThreads: INF - entering KillAllThreads <2>
13:59:12.398 [7492.7108] <4> VxBSALogJobInfo: INF - entering VxBSALOgJobInfo.
13:59:12.398 [7492.4136] <4> KillAllThreads: INF - Killing group #0

(...)

13:59:12.398 [7492.4180] <2> do_pbx_service: [vnet_connect.c:2116] via PBX bprd CONNECT FROM 10.122.3.141.4836 TO 10.122.1.91.1556 fd = 612
13:59:12.398 [7492.4180] <2> async_connect: [vnet_connect.c:1644] connect async CONNECT FROM 10.122.3.141.4836 TO 10.122.1.91.1556 fd = 612
13:59:12.398 [7492.4180] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO FR0-SFSNBMA01 10.122.1.91 bprd VIA pbx
13:59:12.398 [7492.4180] <2> logconnections: BPRD CONNECT FROM 10.122.3.141.4836 TO 10.122.1.91.1556 fd = 612
13:59:12.398 [7492.4180] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
13:59:12.461 [7492.7108] <32> DBthreads::dbclient: ERR - Bad client VxBSAstatus 1 for pipe #0.
13:59:12.461 [7492.4180] <1> CDBbackrec::FreeDeviceSet():     CONTINUATION: - An abort request is preventing anything except termination actions.
13:59:12.461 [7492.4180] <4> VxBSALogJobInfo: INF - entering VxBSALOgJobInfo.

(...)

13:59:12.523 [7492.4180] <4> Dbbackrec::Perform: INF - OPERATION #2 of batch D:\Program Files\Veritas\NetBackup\DbExt\MsSql\Resto_Content_01_03jan.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 19(19) seconds.
13:59:12.523 [7492.4180] <4> VxBSALogJobInfo: INF - entering VxBSALOgJobInfo.
13:59:12.523 [7492.4180] <4> getOwnerName: entering getOwnerName.

(...)

13:59:22.976 [7492.7108] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO FR0-SFSNBMA01 10.122.1.91 bprd VIA pbx
13:59:22.976 [7492.7108] <2> logconnections: BPRD CONNECT FROM 10.122.3.141.4846 TO 10.122.1.91.1556 fd = 820
13:59:22.976 [7492.7108] <2> vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:843] Assuming no VxSS for DB Agents 0 0x0
13:59:23.039 [7492.7108] <1> DBthreads::dbclient:     CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid.
13:59:23.039 [7492.7108] <4> VxBSALogJobInfo: INF - entering VxBSALOgJobInfo.

(...)

13:59:34.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DSN=NBMSSQL_7492_6976_1
13:59:34.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : SERVER=fr0-ccssql-v02\VM370SEAR
13:59:34.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DESCRIPTION=NetBackup MS SQL Server
13:59:34.648 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : TRUSTED_CONNECTION=YES
13:59:34.648 [7492.6976] <4> CGlobalInformation::DeleteDSN: INF - Using ODBC Driver <SQL Server>
13:59:34.679 [7492.6976] <2> CGlobalInformation::DeleteDSN: DBG - removed dsn DSN=NBMSSQL_7492_6976_1
13:59:34.679 [7492.6976] <4> CGlobalInformation::DeleteDSN: INF - SQLConfigDataSource:
13:59:34.679 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DSN=NBMSSQL_7492_6976_2
13:59:34.679 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : SERVER=fr0-ccssql-v02\VM370SEAR
13:59:34.679 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : DESCRIPTION=NetBackup MS SQL Server
13:59:34.679 [7492.6976] <4> CGlobalInformation::LogODBCAttributes: INF - SQLConfigDataSource keyword-value pair : TRUSTED_CONNECTION=YES
13:59:34.679 [7492.6976] <4> CGlobalInformation::DeleteDSN: INF - Using ODBC Driver <SQL Server>
13:59:34.679 [7492.6976] <2> CGlobalInformation::DeleteDSN: DBG - removed dsn DSN=NBMSSQL_7492_6976_2
13:59:34.679 [7492.6976] <2> CGlobalInformation::DeleteDSNInfoList: DBG - Exiting
13:59:34.679 [7492.6976] <4> VxBSATerminate: INF - entering VxBSATerminate.
13:59:34.679 [7492.6976] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_DEBUGFD
13:59:34.679 [7492.6976] <4> VxBSAGetEnv: INF - returning -
 

 

 

 

0 Kudos

quebek
Moderator
Moderator
   VIP    Certified

‎01-03-2014 06:13 AM

any entires where in the third column you will find <8>, <16> or <32> - these are errors... can you filter those files for such entires?

0 Kudos

DavidE31
Level 4

‎01-05-2014 02:48 AM

Hello quebek

here is the dbclient file filtered :

13:59:03.851    [7492.7108]    <8>    vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1585] in failed file cache ERR=10109 NAME=NULL SVC=testdaemon
13:59:03.851    [7492.7108]    <8>    vnet_cached_get_service_port: [vnet_addrinfo.c:2396] vnet_cached_getaddrinfo failed STAT=6 RV=10109 NAME=testdaemon
13:59:03.851    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2159] vnet_cached_get_service_port() failed 6 0x6
13:59:03.851    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2160] service 4818
13:59:03.851    [7492.7108]    <8>    file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\14f\6cf9fd4f+4818,1,400,2,1,0+127.0.0.1.txt
13:59:03.851    [7492.7108]    <8>    verify_hashes: [vnet_vnetd.c:1641] hash_str 5280f2a7075cb20ffdc76ca3ff2440dd
13:59:03.867    [7492.7108]    <8>    vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1532] in failed cache ERR=10109 NAME=NULL SVC=testdaemon
13:59:03.867    [7492.7108]    <8>    vnet_cached_get_service_port: [vnet_addrinfo.c:2396] vnet_cached_getaddrinfo failed STAT=6 RV=10109 NAME=testdaemon
13:59:03.867    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2159] vnet_cached_get_service_port() failed 6 0x6
13:59:03.867    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2160] service 4819
13:59:03.867    [7492.7108]    <8>    file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\14f\6cf9fd4f+4819,1,400,2,1,0+127.0.0.1.txt
13:59:03.882    [7492.7108]    <8>    verify_hashes: [vnet_vnetd.c:1641] hash_str e495baf4dc1c21b7b199ce324b636803
13:59:12.336    [7492.4180]    <16    > Dbbackrec::PerformNBOperation: ERR - Error found executing <restore database "N2_Portal_Site_Content_01" from VIRTUAL_DEVICE='VNBU0-7492-4180-1388753934' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery>.
13:59:12.398    [7492.7108]    <16    > DBthreads::dbclient: ERR - Internal error. See the dbclient log for more information.
13:59:12.398    [7492.4180]    <16    > CDBbackrec::FreeDeviceSet(): ERR - Error in VDS->Close: 0x80770004.
13:59:12.461    [7492.7108]    <32    > DBthreads::dbclient: ERR - Bad client VxBSAstatus 1 for pipe #0.
13:59:12.601    [7492.6024]    <16    > WriteToVirtualDevice: ERR - Error in GetCommand: 0x80770004.
13:59:22.460    [7492.7108]    <8>    close_image: Session being terminated abnormally, cleaning up
13:59:22.804    [7492.7108]    <16    > CDBbackrec::ClientStatus: ERR - Internal error. See the dbclient log for more information.
13:59:22.851    [7492.7108]    <32    > CDBbackrec::ClientStatus: ERR - Failed to get the client status because no BSA transaction is active.
13:59:22.851    [7492.7108]    <16    > CDBbackrec::ProcessVxBSAerror: ERR - Error in DBthreads::dbclient: 6.
13:59:22.976    [7492.7108]    <16    > DBthreads::dbclient: ERR - Error in VxBSAEndData: 6.

 

bpfis log file :

13:25:26.474    [5648.5192]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:25:26.756    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:25:26.756    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:25:26.756    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:25:26.756    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:25:26.756    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:25:26.771    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:25:26.771    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:25:26.771    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:25:26.771    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:25:26.771    [5648.5192]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:25:26.881    [5648.5192]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:25:30.349    [5648.5192]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:25:33.115    [5648.5192]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:25:33.240    [5648.5192]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:27.083    [7596.5508]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:27.645    [7596.5508]    <16    > bprd_isJobActive: get_bprdESwto(528, 330) failed, no entity was found (227)        
13:26:27.661    [7596.5508]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:27.755    [7596.5508]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:26:28.020    [7596.5508]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:26:28.052    [7596.5508]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:28.724    [7596.5508]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:37.270    [6356.6876]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:26:37.520    [6356.6876]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:26:37.536    [6356.6876]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:38.005    [6356.6876]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:40.161    [6356.6876]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:26:40.286    [6356.6876]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:34.098    [5916.656]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:34.176    [5916.656]    <16>    bprd_isJobActive: get_bprdESwto(528, 330) failed, no entity was found (227)        
13:27:34.176    [5916.656]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:34.285    [5916.656]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:27:34.535    [5916.656]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:27:34.551    [5916.656]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:35.066    [5916.656]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:42.941    [7852.6852]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:27:43.191    [7852.6852]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:27:43.207    [7852.6852]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:43.629    [7852.6852]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:45.676    [7852.6852]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:27:45.801    [7852.6852]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:39.581    [5492.6884]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:39.675    [5492.6884]    <16    > bprd_isJobActive: get_bprdESwto(528, 330) failed, no entity was found (227)        
13:28:39.675    [5492.6884]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:39.769    [5492.6884]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:28:40.050    [5492.6884]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:28:40.066    [5492.6884]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:40.644    [5492.6884]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:48.472    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:28:48.753    [8108.5440]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:28:48.784    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:49.253    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:49.347    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:49.440    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:53.722    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:53.815    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:28:53.956    [8108.5440]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:29:42.830    [6476.8076]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:29:42.909    [6476.8076]    <16    > bprd_isJobActive: get_bprdESwto(532, 330) failed, no entity was found (227)        
13:29:42.909    [6476.8076]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:29:43.002    [6476.8076]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: FlashSnap, type: FIM, function: FlashSnap_init        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - FlashSnap_init: Veritas Volume Manager not installed.        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - VfMS error 10; see following messages:        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - Non-fatal method error was reported        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - vfm_configure_fi_one: method: vxvm, type: FIM, function: vxvm_init        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - VfMS method error 3; see following message:        
13:29:43.252    [6476.8076]    <8>    onlfi_initialize_vfms: WRN - vxvm_init: Veritas Volume Manager not installed.        
13:29:43.268    [6476.8076]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2        
13:29:43.815    [6476.8076]    <8>    vnet_check_vxss_client_magic_with_info: [vnet_vxss_helper.c:871] Ignoring VxSS authentication 2 0x2

 

0 Kudos

quebek
Moderator
Moderator
   VIP    Certified

‎01-05-2014 08:39 AM

Hi bpfis has nothing interesting...

not sure but these entries

13:59:03.851    [7492.7108]    <8>    vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1585] in failed file cache ERR=10109 NAME=NULL SVC=testdaemon
13:59:03.851    [7492.7108]    <8>    vnet_cached_get_service_port: [vnet_addrinfo.c:2396] vnet_cached_getaddrinfo failed STAT=6 RV=10109 NAME=testdaemon
13:59:03.851    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2159] vnet_cached_get_service_port() failed 6 0x6
13:59:03.851    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2160] service 4818
13:59:03.851    [7492.7108]    <8>    file_to_cache_item: [vnet_addrinfo.c:6574] fopen() failed ERRNO=2 FILE=D:\Program Files\Veritas\NetBackup\var\host_cache\14f\6cf9fd4f+4818,1,400,2,1,0+127.0.0.1.txt
13:59:03.851    [7492.7108]    <8>    verify_hashes: [vnet_vnetd.c:1641] hash_str 5280f2a7075cb20ffdc76ca3ff2440dd
13:59:03.867    [7492.7108]    <8>    vnet_cached_getaddrinfo_and_update: [vnet_addrinfo.c:1532] in failed cache ERR=10109 NAME=NULL SVC=testdaemon
13:59:03.867    [7492.7108]    <8>    vnet_cached_get_service_port: [vnet_addrinfo.c:2396] vnet_cached_getaddrinfo failed STAT=6 RV=10109 NAME=testdaemon
13:59:03.867    [7492.7108]    <8>    is_pbxable_service: [vnet_connect.c:2159] vnet_cached_get_service_port() failed 6 0x6

are telling me to check the name resolution...

can you please check the master and client communication with bpclntcmd command?

Also if you don't mind to upload full logs from dbclient, tar, bpcd as attachements.

I would also try to restore this DB to original place but to a different client - if this is doable try that...

0 Kudos

DavidE31
Level 4

‎01-06-2014 01:49 AM

Hello,

I will post full logs asap

Regarding the master/client communication, as I have been able to make successful tests with a small database I have created, I don't think there are communications problems.

Moreover, we already have made restore tests from one client to another, we get the same restore errors

 

Thanks

0 Kudos

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

‎01-06-2014 04:37 AM

Hi,

 

Have you tried with NUMBUFS 1, and also, have you tried to first restore the full (unrecovered), then restore the diff after?

 

 

0 Kudos

DavidE31
Level 4

‎01-06-2014 05:32 AM

Hi Riaa,

I've set NUMBUFS to 1 for both full and diff restore, I get the same problem (database stays in "restoring..." status and mdf file size is downed to 0)

I'll try a full unrecovered then a diff in few minutes, even if it seems to me the test has already be done before by someone else in the team I work in

0 Kudos

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

‎01-06-2014 05:39 AM

Reason I say that is because the backups types for Full and Diff are different. Full can occur with snapshot, and Diff cannot, it reverts to a stream backup. So that might cause something funny if you try restore them together?

0 Kudos

DavidE31
Level 4

‎01-16-2014 12:23 AM

restoring a diff backup in RECOVERED mode after having restored a successful FULL with NOT RECOVERED mode doesnt work as well

Symantec support asked us to try and disable our antivirus on the client (McAfee VSE) temporarly for a full/diff restore. Have you ever heard about antivirus that could prevent a diff restore to complete ?

 

As today, antivirus disabled doesnt fix the issue.

There may be a problem with Instant File Initialization, not sure ...

Anyway, enabling and disabling IFI doesn't make our restores work

0 Kudos

DavidE31
Level 4

‎01-22-2014 02:10 AM

Hello all,

here is an update on this problem

Restoring full/diff backups with MOVE script is still not possible.

But when a copy an existing database to a new one using MS SQL management studio, on the same instance, and then I full back it up, create a new table, diff back it up, I can full/diff restore using a MOVE script from new backup sets done.

I don't know what this let suggests ? the only difference between the copied database and the original one is the database ID and therefore the name of this database ...

A call will be open to Microsoft Support

0 Kudos

DavidE31
Level 4

‎02-21-2014 03:36 AM

Hello,

I have news on this problem

I could successfully make full/diff restores using MOVE scripts of databases

What I've done is :

- creating new policy for backup not using MSDP storage pool but a basic disk pointing to a local disk

- configuring policy to NOT perform backup as snapshot

What do you think of this ?

Thanks

0 Kudos