agent for microsoft sql server

155 Topics

How 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 B
Solved
Ajeesh
7 years ago Place NetBackup
6.9KViews
0likes
8Comments
Unable 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.
Solved
rebarquero
8 years ago Place NetBackup
14KViews
2likes
11Comments
MS SQL 2005 Full and Log backups at the same time.
Hello, Im in the process of testing and implementing the Netbackup 7.1 Enterprise solution in our enviroement. Specifically for backing up MS SQL 2005 databases. Some of the databases require only daily or weekly full backups but a few more important ones require frequent log backups. For example a specific database requires log backup every 15 minutes 24/7 and a daily full backup. MS SQL 2005 can backup a database and its log at the same time and our current solution is using SQL scripts that are scheduled using the SQL Agent. Backing up the log or data with Netbackup works fine separately but if either is allready running when the other tries to start then Netbackup logs an error message "INFO Error <DB_Name> is involved in another operation." Just to clarify this is a problem only when trying to backup the data and log of the same database. If I initiate a log backup by an adhoc SQL query at the same time netbackup is allready running a full backup of the database then everything works fine. So my question is does Netbackup support what I am trying to do?
Solved
KristjanS
8 years ago Place NetBackup
2KViews
0likes
7Comments
SQL backup fail with statuscode 2
Hi We have a 2008 SQL server that we can't backup from the master. It fails wit statuscode 2 Backup from the client works well. Env: Master: Windows 2008 Client : windows 2008 with SQL server 2008 Netbackup version: 7.6.0.1 I have attached the dbclient log (dbclient_log.doc) and the output from from the job (servertest.doc) We have other W2008 server with SQL server 2008 where netbackup is working. Any help is appreciated. //Lasse
Solved
lafo
9 years ago Place NetBackup
2.9KViews
1like
9Comments
none of the requested files were backed up (2)
Hello, can any one explain me this error : Info bphdb(pid=5652) Backup started 5/10/2016 11:59:39 AM - Error bpbrm(pid=9056) from client tcimor-db1: ERR - command failed: none of the requested files were backed up (2) 5/10/2016 11:59:39 AM - Error bpbrm(pid=9056) from client tcimor-db1: ERR - bphdb exit status = 2: none of the requested files were backed up 5/10/2016 11:59:39 AM - Info bphdb(pid=5652) done. status: 2: none of the requested files were backed up 5/10/2016 11:59:39 AM - end writing none of the requested files were backed up(2) i need solution for this best regards
ihaddoudy
9 years ago Place NetBackup
2.2KViews
0likes
7Comments
ANY MATERIALS FOR A FRESHER TO CRACK THE CERTIFICATION EXAM
Hi, i am fresher going to da certification on Netbackup tool. please give me any suggestions as : 1) which certification will help me a lot to work on Netbackup all kinds of services. 2) materials which can be helpful for cracking the exam other than the guides provided by the website. 3) what should i do to be more competent enough to handle all the situations in the environment while dealing with this tool. Regards, vinay sai
Solved
pravinay
9 years ago Place NetBackup
1.4KViews
0likes
2Comments
Unable to Complete Tape Restore - "The device is now being reused for one of the remaining families"
I am experiencing the following: I resume a restore from tape using Netbackup Client for SQL Server 7.6.1 and I monitor it using SQL Serevr Management Studio and the Job Details on NetBackup Activity Monitor . ON SSMS, the restore process gets about halfway and stops moving, the databases being developed remain in "Restoring" state. On the Job Details log, the first client job appears to complete successfully but the parent job returns error.
Kenneth_Igiri
10 years ago Place NetBackup
3.4KViews
0likes
10Comments
Migration of clients from Solaris master server to new linux master server with backup images
Hi Team, I have an activity to perform for my client and need your suggestions. The activity is: Existing setup: Master - solaris 11 [standalone, means non-clustered], NB Version - 7.7 Another site: Master: Linx 6 [VCS clustered], NB Version - 7.7 I have to migrate certain clients from Existing setup to another site, i.e. move clients which are currently being backed up by Solaris master server, to new master server i.e. Linux - We want to move the old backups as well -The old backups includes, windows, linux, solaris clients with Vmware, Oracle, MS-SQL, Filesystem backups Here is my plan: 1) Isolate the clients and policy list 2) Determine all backup images with backup and expiry date 3) Determine the list of medias used in the backups of all these clients 4) Move the tapes to new tape library and placed them in SAFE volume pool 5) Run phase 1 on all these tapes and run phase 2 import for images determined in Step 2 6) Run bpimagelist -recalculate against all these images with the date as expiry date we find in Step 2 7) Modify the bp.conf or registry for SERVER entries and populate the new servers 8) Modify the scripts for oracle & SQL DB backups 9) RUn some test restores to test if everything is ok 10) Disable the policies in Solaris master server My concerns are with the DB backups and vmware backups. With the phase 1 and phase 2 imports are enough for DB backups? Because, I beleive RMAN also keeps the information about backup media server or backup server, which will change now. Any extra steps required? Thanks for your assistance and time.
Solved
Pinku
10 years ago Place NetBackup
2.9KViews
0likes
19Comments
Deduplication when using SQL Server backup compression
A quick question about using NetBackup with compressed SQL Server backups. Our backups infrastructure consists of NetBackup v7.6 and NetBackup 5230 appliances. Our SQL server estate is a mixture of SQL Server versions 2005-2012 on Windows 2003-2012. We've noticed that the deduplication ratio (as reported by backup jobs in Netbackup Activity Monitor) for compressed SQL backups is 0% (we experimented with the NetBackup SQL Agent and also standard flat file backups). Now we weren't expecting to get much deduplication out of a compressed SQL Server backup - but it was a suprise to get nothing at all. Previous tests performed on other deduplication platforms (Exagrid and Windows native 2012 deduplication) showed that a noticeable (albeit much lower rate compared with uncompressed backups) deduplication level of about 4:1 was possible with compressed SQL Server backups. So my question is - is this a configuration issue on our NetBackup infrastructure - or is there a technical\design reason why the deduplication of compressed SQL Server backups is not available in NetBackup? Regards Terry
Solved
Terry_Darrocot
10 years ago Place NetBackup Appliance
4.7KViews
0likes
3Comments
probleme exchange DAG server 2012
master server : solaris 10 media1 & media 2: oracle linux server backup 7.6.4 client : windows 2012 DAG exchange client version 7.5.0.6 code erreur : 1: (636) read from input socket failed file list : SET SNAP_ID=TTDAG01_1431802911 SET SNAP_ID=TTDAG01_1431802914 EXCHGDATA 49 Microsoft Exchange Database Availability Groups:\ 268566596 16 130762766177000000 130762766177000000 130762766177000000 0 0 0 FILEBACKUP 106 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MEDAG.MetaData.txt EXCHGDATA 56 Microsoft Exchange Database Availability Groups:\TTDAG01 2752512 16 130762766177000000 130762766177000000 130762766177000000 0 0 0 FILEBACKUP 111 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MEDAG_DAG1.MetaData.txt EXCHGDATA 29 Microsoft Information Store:\ 268566570 16 130762766177000000 130762766177000000 130762766177000000 0 0 0 FILEBACKUP 104 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS.MetaData.txt EXCHGDATA 39 Microsoft Information Store:\DBLight01\ 270532609 16 130762766538222031 130762766538222031 130762766538222031 0 0 0 FILEBACKUP 108 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1.MetaData.txt SCC_DATA 48 Microsoft Information Store:\DBLight01\User?Data FILEBACKUP 110 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD.MetaData.txt SCC_DATA 64 Microsoft Information Store:\DBLight01\User?Data\Exchange Server FILEBACKUP 113 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES.MetaData.txt SCC_DATA 90 Microsoft Information Store:\DBLight01\User?Data\Exchange Server\Microsoft Exchange Server FILEBACKUP 117 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES_MES.MetaData.txt SCC_DATA 118 Microsoft Information Store:\DBLight01\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store FILEBACKUP 121 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES_MES_MIS.MetaData.txt SCC_DATA 126 Microsoft Information Store:\DBLight01\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica FILEBACKUP 129 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES_MES_MIS_Replica.MetaData.txt SCC_DATA 142 Microsoft Information Store:\DBLight01\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica\KBPRMAILBX01A01 FILEBACKUP 145 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES_MES_MIS_Replica_KBPRMAILBX01A01.MetaData.txt SCC_DATA 152 Microsoft Information Store:\DBLight01\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica\KBPRMAILBX01A01\DBLight01 FILEBACKUP 155 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1UD_ES_MES_MIS_Replica_KBPRMAILBX01A01_DBLight01.MetaData.txt EXCHGDATA 48 Microsoft Information Store:\DBLight01\Database\ 2097154 128 130762766552031983 130762766550000000 130762766550000000 585173590 183 FILEBACKUP 117 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Database.MetaData.txt BACKUP G:\DBLight01\DB\DBLight01.edb USING /Microsoft Information Store/DBLight01/Database//\\?/GLOBALROOT/Device/HarddiskVolumeShadowCopy100/DBLight01/DB/DBLight01.edb OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_11460_1,GRT_LINK=1,METADATA=C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Database_DBLight01.edb.MetaData.txt EXCHGDATA 55 Microsoft Information Store:\DBLight01\Logs_1431802914\ 2097154 128 130762766560779169 130762766560000000 130762766560000000 1016192358 4 FILEBACKUP 113 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Logs.MetaData.txt LOGS_BACKUP G:\DBLight01\LOG\E00003485AD.log USING /Microsoft Information Store/DBLight01/Logs_1431802914//\\?/GLOBALROOT/Device/HarddiskVolumeShadowCopy100/DBLight01/LOG/E00003485AD.log OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_11460_1,GRT_LINK=0,METADATA=C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Logs_E00003485AD.log.MetaData.txt,LOG_COUNT=5056 LOGS_BACKUP G:\DBLight01\LOG\E000034996D.log USING /Microsoft Information Store/DBLight01/Logs_1431802914//\\?/GLOBALROOT/Device/HarddiskVolumeShadowCopy100/DBLight01/LOG/E000034996D.log OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_11460_1,GRT_LINK=1,METADATA=C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Logs_E000034996D.log.MetaData.txt,LOG_COUNT=6 BACKUP G:\DBLight01\LOG\E00tmp.log USING /Microsoft Information Store/DBLight01/Logs_1431802914//\\?/GLOBALROOT/Device/HarddiskVolumeShadowCopy100/DBLight01/LOG/E00tmp.log OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_11460_1,GRT_LINK=1,METADATA=C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Logs_E00tmp.log.MetaData.txt BACKUP G:\DBLight01\LOG\E00.chk USING /Microsoft Information Store/DBLight01/Logs_1431802914//\\?/GLOBALROOT/Device/HarddiskVolumeShadowCopy100/DBLight01/LOG/E00.chk OPTIONS:ALT_PATH_PREFIX=C:\Program Files\Veritas\NetBackup\temp\_vrts_frzn_img_11460_1,GRT_LINK=1,METADATA=C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG1_Logs_E00.chk.MetaData.txt EXCHGDATA 39 Microsoft Information Store:\DBLight02\ 270532609 16 130762769231440222 130762769231440222 130762769231440222 0 0 0 FILEBACKUP 108 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2.MetaData.txt SCC_DATA 48 Microsoft Information Store:\DBLight02\User?Data FILEBACKUP 110 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD.MetaData.txt SCC_DATA 64 Microsoft Information Store:\DBLight02\User?Data\Exchange Server FILEBACKUP 113 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES.MetaData.txt SCC_DATA 90 Microsoft Information Store:\DBLight02\User?Data\Exchange Server\Microsoft Exchange Server FILEBACKUP 117 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES_MES.MetaData.txt SCC_DATA 118 Microsoft Information Store:\DBLight02\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store FILEBACKUP 121 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES_MES_MIS.MetaData.txt SCC_DATA 126 Microsoft Information Store:\DBLight02\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica FILEBACKUP 129 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES_MES_MIS_Replica.MetaData.txt SCC_DATA 142 Microsoft Information Store:\DBLight02\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica\KBPRMAILBX01A01 FILEBACKUP 145 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES_MES_MIS_Replica_KBPRMAILBX01A01.MetaData.txt SCC_DATA 152 Microsoft Information Store:\DBLight02\User?Data\Exchange Server\Microsoft Exchange Server\Microsoft Information Store\Replica\KBPRMAILBX01A01\DBLight02 FILEBACKUP 155 0 C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.TTDAG01_1431802914.1.0.MIS_SG2UD_ES_MES_MIS_Replica_KBPRMAILBX01A01_DBLight02.MetaData.txt EXCHGDATA 48 Microsoft Information Store:\DBLight02\Database\ 2097154 128 130762769243870157 130762769240000000 130762769240000000 679545362 24 ... msg erreur : 05/16/2015 20:20:09 - Info nbjm (pid=2139) starting backup job (jobid=378833) for client KBPRMAILBX01A01.INTRA.TUNISIETELECOM.ENTERPRISE, policy Exchange2010, schedule Full 05/16/2015 20:20:10 - estimated 0 kbytes needed 05/16/2015 20:20:10 - Info nbjm (pid=2139) started backup (backupid=TTDAG01_1431804009) job for client KBPRMAILBX01A01.INTRA.TUNISIETELECOM.ENTERPRISE, policy Exchange2010, schedule Full on storage unit Dedup_Raid5 05/16/2015 20:20:11 - started process bpbrm (pid=20161) 05/16/2015 20:20:14 - connecting 05/16/2015 20:20:15 - connected; connect time: 0:00:00 05/16/2015 20:21:20 - begin writing 05/17/2015 02:12:03 - Info bpbrm (pid=20161) KBPRMAILBX01A01.INTRA.TUNISIETELECOM.ENTERPRISE is the host to backup data from 05/17/2015 02:12:03 - Info bpbrm (pid=20161) reading file list for client 05/17/2015 02:12:05 - Info bpbrm (pid=20161) starting bpbkar on client 05/17/2015 02:12:28 - Info bpbkar (pid=8288) Backup started 05/17/2015 02:12:28 - Info bpbrm (pid=20161) bptm pid: 20164 05/17/2015 02:12:29 - Info bptm (pid=20164) start 05/17/2015 02:13:04 - Info bptm (pid=20164) using 262144 data buffer size 05/17/2015 02:13:04 - Info bptm (pid=20164) using 256 data buffers 05/17/2015 02:13:05 - Info bptm (pid=20164) start backup 05/17/2015 02:13:10 - Info bptm (pid=20164) backup child process is pid 20198 05/17/2015 03:08:07 - Info bpbrm (pid=20161) DB_BACKUP_STATUS is 0 05/17/2015 03:16:57 - Info bpbrm (pid=20161) DB_BACKUP_STATUS is 0 05/17/2015 04:24:05 - Info bpbrm (pid=20161) DB_BACKUP_STATUS is 0 05/17/2015 04:24:06 - Error bpbrm (pid=20161) could not write FILE ADDED message to OUTSOCK 05/17/2015 04:38:59 - Info bpbrm (pid=20161) DB_BACKUP_STATUS is 0 05/17/2015 04:39:00 - Error bpbrm (pid=20161) could not write FILE ADDED message to OUTSOCK 05/17/2015 05:31:59 - Info bpbrm (pid=20161) DB_BACKUP_STATUS is 0 05/17/2015 05:32:00 - Error bpbrm (pid=20161) could not write FILE ADDED message to OUTSOCK 05/17/2015 05:32:07 - Error bpbrm (pid=20161) could not write FILE ADDED message to OUTSOCK 05/17/2015 05:32:07 - Info bptm (pid=20164) waited for full buffer 488334 times, delayed 593006 times 05/17/2015 05:32:08 - Error bpbrm (pid=20161) could not write FILE ADDED message to OUTSOCK 05/17/2015 05:32:34 - Info bptm (pid=20164) EXITING with status 0 <---------- 05/17/2015 05:32:34 - Info media2 (pid=20164) StorageServer=PureDisk:media2; Report=PDDO Stats (multi-threaded stream used) for (media2): scanned: 683139905 KB, CR sent: 27483911 KB, CR sent over FC: 0 KB, dedup: 96.0%, cache hits: 19049 (0.4%) 05/17/2015 05:32:34 - Info bpbrm (pid=20161) validating image for client TTDAG01 05/17/2015 05:32:38 - Error bpbrm (pid=20161) could not write EXIT STATUS to OUTSOCK 05/17/2015 05:32:38 - Info bpbkar (pid=8288) done. status: 0: the requested operation was successfully completed read from input socket failed (636)
slim_Hannachi
10 years ago Place NetBackup
790Views
1like
1Comment