Netbackup 7.6.1 client binaries
Hi All, Observed the 7.6.1 client binaries downloaded from symantec file connect having not all client binaries. The download contain two files NetBackup_7.6.1_CLIENTS1.tar.gz & NetBackup_7.6.1_CLIENTS2.tar.gz. Even if we extract individually or join and extract also not resulting all client binaries in the directories. Anyone used 7.6.1 clinet binaries, please share your ideas.Solved5.5KViews2likes9Commentsbplist EXIT STATUS 227: no entity was found (Again!)
Dear All, The bplist command lists all you want, and exactly all you ask for (even not being aware of it), as 1E100 counts problems are not rare. Basing on the already noticed and described cave-eats (short summary): https://www-secure.symantec.com/connect/forums/bplist-exit-status-227-no-entity-was-found Remember to choose policy type, if not you are using type == 0 (not Windows, not SQL, not Oracle etc...) https://www-secure.symantec.com/connect/forums/bplist-command As above and provide date range. Nice list of NetBackup policy types http://www.symantec.com/docs/TECH27299 bplist detailed syntax description http://www.symantec.com/docs/HOWTO43668 I would like to propose a set of "golden rules" for bplist command: 1. Always specify policy type (-t). 2. Always provide relevand data range (-s, -d). 3. Mind the listing recursiveness (-R) as it may be too verbose when you just put the "/" or it may not show anything for non-file like backup types. 4. Provide as many other details as possible to speed up the search. Template for good examples: bplist -C <ClientName> -S <MasterServer> -t <PolicyType> -k <PolicyName> -s MM/DD/YYYY HH:MM:SS -e MM/DD/YYYY HH:MM:SS -R / That may result in something like: bplist -C MyClient -S MyMaster -t 4 -k OraclePolicyName -s 08/08/2014 08:00:00 -e 09/09/2014 08:00:00 -R / Hopefully I will find this article prior loosing few hours solely on bplist syntax refresh ;-)2.6KViews2likes2CommentsNetbackup Services not Starting up
Hello Friends, My master Server is Windows 2008 R2 Netbackup 7.5.0.7 I try to restart Netbackup Services as Below NetBackup 7.5 -- Startup Utility NetBackup services are about to be started. Do you wish to proceed? (y/n) y Starting services > NetBackup Legacy Network Service > NetBackup Legacy Network Service -- STARTED > NetBackup Legacy Client Service > NetBackup Legacy Client Service -- STARTED > NetBackup Client Service > NetBackup Client Service -- STARTED > NetBackup SAN Client Fibre Transport Service > NetBackup SAN Client Fibre Transport Service -- STARTED > NetBackup Event Manager > NetBackup Event Manager -- STARTED > NetBackup Relational Database Manager > NetBackup Relational Database Manager -- STARTED > NetBackup Enterprise Media Manager > NetBackup Enterprise Media Manager -- STARTED > NetBackup Resource Broker > NetBackup Resource Broker -- STARTED > NetBackup Volume Manager > NetBackup Volume Manager -- STARTED > NetBackup Device Manager > NetBackup Device Manager -- STARTED > NetBackup Remote Manager and Monitor Service > NetBackup Remote Manager and Monitor Service -- STARTED > NetBackup Deduplication Manager > NetBackup Deduplication Manager -- DISABLED > NetBackup Deduplication Engine > NetBackup Deduplication Engine -- DISABLED > NetBackup CloudStore Service Container > NetBackup CloudStore Service Container -- STARTED > NetBackup Authentication > NetBackup Authentication -- NOT STARTED > NetBackup Authorization > NetBackup Authorization -- NOT STARTED > NetBackup Audit Manager > NetBackup Audit Manager -- STARTED > NetBackup Database Manager > NetBackup Database Manager -- STARTED > NetBackup Compatibility Service > NetBackup Compatibility Service -- STARTED > NetBackup Request Daemon > NetBackup Request Daemon -- STARTED > NetBackup Job Manager > NetBackup Job Manager -- STARTED > NetBackup Policy Execution Manager > NetBackup Policy Execution Manager -- STARTED > NetBackup Service Layer > NetBackup Service Layer -- STARTED > NetBackup Vault Manager > NetBackup Vault Manager -- STARTED > NetBackup Key Management Service > NetBackup Key Management Service -- STARTED > NetBackup Storage Lifecycle Manager > NetBackup Storage Lifecycle Manager -- STARTED > NetBackup Agent Request Server > NetBackup Agent Request Server -- STARTED > NetBackup Service Monitor > NetBackup Service Monitor -- NOT STARTED > NetBackup Indexing Manager > NetBackup Indexing Manager -- STARTED > NetBackup Bare Metal Restore Master Server > NetBackup Bare Metal Restore Master Server -- STARTED > NetBackup Bare Metal Restore Boot Server > NetBackup Bare Metal Restore Boot Server -- STARTED Start up of one or more services failed. however I find only few process started here. I am not able to see ltid,bptm,vmd....etc.. when I do bpps * WDRBKUPMSTR2 10/08/14 01:47:36.995 COMMAND PID LOAD TIME MEM START NBConsole 4028 0.000% 6.614 56M 10/06/14 16:31:11.798 vnetd 7024 0.000% 0.078 14M 10/08/14 01:42:36.103 bpinetd 6500 0.000% 1.029 16M 10/08/14 01:42:36.929 bpcd 6584 0.000% 0.140 17M 10/08/14 01:42:38.489 nbcssc 4460 0.000% 0.780 12M 10/08/14 01:43:01.406 bpps 20172 0.000% 0.499 10M 10/08/14 01:47:35.482 Please Help whats going Wrong. my two drives are Down and vmoprcmd is not giving any outputSolved14KViews2likes3Commentsbpexpdate versus nbholdutil
Hi, I am looking for some more information on nbholdutil as I have not been able to find much information on it. What i'm trying to do: Suspend images stored on tape by backup ID indefinitely until legal lets me know. I know how to do this but would like some info on the difference between bpexpdate and nbholdutil. So it appears there are 2 options, the traditional bpexpdate where I can just manually set a date far out in the future and continually do so, or from what I gathered from reading the commands guide, nbholdutil will do the same thing but hold the images indefinitely. Note* I do not have the OpsCenter Search and Hold License so I am strictly using the command line version. Below is the part i'm a bit confused on: NetBackup Search provides two methods for placing a hold on a backup image: Legal hold - You create a legal hold from Symantec NetBackup OpsCenter based on the results of a saved search. Local hold - You create a local hold from the command line interface of the NetBackup master server. So using the command line I put all my images on hold using this command: nbholdutil -add -holdname <name> -backupid <backupID> -allcopy Questions: Are there any differences between the "Legal" and the "Local" hold other than how you perform the hold? (GUI vs CLI) Is placing a hold on an image effectively the same thing as using bpexpdate and setting the date out, other than the fact that nbholdutil is an indefinite hold? Are there any caveats to using nbholdutil? thanks!Solved1.6KViews1like5CommentsNETBACKUP REPORT STATUS 0 AND DO NOT INFORMATION JOB SIZE
Hi Guys! Good Morning, The more a month I'm having trouble generating the volumetric report using the OpsCenter because the netbackup is not computing the amount of data copied. Found that, in both is generating the same data, so I believe the problem is not the OpsCenter. Someone had seen this problem? Netbackup Version = 7.1.0.4 Opscenter Version = 7.1.0.4Solved1.8KViews1like8CommentsNot able to do ndmp restore
Hi All, I am not able to do a ndmp restore .The filler is a emc vnx 5100 box. I am using netbackup 7.5 I tried all the options restore everything to a differnt location and orginal location but still getting error 2850 . 2-07-2015 11:55:08 - begin Restore 22-07-2015 11:55:09 - 1 images required 22-07-2015 11:55:09 - media L212L5 required 22-07-2015 11:55:09 - restoring image INMUMTCONAS01_1437330601 22-07-2015 11:55:10 - Info bpbrm(pid=4668) inmumtconbc02.india.tcs.com is the host to restore to 22-07-2015 11:55:10 - Info bpbrm(pid=4668) telling media manager to start restore on client 22-07-2015 11:55:11 - Info bpbrm(pid=4848) inmumtconbc02.india.tcs.com is the host to restore to 22-07-2015 11:55:11 - Info bpbrm(pid=4848) start tar32 on client 22-07-2015 11:55:11 - Info tar32(pid=4656) Restore started. 22-07-2015 11:55:11 - connected 22-07-2015 11:55:11 - Info bptm(pid=5100) Waiting for mount of media id L212L5 (copy 1) on server inmumtconbc02.india.tcs.com. 22-07-2015 11:55:11 - started process bptm (5100) 22-07-2015 11:55:11 - mounting L212L5 22-07-2015 11:55:11 - Info bptm(pid=5100) INF - Waiting for mount of media id L212L5 on server inmumtconbc02.india.tcs.com for reading. 22-07-2015 11:55:11 - requesting resource L212L5 22-07-2015 11:55:11 - granted resource L212L5 22-07-2015 11:55:11 - granted resource HP.ULTRIUM5-SCSI.000 22-07-2015 11:56:39 - mounted; mount time: 00:01:28 22-07-2015 11:56:39 - Info bptm(pid=5100) L212L5 22-07-2015 11:56:40 - Info bptm(pid=5100) INF - Waiting for positioning of media id L212L5 on server inmumtconbc02.india.tcs.com for reading. 22-07-2015 11:56:40 - positioning L212L5 to file 4 22-07-2015 11:57:37 - positioned L212L5; position time: 00:00:57 22-07-2015 11:57:37 - begin reading 22-07-2015 11:57:39 - Info ndmpagent(pid=4656) INF - Restoring NDMP files from /root_vdm_1/ISMUMBAI 22-07-2015 11:57:59 - Error ndmpagent(pid=4656) failed to connect to NDMP server inmumtconbc02.india.tcs.com, connect error = -1003 (Unable to connect to NDMP server) 22-07-2015 11:57:59 - Error ndmpagent(pid=4656) NDMP restore failed from path /root_vdm_1/ISMUMBAI 22-07-2015 11:58:04 - Info ndmpagent(pid=4656) done. status: 25: cannot connect on socket 22-07-2015 11:58:04 - Info bpbrm(pid=4668) got ERROR 5 from media manager 22-07-2015 11:58:04 - Info bpbrm(pid=4668) terminating bpbrm child 4848 jobid=754 22-07-2015 11:58:04 - Error bpbrm(pid=4668) could not open event Global\NetBackup Terminate Event, pid: 4848, The system cannot find the file specified. 22-07-2015 11:58:04 - restored image INMUMTCONAS01_1437330601 - (the restore failed to recover the requested files(5)); restore time 00:02:55 22-07-2015 11:58:07 - end Restore; elapsed time: 00:02:59 Restore error(2850)Solved946Views1like1Commentprobleme 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)765Views1like1CommentNBU with DD boost over FC
Hi, I'm currently doing some test for a project that the client is going to use NBU with data domain boost. We tried and sucess to backup data to DD boost through NBU, however, I can't establish the connection between NBU server and DD. Even the NBU server is visable to DD, NBU server wouldn't be able to mount the DD and see it on the device manager. Have search the NBU compatibilty matrix on http://www.symantec.com/business/support/index?page=content&id=TECH59978 but I couldn't found the compatility of NBU and DDOS. 1) Can someone share the experience of using DDBoost over FC with NBU? 2) We are suspecting this is the compatability issue between NBU and DDOS, would that be a case? We are currently testing on Win server 2008 R2 with NBU 7.6.1 and DDOS 5.5.0.1. Best, BrianSolved4KViews1like3Comments