Restore Transaction Log - SqlServer2012
Hi all! we have problem with restore transaction log from netbackup. We have configured all like the documentation for try it, but the problem is this: 14-apr-2015 11.55.35 - begin Restore 14-apr-2015 11.55.36 - Info dbclient (pid=840) INF - RESTORE STARTED USING 14-apr-2015 11.55.36 - Info dbclient (pid=840) Microsoft SQL Server 2012 - 11.0.2100.60 (X64) 14-apr-2015 11.55.36 - Info dbclient (pid=840) Feb 10 2012 19:39:15 14-apr-2015 11.55.36 - Info dbclient (pid=840) Copyright (c) Microsoft Corporation 14-apr-2015 11.55.36 - Info dbclient (pid=840) Standard Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: ) (Hypervisor) 14-apr-2015 11.55.36 - Info dbclient (pid=840) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\restore_tran.bch, Op# = 1. 14-apr-2015 11.55.37 - Info dbclient (pid=840) INF - Using backup image DB-CRM.MSSQL7.DB-CRM.fg.VTE_CRM.PRIMARY.7.001of001.20150414000002..C 14-apr-2015 11.55.37 - Info dbclient (pid=840) INF - restore database "VTE_CRM" filegroup = 'PRIMARY' from VIRTUAL_DEVICE='VNBU0-840-5352-1429005337' with stats = 10, blocksize = 65536, maxtransfersize = 65536, buffercount = 1, replace , norecovery 14-apr-2015 11.55.37 - Info dbclient (pid=840) INF - Number of stripes: 1, Number of buffers per stripe 1. 14-apr-2015 11.55.37 - Info dbclient (pid=840) INF - Created VDI object for SQL Server instance <DB-CRM>. Connection timeout is <300> seconds. 14-apr-2015 12.00.37 - Info dbclient (pid=840) ERR - Error in GetConfiguration: 0x80770003. 14-apr-2015 12.00.37 - Info dbclient (pid=840) CONTINUATION: - The api was waiting and the timeout interval had elapsed. 14-apr-2015 12.00.38 - Info dbclient (pid=840) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3102><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE cannot process database 'VTE_CRM' because it is in use by this session. It is recommended that the master database be used when performing this operation.>. 14-apr-2015 12.00.38 - Info dbclient (pid=840) DBMS MSG - SQL Message <3013><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.> 14-apr-2015 12.00.38 - Info dbclient (pid=840) ERR - Error found executing <restore database "VTE_CRM" filegroup = 'PRIMARY' from VIRTUAL_DEVICE='VNBU0-840-5352-1429005337' with stats = 10, blocksize = 65536, maxtransfersize = 65536, buffercount = 1, replace , norecovery>. 14-apr-2015 12.00.38 - Info dbclient (pid=840) ERR - Error in VDS->Close: 0x80770004. 14-apr-2015 12.00.39 - Info dbclient (pid=840) CONTINUATION: - An abort request is preventing anything except termination actions. 14-apr-2015 12.00.39 - Info dbclient (pid=840) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\restore_tran.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 304(304) seconds. 14-apr-2015 12.00.41 - Info dbclient (pid=840) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\restore_tran.bch>: 14-apr-2015 12.00.41 - Info dbclient (pid=840) <0> operations succeeded. <1> operations failed. We have tried with my dba to set db in multiuser and single user, but the problem is the same! Has anyone ever experienced this problem and solved it? Thanks!Solved890Views3likes4CommentsCreating a native SQL Server backup file from Netbackup image
Is there a way to create a SQL Server native backup file from a previously taken Netbackup backup image? We currently backup our SQL Server databases to disk and let Netbackup take them to tape. We're looking to eliminate the disk drop and backup direct to Netbackup. Often times we need to send backups of our databases to vendors who require backups in the .bak format. In order to be able to use Netbackup for all our SQL Server backups we need to be able to make a .bak file from a previously taken backup. Is this possible? I haven't been able to find anything in the documentation suggesting it is, but may just be missing something. Thanks in advance for the help.Solved2.2KViews3likes7CommentsSQL backup problem
Hi experts SQL 2012 on server WIN 2008. recently added SQL instance. when i tried to run of this it fails give me error. 16> CODBCaccess::LogODBCerr: DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "model" under the current security context.>. i m getting same error for all databases in SQL instance. dbclient logs attachedSolved1.7KViews3likes8CommentsUnable 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 setupis 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.Solved13KViews2likes11CommentsLocal permissions for NetBackup user on SQL Server
Hi everybody, I was wondering if there is an official document or some documentation about why is necessary that a domainuser created to backup SQL Server with NetBackupneeds to be in the local administrator group? We're not using Local System so we created this user but need to have some evidence to our security team to get this kind of permission. I have only found the tech notes about SQL Server permissions but not about Windows server permissions for example. Any help is welcome. Thank you!!Solved3.1KViews2likes5Commentscan't connect to client(58) - SQL
Hello, I have a question. I have one Backup for SQL that showing me a error message, follow below. 2/9/2013 9:09:37 PM - Info nbjm(pid=586636) starting backup job (jobid=8544804) for client USCHINTDB900, policy CICA-SBY-SQL-TRANS-01, schedule Default-Application-Backup 12/9/2013 9:09:37 PM - Info nbjm(pid=586636) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=8544804, request id:{5510ECB4-613F-11E3-A3B3-2D900BB80000}) 12/9/2013 9:09:37 PM - requesting resource DISKPOOL1_805_CICA 12/9/2013 9:09:37 PM - requesting resource ussbybkup.NBU_CLIENT.MAXJOBS.USCHINTDB900 12/9/2013 9:09:37 PM - requesting resource ussbybkup.NBU_POLICY.MAXJOBS.CICA-SBY-SQL-TRANS-01 12/9/2013 9:09:42 PM - granted resource ussbybkup.NBU_CLIENT.MAXJOBS.USCHINTDB900 12/9/2013 9:09:42 PM - granted resource ussbybkup.NBU_POLICY.MAXJOBS.CICA-SBY-SQL-TRANS-01 12/9/2013 9:09:42 PM - granted resource MediaID=@aaaa4;Path=G:\NBU_STAGING_CICA;MediaServer=ussbyvcbk805 12/9/2013 9:09:42 PM - granted resource DISKPOOL1_805_CICA 12/9/2013 9:11:07 PM - estimated 0 Kbytes needed 12/9/2013 9:11:07 PM - Info nbjm(pid=586636) started backup job for client USCHINTDB900, policy CICA-SBY-SQL-TRANS-01, schedule Default-Application-Backup on storage unit DISKPOOL1_805_CICA 12/9/2013 9:11:08 PM - started process bpbrm (8584) 12/9/2013 9:11:09 PM - end writing 12/9/2013 9:16:48 PM - Error bpbrm(pid=8584) Cannot connect to USCHINTDB900 can't connect to client(58) 12/9/2013 9:16:48 PM - Info bpbrm(pid=8584) USCHINTDB900 is the host to backup data from 2/9/2013 8:54:12 PM - Error bprd(pid=815348) Unable to write progress log </C/ProgramÀFiles/Veritas/NetBackup/Logs/user_ops/dbext/logs/6276.0.1386640448> on client uschintdb900. Policy=CICA-SBY-SQL-TRANS-01 Sched=NONE 12/9/2013 8:54:12 PM - Error bprd(pid=815348) CLIENT uschintdb900 POLICY CICA-SBY-SQL-TRANS-01 SCHED NONE EXIT STATUS 58 (can't connect to client) can't connect to client(58) This server is pinging, but I can't conect to the client. C:\Users\s9lara>ping uschintdb900 Pinging USCHINTDB900 [10.16.103.23] with 32 bytes of data: Reply from 10.16.103.23: bytes=32 time=2ms TTL=127 Reply from 10.16.103.23: bytes=32 time=2ms TTL=127 Reply from 10.16.103.23: bytes=32 time=1ms TTL=127 Reply from 10.16.103.23: bytes=32 time=2ms TTL=127 Ping statistics for 10.16.103.23: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 2ms, Average = 1ms Regards, SidneiSolved921Views2likes4CommentsError in when backing up SQL
Hi All, We have configured SQL backups in our environment. One of the client that we are trying tyo backup its database has a strange behavior, we we run the job via the activity monitor we gotr the error shown below, while when i run the created*.bch file used for backing up the databasefrom client server SQL, the job completed successfully with out any error. Hint,the account using have sysadmin rights to all databases? Please Advbise. 1/14/2014 9:47:16 AM - Info nbjm(pid=5244) starting backup job (jobid=484798) for client sipc-lyncdb, policy lyncdb-Weekly-Full, schedule Full 1/14/2014 9:47:16 AM - Info nbjm(pid=5244) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=484798, request id:{2F7AC2B0-6F02-4870-B053-873E53EBCCB4}) 1/14/2014 9:47:16 AM - requesting resource STU2 1/14/2014 9:47:16 AM - requesting resource sipc-netbackup.NBU_CLIENT.MAXJOBS.sipc-lyncdb 1/14/2014 9:47:16 AM - requesting resource sipc-netbackup.NBU_POLICY.MAXJOBS.lyncdb-Weekly-Full 1/14/2014 9:47:16 AM - granted resource sipc-netbackup.NBU_CLIENT.MAXJOBS.sipc-lyncdb 1/14/2014 9:47:16 AM - granted resource sipc-netbackup.NBU_POLICY.MAXJOBS.lyncdb-Weekly-Full 1/14/2014 9:47:16 AM - granted resource sipc-sapdev2-hcart2-robot-tld-2 1/14/2014 9:47:16 AM - estimated 0 Kbytes needed 1/14/2014 9:47:16 AM - Info nbjm(pid=5244) started backup (backupid=sipc-lyncdb_1389682036) job for client sipc-lyncdb, policy lyncdb-Weekly-Full, schedule Full on storage unit sipc-sapdev2-hcart2-robot-tld-2 1/14/2014 9:47:24 AM - started process bpbrm (10120) 1/14/2014 9:47:26 AM - Info bpbrm(pid=10120) sipc-lyncdb is the host to backup data from 1/14/2014 9:47:26 AM - Info bpbrm(pid=10120) reading file list from client 1/14/2014 9:47:26 AM - connecting 1/14/2014 9:47:28 AM - Info bpbrm(pid=10120) starting bphdb on client 1/14/2014 9:47:28 AM - Info bphdb(pid=4172) Backup started 1/14/2014 9:47:28 AM - connected; connect time: 00:00:02 1/14/2014 9:47:35 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "LcsCDR" under the current security context.>. 1/14/2014 9:47:35 AM - Info dbclient(pid=3668) ERR - Error found executing <use "LcsCDR">. 1/14/2014 9:47:35 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database LcsCDR. 1/14/2014 9:47:35 AM - Info dbclient(pid=3668) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 4(4) seconds. 1/14/2014 9:47:39 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "mgc" under the current security context.>. 1/14/2014 9:47:39 AM - Info dbclient(pid=3668) ERR - Error found executing <use "mgc">. 1/14/2014 9:47:40 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database mgc. 1/14/2014 9:47:40 AM - Info dbclient(pid=3668) INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2(2) seconds. 1/14/2014 9:47:44 AM - Info dbclient(pid=3668) DBMS MSG - ODBC return code <-1>, SQL State <08004>, SQL Message <916><[Microsoft][ODBC SQL Server Driver][SQL Server]The server principal "NT AUTHORITY\SYSTEM" is not able to access the database "QoEMetrics" under the current security context.>. 1/14/2014 9:47:44 AM - Info dbclient(pid=3668) ERR - Error found executing <use "QoEMetrics">. 1/14/2014 9:47:44 AM - Info dbclient(pid=3668) ERR - Unable to determine FILESTREAM paths for database QoEMetrics. 1/14/2014 9:47:44 AM - Info dbclient(pid=3668) INF - OPERATION #3 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2(2) seconds. 1/14/2014 9:47:46 AM - Info dbclient(pid=3668) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\F.bch>: 1/14/2014 9:47:46 AM - Info dbclient(pid=3668) <0> operations succeeded. <3> operations failed. 1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - The following object(s) were not backed up successfully. 1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - LcsCDR 1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - mgc 1/14/2014 9:47:47 AM - Info dbclient(pid=3668) INF - QoEMetrics 1/14/2014 9:48:07 AM - Error bpbrm(pid=10120) from client sipc-lyncdb: ERR - command failed: none of the requested files were backed up (2) 1/14/2014 9:48:07 AM - Error bpbrm(pid=10120) from client sipc-lyncdb: ERR - bphdb exit status = 2: none of the requested files were backed up 1/14/2014 9:48:09 AM - Info bphdb(pid=4172) done. status: 2: none of the requested files were backed up 1/14/2014 9:48:09 AM - end writing none of the requested files were backed up(2)Solved3.4KViews2likes5Commentsbackup Performence
how to improve backup performance(For example I am running a backup operation it is taking 10 hours (consider ) then I need it to finish it within 5 hours or below mean as early as possible is it possible or not if possible means how Give me an example )Solved1.9KViews2likes8CommentsSQL Backup takes too much time
Hello, I need some advice. Running Symantec Netbackup 7.5.0.6 on windows server 2008 R2 SP1. SQL server is 2008 running on server 2008 R2. Everything works fine, all the databases finish their backups, but unfortunately it takes too long. We have many instances on the SQL server, and many databases for each instance. Each database is about 4-10 MB. Their backups take only 10-20 sec. The problem is that untill they start to backup it takes a long time. I can see the job is Active but writing to disk only starts after 5-10 min. As a result of this, the instance that has 800 samll databases doesn't finish its whole backup during the night Please suggest what should i change to improve the time period until the job actually starts to backup. This is the script that backups all the databases: OPERATION BACKUP DATABASE $ALL EXCLUDE "master" SQLHOST "bronko" SQLINSTANCE "instance1" NBSERVER "MSbackup" MAXTRANSFERSIZE 6 BLOCKSIZE 7 DUMPOPTION INCREMENTAL NUMBUFS 2 SQLCOMPRESSION TRUE RESTARTTYPE AUTO RESTARTWAITSECONDS 60 NUMRESTARTS 3 BATCHSIZE 20 ENDOPER TRUESolved2.9KViews2likes4Comments