How restore SQL database to different server?
Hello! We used Netbackup 7.6.1 With scripts .bch has been configured Full online backup SQL database which succeeds. Recovery with .bch is also successful, but only on the same server. (in mode "recovered" and "not recovered" (.mdb,.ldb)) How to set up a database restore to a different server? I have tried to make these instructions: Recovery is initiated on the master server Redirecting a SQL restore to a different host Multiple NetBackup database clients can be configured to use a single NetBackup master server for backing up SQL Server databases. With this configuration, you can back up SQL Server database objects from one client and restore them to another. In the following procedure, HostA is the client that was originally backed up and HostB is the other client to which the restore is redirected. To redirect a restore to a different host 1 Establish permission settings on the master server. Do one of the following: ■ Create a install_path\NetBackup\db\altnames\No.Restrictions file to allow unrestricted redirected restore privileges. ■ Create a install_path\NetBackup\db\altnames\HostB file to allow HostB to restore HostA's data. The client named HostB can then access HostA's data on the master as well as any other client's data that was backed up on the master. 2 Select File > SetSQLServerconnectionproperties. 3 Log onto the target instance on HostB. 4 Select File > SetNetBackupclientpropertiesand select the current master server to be a master server that is common to both HostA and HostB. 5 Select File > RestoreSQLServerobjects. 6 From the Backup History Options dialog box, select HostA as the SQL host from which the target objects were backed up. When the restore window appears it contains a history of objects that were backed up from HostA. Select those objects and restore them to HostB. In this scenario, I get an error ERR - Error in CoCreateInstance: 0x80040154. and Recovery is initiated on the client server which was backuped https://support.symantec.com/en_US/article.TECH35995.html Here is an example with the option "not recovered" HostA - source client HostB - destination client # # 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 "123" # # Replace the file path <E:\SQLData\PortalDBs\WSS_videocam.mdf> # with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>. # The target of the MOVE keyword must be "WSS_videocam". MOVE "WSS_videocam" TO "E:\123.mdf" # # # Replace the file path <E:\SQLData\PortalDBs\WSS_videocam_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 "WSS_videocam_log". MOVE "WSS_videocam_log" TO "E:\123_log.LDF" # # The following image is type: Full NBIMAGE "HostA.MSSQL7.HOSTA.db.WSS_videocam.~.7.001of001.20150430110244..C" SQLHOST "HostB" NBSERVER "HostM" BROWSECLIENT "HostA" MAXTRANSFERSIZE 6 BLOCKSIZE 7 RESTOREOPTION REPLACE RECOVEREDSTATE NOTRECOVERED SQLCOMPRESSION TRUE NUMBUFS 2 ENDOPER TRUE INF - RESTORE STARTED USING Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64) Jun 28 2012 08:36:30 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor) Batch = C:\test.bch, Op# = 1. INF - Using backup image HostA.MSSQL7.HOSTA.db.WSS_videocam.~.7.001of001.20150430110244..C INF - restore database "123" from VIRTUAL_DEVICE='VNBU0-6740-6876-1430400456' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery, move 'WSS_videocam' to 'E:\123.mdf', move 'WSS_videocam_log' to 'E:\123_log.LDF', replace INF - Number of stripes: 1, Number of buffers per stripe 2. INF - Created VDI object for SQL Server instance <HostB>. Connection timeout is <300> seconds. ERR - Error in GetConfiguration: 0x80770003. CONTINUATION: - The api was waiting and the timeout interval had elapsed. DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3201><[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device 'VNBU0-6740-6876-1430400456'. Operating system error 0x80070002(failed to retrieve text for this error. Reason: 15105).>. DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.> ERR - Error found executing <restore database "123" from VIRTUAL_DEVICE='VNBU0-6740-6876-1430400456' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery, move 'WSS_videocam' to 'E:\123.mdf', move 'WSS_videocam_log' to 'E:\123_log.LDF', replace>. INF - OPERATION #1 of batch C:\test.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 304(304) seconds. INF - Results of executing <C:\test.bch>: <0> operations succeeded. <1> operations failed. As now all I fix this? I already read a lot of topics on the forum and admin guide, but nothing happens... Is it possible to perform a recovery exclusively on the master server in case the server is physically damaged power? Thanks in advance.Solved16KViews0likes18CommentsUnable to set SQL Server Connection Properties for specific client
Hi everyone, I've been dealing with this issue without any solution until this moment. I'm trying to configure a SQL client with NetBackup but the more curious thing for me is that when I start the NetBackup Database Extension, it only shows me a host name in the combo box but not the real name of the client that I am connecting to but another server in the same network which hasn't installed neither NetBackup nor SQL Server. For example it shows only server name VOLCANO01 but the local server name and the one that I need to setup is VOLCANO09. When I try to apply settings after typing the correct name of the server and giving the credentials it shows me the common error: "Application connection failed for VOLCANO09\. Please select a different SQL Server host and instance, or press 'cancel' to exit the NetBackup for SQL Server Graphical User Interface.". Setting the logs in verbose this is the detail 15:43:01.325 [3152.3376] <4> VxBSAInit: Veritas NetBackup XBSA Interface - 7.6 0 15:43:01.325 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_API 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_FEATURE_ID 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - <FEATURE_ID> 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01 15:43:01.326 [3152.3376] <4> bsa_checkFeatureId: INF - entering bsa_checkFeatureId 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST 15:43:01.326 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01 15:43:01.337 [3152.3376] <2> vnet_pcache_init_table: [vnet_private.c:208] starting cache size 200 0xc8 15:43:01.345 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.345 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.346 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.346 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.347 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.347 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.348 [3152.3376] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 15:43:01.362 [3152.3376] <2> vnet_pbxConnect: pbxConnectEx Succeeded 15:43:01.362 [3152.3376] <2> do_pbx_service: [vnet_connect.c:2164] via PBX bprd CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464 15:43:01.363 [3152.3376] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464 15:43:01.363 [3152.3376] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO MASTER01 172.30.20.210 bprd VIA pbx 15:43:01.363 [3152.3376] <2> init_resilient_cache: [vnet_nbrntd.c:863] Initialize resilient cache. 0 0x0 15:43:01.363 [3152.3376] <2> logconnections: BPRD CONNECT FROM 192.168.200.236.58701 TO 172.30.20.210.1556 fd = 464 15:43:01.363 [3152.3376] <2> vnet_check_vxss_client_magic_with_info_ex: [vnet_vxss_helper.c:894] Assuming no VxSS for DB Agents 0 0x0 15:43:01.701 [3152.3376] <4> bsa_checkFeatureId: INF - Successfully validated FeatureId 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_VERBOSE_LEVEL 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - 5 15:43:01.701 [3152.3376] <4> VxBSAInit: Veritas NetBackup XBSA Interface - 7.6 0 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_API 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_FEATURE_ID 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - <FEATURE_ID> 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01 15:43:01.701 [3152.3376] <4> bsa_checkFeatureId: INF - entering bsa_checkFeatureId 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - BSA_SERVICE_HOST 15:43:01.701 [3152.3376] <4> VxBSAGetEnv: INF - returning - MASTER01 15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.719 [3152.3376] <2> vnet_sortaddrs: [vnet_addrinfo.c:3852] sorted addrs: 1 0x1 15:43:01.719 [3152.3376] <2> vnet_get_pref_netconnection: [vnet_addrinfo.c:4750] using interface ANY 15:43:01.720 [3152.3376] <2> async_connect: [vnet_connect.c:1499] connect in progress 1 0x1 15:43:01.724 [3152.3376] <2> vnet_pbxConnect: pbxConnectEx Succeeded 15:43:01.725 [3152.3376] <2> do_pbx_service: [vnet_connect.c:2164] via PBX bprd CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464 15:43:01.725 [3152.3376] <2> async_connect: [vnet_connect.c:1691] connect async CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464 15:43:01.725 [3152.3376] <2> connect_to_service: connect succeeded STATUS (0) SUCCESS FROM 0.0.0.0 TO MASTER01 172.30.20.210 bprd VIA pbx 15:43:01.726 [3152.3376] <2> logconnections: BPRD CONNECT FROM 192.168.200.236.58702 TO 172.30.20.210.1556 fd = 464 15:43:01.726 [3152.3376] <2> vnet_check_vxss_client_magic_with_info_ex: [vnet_vxss_helper.c:894] Assuming no VxSS for DB Agents 0 0x0 15:43:02.061 [3152.3376] <4> bsa_checkFeatureId: INF - Successfully validated FeatureId 15:43:02.061 [3152.3376] <4> VxBSAGetEnv: INF - entering GetEnv - NBBSA_VERBOSE_LEVEL 15:43:02.061 [3152.3376] <4> VxBSAGetEnv: INF - returning - 5 15:43:02.061 [3152.3376] <4> VxBSADeleteOldFiles: INF - entering VxBSADeleteOldFiles 15:43:02.061 [3152.3376] <4> delete_old_files: entering delete_old_files. 15:43:02.062 [3152.3376] <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed. 15:43:02.062 [3152.3376] <1> CGlobalInformation::VCSVirtualNameList: CONTINUATION: - The system cannot find the path specified. 15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Native Client 15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Native Client\ 15:43:02.062 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Native Client\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Native Client\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\DataAccess\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server is installed on the system 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 10.0 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 10.0\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 10.0\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server Native Client 10.0 is installed on the system 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 11.0 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 11.0\ 15:43:02.063 [3152.3376] <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0\ 15:43:02.064 [3152.3376] <4> dbc_GetServerName: entering dbc_GetServerName. 15:43:02.064 [3152.3376] <4> getServerName: entering getServerName. 15:43:02.064 [3152.3376] <4> getServerName: Read server name from nb_master_config: MASTER01 15:43:02.064 [3152.3376] <4> CDBIniParms::CDBIniParms: INF - NT User is Admin_bcr 15:43:02.072 [3152.3376] <16> CGlobalInformation::QuerySQLServerInfo: ERR - Error in RegConnectRegistry, opening <HKEY_LOCAL_MACHINE> key on <\\>: 1707. The text follows: 15:43:02.073 [3152.3376] <1> CGlobalInformation::QuerySQLServerInfo: CONTINUATION: - The network address is invalid. 15:43:02.073 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server> 15:43:02.081 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Error Creating ODBC data source name 15:43:02.081 [3152.3376] <1> CGlobalInformation::CreateDSN: CONTINUATION: - Invalid string 15:43:02.081 [3152.3376] <1> CGlobalInformation::CreateDSN: CONTINUATION: - Driver's ConfigDSN, ConfigDriver, or ConfigTranslator failed 15:43:04.881 [3152.3376] <4> SQLEnumerator: INF - Enumerated SQL hosts: SERVER:Server={(local),VOLCANO01};UID:Login ID=?;PWD:Password=?;Trusted_Connection:Use Integrated Security=?;*APP:AppName=?;*WSID:WorkStation ID=? 15:43:04.881 [3152.3376] <4> CGlobalInformation::IsDefaultInstanceInstalled: INF - Error: ERROR_FILE_NOT_FOUND 15:43:04.881 [3152.3376] <1> CGlobalInformation::IsDefaultInstanceInstalled: CONTINUATION: - The system cannot find the file specified. 15:43:04.882 [3152.3376] <4> CGlobalInformation::SQLEnumerator: INF - Hosts and instances retrieved from host list string 15:43:04.882 [3152.3376] <4> CGlobalInformation::SQLEnumerator: INF - host: VOLCANO01 15:43:04.882 [3152.3376] <4> CGlobalInformation::SQLEnumerator: INF - instance: <default> 15:43:04.918 [3152.3376] <4> AugmentInstanceList: INF - Cannot obtain remote access to registry on \\VOLCANO01 15:43:04.919 [3152.3376] <8> CSQLDBMSOptions::OnInitDialog: WARN - Cannot expand instance list for host . 15:43:04.919 [3152.3376] <4> CSQLDBMSOptions::OnInitDialog: INF - It is unknown whether NetBackup for Microsoft SQL Server is installed on host machine 15:43:16.392 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server> 15:43:16.418 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_2>, SQL userid <sa> handle <0x00329810>. 15:43:33.957 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_2>, SQL userid <sa> handle <0x0032ab60>. 15:43:51.483 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <17><[Microsoft][ODBC SQL Server Driver][Shared Memory]SQL Server does not exist or access denied.>. 15:43:51.483 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).> 15:43:51.483 [3152.3376] <4> CGlobalInformation::CreateDSN: INF - Failed to connect. Attempting operation with next installed ODBC Driver <SQL Server Native Client 10.0> 15:43:51.521 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032b730>. 15:44:07.094 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032ce70>. 15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. >. 15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.> 15:44:22.621 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 10.0]Login timeout expired> 15:44:22.621 [3152.3376] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x0032ce70> 15:44:22.621 [3152.3376] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_3152_3376_3>, SQL userid <sa> handle <0x0032ec20>. 15:44:38.147 [3152.3376] <4> DBConnect: INF - Failed sql connect try #1 15:44:54.691 [3152.3376] <4> DBConnect: INF - Failed sql connect try #2 15:45:11.224 [3152.3376] <4> DBConnect: INF - Failed sql connect try #3 15:45:27.736 [3152.3376] <4> DBConnect: INF - Failed sql connect try #4 15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08001>, SQL Message <2><[Microsoft][SQL Server Native Client 10.0]Named Pipes Provider: Could not open a connection to SQL Server [2]. >. 15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <2><[Microsoft][SQL Server Native Client 10.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.> 15:45:44.260 [3152.3376] <16> CODBCaccess::LogODBCerr: DBMS MSG - SQL Message <0><[Microsoft][SQL Server Native Client 10.0]Login timeout expired> 15:45:44.260 [3152.3376] <16> CGlobalInformation::QuerySQLServerInfo: ERR - Unable to login into SQL instance <VOLCANO09\> as user <sa>. 15:45:44.260 [3152.3376] <4> CGlobalInformation::DeleteDSN: INF - Using ODBC Driver <SQL Server> 15:45:44.267 [3152.3376] <16> CSQLDBMSOptions::OnApply: ERR - Error 64 has been returned from QuerySQLServerInfo I tried some suggestions in several posts regarding UAC, user permissions, etc., but the issue is still there. Please advice. Thank you. Regards, Rolando.Solved13KViews2likes11CommentsBackup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated ThanksSolved13KViews1like4CommentsNetBackup: Cannot browse or restore SQL client backups
I am running NetBackup 7.5.0.6 and SQL 2012 on a Windows 2012 cluster. I have been able to back up databases from the SQL instance, but when I try to use the client to do a restore, I get an error "Error encountered trying to read database images" followed by "You may have received this error if you do not have access rights to backup imanges created for <sqlinstance>". The dbclient log shows - <2> vnet_pbxConnect: pbxConnectEx Succeeded <2> logconnections: BPRD CONNECT FROM 167.251.102.147.54431 TO 167.251.109.123.1556 fd = 504 <4> CGlobalInformation::VCSVirtualNameList: INF - Veritas Cluster Server is not installed. <1> CGlobalInformation::VCSVirtualNameList: CONTINUATION: - The system cannot find the path specified. <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Native Client <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Native Client\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Native Client\ <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Native Client\ <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\DataAccess\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server is installed on the system <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 10.0 <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 10.0\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 10.0\ <4> ODBCDataSource::isInstalled: INF - Registry entry not found for: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 10.0\ <4> ODBCDataSource::isInstalled: INF - Searching for ODBC Driver: SQL Server Native Client 11.0 <4> ODBCDataSource::isInstalled: INF - Registry Install Path: SOFTWARE\Microsoft\Microsoft SQL Server Native Client 11.0\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver Entry Registry Path: SOFTWARE\ODBC\ODBCINST.INI\SQL Server Native Client 11.0\ <4> ODBCDataSource::isInstalled: INF - ODBC Driver: SQL Server Native Client 11.0 is installed on the system <4> getServerName: Read server name from nb_master_config: mtccbackup13 <4> CDBIniParms::CDBIniParms: INF - NT User is _sqlserver <4> CGlobalInformation::CreateDSN: INF - Using ODBC Driver <SQL Server> <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_14296_10600_1>, SQL userid <_sqlserver> handle <0x01108ad0>. <4> CGlobalInformation::CreateDSN: INF - A successful connection to SQL Server <ETCCSPCLDB\> has been made using standard security with DSN <NBMSSQL_temp_14296_10600_1> <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x01108ad0> <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_temp_14296_10600_1>, SQL userid <_sqlserver> handle <0x011091f0>. <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x011091f0> <4> CGlobalInformation::DeleteDSN: INF - Using ODBC Driver <SQL Server> <4> getServerName: Read server name from nb_master_config: mtccbackup13 <2> vnet_pbxConnect: pbxConnectEx Succeeded <2> logconnections: BPRD CONNECT FROM 167.251.102.147.54436 TO 167.251.109.123.1556 fd = 864 <4> CBSASession::createSession(): INF - An XBSA Session has been created. <4> CDbbackupView::GetImageList: INF - XBSA Initialized. <2> vnet_pbxConnect: pbxConnectEx Succeeded <2> logconnections: BPRD CONNECT FROM 167.251.102.147.54437 TO 167.251.109.123.1556 fd = 848 <16> VxBSAQueryObject: ERR - dbc_get_string() failed 135 I had our Server Management group specifically give both nodes "Browse and restore ability" in the General tab of Client Attributes in Configuring Host Properties without any change to the outcome. I have the SQL server client set up correctly, and have tried running the NetBackup client as Administrator from both nodes and the virtual instance itself. Any ideas? Thanks GeoffBatesSolved9KViews1like7CommentsMS SQL Agent: Application connection failed for servername\.
Hi We have deployed new server: OS: Windows Server 2008 R2 x64 DB: MS SQL Server 2008 R2 x64 Express But netbackup SQL Agent can't connect to the instance with correct sa account: --------------------------- NetBackup Database Extension --------------------------- Application connection failed for SERVER01\. Please select a different SQL Server host and instance, or press 'cancel' to exit the NetBackup for SQL Server Graphical User Interface. --------------------------- OK Cancel --------------------------- We tried to disable UAC and run As Adminisrator, but without success We installed update 7.0.3 but id didn't help We've also checked Remote Registry service, its state is started This NB SQL Agent can connect to another SQL Server (with win 2003 x86-32), but can't connect to his own server.Solved8.4KViews0likes4CommentsERR - Error in VxBSASetEnv(BSA_SERVICE_HOST): 6.
Hi Guys, One Master server and Two Master servers running on Win 2008 Standard SP2 with Netbackup version 7.0.1 Client running on 2000 Server SP3, MSSQL 2000 Both the Master and media servers are in LAN and the client in in DMZ, ports are opened able to telnet and backup the filesystems. Only thing i struck with is the SQL backups. Backup exiting with the status code 2. Error message: ERR - Error in VxBSASetEnv(BSA_SERVICE_HOST): 6. CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid. ERR - Error in CDBbackrec::CDBbackrec: 6. CONTINUATION: - The system cannot find the file specified. ERR - Error in VxBSASetEnv(BSA_SERVICE_HOST): 6. CONTINUATION: - The handle used to associate this call with a previous VxBSAInit() call is invalid. INF - Results of executing <C:\Full_SQL_4wks.bch>: <0> operations succeeded. <23> operations failed. INF - The following object(s) were not backed up successfully. INF - ChoicesPersistence Tried all the possible solutions posted in the forum ealier. Thanks, SKSolved7.6KViews0likes5CommentsHow to exclude a SQL DB of a particular instance from backup
Hi, I am using separate scripts to perform FULL, INCR & LOG backups of the MSSQL databases. In each of the scripts I use the keyword "SQLINSTANCE $ALL" to backup all the instances. Suppose there are 3 instances: Instance1, Instance2, Instance3. And all these instances have 1 database named "DB01". Now, I need to exclude the database DB01 from LOG backup script of instance "Instance1". But the databases of Instance2 and Instance3 shouldn't be excluded. Note: I already heard about excluding the databases using NB_SQL_DATABASE_EXCLUDE environment variable. But this will cause excluding the database from all 3 instances. But what I want to exclude is only "Instance1\DB01". Regards, Ajeesh BSolved6.7KViews0likes8CommentsBE 2012 and Data Domain w/ DDBoost
Background: So we have Backup Exec 2012 and two Data Domain DD620's. We have all the required licensing including the Data Domain DD Boost and replication licenses. I have installed the Open Storage Technology (OST) plugin 2.5.0.3 as suggested for the version of BE. Both DD boxes are visable and connected to my BE server. I have foud some documentation and a video that explains some of what I am looking for but not entirely and most of it is for BE2010. The BE 2012 documentation from DD is not up to date yet. I am trying to setup backups as my tape drive has had enough and is not working properly. Anyone I have talked to just says you backup to it, then I continue finding little things that need to be done. No verify, no precompression, some said no deduplication in the job, other said server side dedupe because DDBoost manages it with OST plugin. Too much information and not enough people knowing what to tell me. The DD weekend support guys don't know the software titles they just know the hardware. I need help now unfortunately... Question: What settings do I use for Backups? I have Active Directory, Exchange, SharePoint, and SQL agents.6.5KViews1like32CommentsHaving problem on MSSQL agent backup
Hello Everyone, I'm new here and this is my first post!! :D I want to ask experts here about error from backup MSSQL using online agent. I use NBU extension GUI to create backup script to full backup all DB in default instance. When the schedule completed the parent job got status 1. Then I look for detailed page and found 1 of my DB cannot backup. ###error messages appear in Job status on NBU extention GUI ### INFO Error in GetConfiguration: 0x80770003. INFO The api was waiting and the timeout interval had elapsed. ###cut from dbclient log### 12:07:32.258 [8532.6572] <16> writeToServer: ERR - send() to server on socket failed: 12:07:32.258 [8532.6572] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket 12:07:32.258 [8532.6572] <4> dbc_RemoteWriteFile: INF - RemoteWriteFile status = 0 12:07:32.258 [8532.6572] <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003. error messages don't make any sense to me. I tried google and KB but no work. has anyone experience this before? please help me D: PS. sorry for my bad english.Solved5.9KViews2likes9CommentsFailed Final error: 0xe00084bd - The system cannot find the path specified - unable to restore file or directory.
Hello I can't backup only this Vm with Backup Exec 2014 since a very long time. They are no snapshot existed in snapshot Manager. When i select manually only one VM using snapshot technology .. Could you help me ? it says always .. And after the message appears.... ANd, Why it talk about restore ? I giev a backup not a restore. Error : e00084bd - The system cannot find the path specified - unable to restore file or directory. See the job log for details. Agent used : Yes Advanced Open File Option used : No5.6KViews1like16Comments