NetBackup - NAS appliance and Offline Backups
Group, Hi, all. We're looking at options for an offline DR backup and were wondering if anyone has tried using a NAS appliance to receive backup copies and then just disconnecting it from the network once the backup completes? If so, what were your results? Thanks, Jason1.7KViews0likes7CommentsNetbackup 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.6KViews2likes9CommentsPros and Cons of Merge or Migrate of Catalog
Hi All, I am working on a hardware refresh for one of our NBU domain. I would like to know the pros and cons of Catalog Migarion over Catalog Merge. I would like to have a discussion thread which lists the the timeline, risks, overall implementation tasks etc... Thanks JafferSolved2.7KViews0likes6CommentsNetabckup Appliance 5200 not responding during upgrade
Hi all, I had a problem during upgrade, its been 18 Hours and it still stop on the same state of upgrade Veritas Optimzed Operating System 1 after do starting up vxconfigb ackupd. Below was the pic of the proses upgrade. Thanks All for your helpSolved574Views0likes1Commentbpexpdate 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.7KViews1like5CommentsEnterprise Vault: Export Back to Outlook 2010 issue
Hi all, Currently preparing for an Office 365 cutover by unarchiving all emails and exporting them back to their mailboxes (disabled users as well). I have an issue where when attempting to export archives back to outlook 2010 I cannot see the destination inbox. Currently only testing for one user. Checked the following: 1. Inbox is NOT hidden from exchange list 2. Account is NOT disabled in AD 3. EVService can control the account Any thoughts or other fields that need to be considered? EV states that the inbox has to be enabled and existing which they are. EV Version 10.0.1.1293 with Win2008-Outlook 2010 and Win2012-AD Thanks for your time!531Views1like3CommentsTECH51290 in relation to SQL Compatibility Mode for SQL 2012
Hey there!!! Needed a confirmation on a doubt I had. Having the same event as seen in the Status screen of the VAC and in TECH51290. Currently in my environment I have SQL 2012. It most likely must have been an upgrade from SQL 2008. The Compatibility Mode is set to 100 (SQL 2008). Will it make sense to follow this technote?956Views0likes3CommentsError 2820 restoring vmware virtual server with USB attached device
Hi, I got 2820 error when trying to restore the VM image backup of virtual server with physically attached USB device (special token card). Part of restore log with error is ................. skipped .... 13.08.2015 15:26:24 - end reading; read time: 0:00:00 13.08.2015 15:26:25 - Info bptm(pid=3464) completed reading backup image 13.08.2015 15:26:25 - Info bptm(pid=3464) EXITING with status 0 <---------- 13.08.2015 15:26:42 - Info bpVMutil(pid=5492) INF - vmwareLogger: WaitForTaskComplete: The device '4' is referring to a nonexisting controller '7,000'. <33> 13.08.2015 15:26:42 - Info bpVMutil(pid=5492) INF - vmwareLogger: WaitForTaskComplete: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE 13.08.2015 15:26:42 - Info bpVMutil(pid=5492) INF - vmwareLogger: CreateVm: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE 13.08.2015 15:26:42 - Info bpVMutil(pid=5492) INF - vmwareLogger: CreateVirtualMachineExAPI: SYM_VMC_ERROR: TASK_REACHED_ERROR_STATE 13.08.2015 15:26:47 - end Restore; elapsed time: 0:03:35 VMware policy restore error (2820) Another virtual machines without USB connected devices are restored without errors. I try restore with different options but with the same result. So options "keep hardware version", "remove backing information for devices like cd/dvd ...", "remove network inf.." and restoring to another datastore and esx were probed without success. We work in NBU 7.6.1.1 and vmware vSphere 5.5 environment Please help to solve this problem. Regards, Vlad.Solved3.4KViews0likes10Commentsprobleme 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)790Views1like1Comment