How many integrations are there between VMware and Net Backup for virtual machine backup?
I asked one of our leading virtualization experts, Gerorge Winter to get me a list of some of the integrations we have built with VMware. Here is his first pass of a list he just sent me in email. This is the underpinning of the technology that has taken home more Best of VMworld awards for data protection than anyone else. More capabilities are coming for VMworld this year too. vStorage API for Data Protection (VADP) – Explicit integration with this backup API vCenter server – Credentialed access to the vCenter which provides ability to direct backup activities to the entire vSphere environment through this single point of contact ESX server – Direct access to the ESX server for backup or optimized restore functionality ESXi server – Direct access to the ESXi server for backup or optimized restore functionality Changed Block Tracking (CBT) – Full support of this mechanism to provide true incremental backup and restore functionality VMware Consolidated Backup (VCB) – Image based backups VMware Consolidated Backup (VCB) mount API – File level backups VMware Converter – Integration provides entire VM restore support for non-VADP (VCB) style of backups VDDK SAN Access – Used for direct access to Datastores for true off-host backups. Support for both Fibre and iSCSI based Datastores. VDDK SAN Access – Used for direct access to Datastores for true direct to storage restores. Support for both Fibre and iSCSI based Datastores. VDDK NBD transport – Network based backups and restores VDDK NBDSSL transport – Secure Network based backups and restores Hotadd – Virtual Machine based backups and restores VDDK Mount API – Part of the Application/Database Granular Restore functionality
SLP Duplication of MS Exchange 2013 GRT images
Hi I have a couple of issues with SLP duplication from disk to tape. 1. As far as I can see, the duplication job requests and is granted a tape drive and a tape before the cataloging of the mailboxes starts, but the cataloging doesn't write anything to the tape. After cataloging the job again requests resources, on which the image is written. Why is the duplication job requesting resources it doesn't need? 2. When there are more than one image in the duplication job, the duplication of the first image is successful and the second and following images fails. The failing duplication's succeeds in later duplication jobs. Our configuration is: Master server 7.6.1.1 on Windows 2008R2 Appliance 2.6.1.1 on NetBackup Appliance 5220 Media server 7.6.1.1 on Linux MS Exchange 2013 CU8 on Windows 2012R2 (vmWare 5.5) - Agent NetBackup 7.6.1.1 The Exchange backup goes to PureDisk on Appliance and then to tape. Duplication job log 1: 20/05/2015 00:30:24 - begin Duplicate 20/05/2015 00:30:24 - requesting resource LCM_s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 00:30:24 - granted resource LCM_s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 00:30:24 - started process RUNCMD (4116) 20/05/2015 00:30:24 - ended process 0 (4116) 20/05/2015 00:30:24 - requesting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 00:30:24 - requesting resource @aaaah 20/05/2015 00:30:24 - reserving resource @aaaah 20/05/2015 00:30:25 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 00:31:18 - reserved resource @aaaah 20/05/2015 00:31:18 - granted resource C00153 20/05/2015 00:31:18 - granted resource IBM.ULT3580-TD5.001 20/05/2015 00:31:18 - granted resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 00:31:18 - granted resource MediaID=@aaaah;DiskVolume=PureDiskVolume;DiskPool=dp_disk_s-sg-infr-nba01;Path=PureDiskVolume;StorageServer=s-sg-infr-nba01;MediaServer=s-sg-infr-nba01 20/05/2015 00:32:03 - Info bpdbm(pid=9120) cataloguing file number 10000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:32:29 - Info bpdbm(pid=9120) cataloguing file number 20000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:32:44 - Info bpdbm(pid=9120) cataloguing file number 30000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:32:55 - Info bpdbm(pid=9120) cataloguing file number 40000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:33:04 - Info bpdbm(pid=9120) cataloguing file number 50000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:33:32 - Info bpdbm(pid=9120) cataloguing file number 60000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/... 20/05/2015 00:33:42 - Info bpdbm(pid=9120) cataloguing file number 70000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:34:03 - Info bpdbm(pid=9120) cataloguing file number 80000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:34:15 - Info bpdbm(pid=9120) cataloguing file number 90000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:34:41 - Info bpdbm(pid=9120) cataloguing file number 100000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:37:12 - Info bpdbm(pid=9120) cataloguing file number 200000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:39:31 - Info bpdbm(pid=9120) cataloguing file number 300000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:41:29 - Info bpdbm(pid=9120) cataloguing file number 400000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:44:02 - Info bpdbm(pid=9120) cataloguing file number 500000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:47:02 - Info bpdbm(pid=9120) cataloguing file number 600000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:50:00 - Info bpdbm(pid=9120) cataloguing file number 700000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:53:01 - Info bpdbm(pid=9120) cataloguing file number 800000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:55:38 - Info bpdbm(pid=9120) cataloguing file number 900000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 00:58:07 - Info bpdbm(pid=9120) cataloguing file number 1000000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:00:47 - Info bpdbm(pid=9120) cataloguing file number 1100000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:03:26 - Info bpdbm(pid=9120) cataloguing file number 1200000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:06:11 - Info bpdbm(pid=9120) cataloguing file number 1300000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:08:23 - Info bpdbm(pid=9120) cataloguing file number 1400000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:11:56 - Info bpdbm(pid=9120) cataloguing file number 1500000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:16:33 - Info bpdbm(pid=9120) cataloguing file number 1600000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:21:13 - Info bpdbm(pid=9120) cataloguing file number 1700000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:25:11 - Info bpdbm(pid=9120) cataloguing file number 1800000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:29:12 - Info bpdbm(pid=9120) cataloguing file number 1900000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:33:55 - Info bpdbm(pid=9120) cataloguing file number 2000000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:37:21 - Info bpdbm(pid=9120) cataloguing file number 2100000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:42:30 - Info bpdbm(pid=9120) cataloguing file number 2200000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:45:25 - Info bpdbm(pid=9120) cataloguing file number 2300000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:50:19 - Info bpdbm(pid=9120) cataloguing file number 2400000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Database/ 20/05/2015 01:53:58 - Info bpdbm(pid=9120) cataloguing file number 2500000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Logs_1432044322/E010004D261.log 20/05/2015 01:54:01 - Info bpdbm(pid=9120) cataloguing file number 2600000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-B1/Logs_1432044322/E0100065901.log 20/05/2015 01:54:02 - Info bpdbm(pid=9120) catalogued 2649942 entries 20/05/2015 01:54:03 - Info bpduplicate(pid=4116) window close behavior: Suspend 20/05/2015 01:54:05 - Info bptm(pid=7316) start 20/05/2015 01:54:05 - started process bptm (7316) 20/05/2015 01:54:05 - requesting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 01:54:06 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 01:54:10 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 01:54:23 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 01:54:29 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:00:30 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:01:40 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:03:11 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:04:00 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:08:58 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:10:03 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:15:49 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:16:26 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:29:07 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:29:26 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:39:12 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:40:14 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:44:05 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:44:55 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 02:49:30 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - No drives are available 20/05/2015 02:50:11 - awaiting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP - Maximum job count has been reached for the storage unit 20/05/2015 03:04:17 - Info bptm(pid=7316) start backup 20/05/2015 03:04:17 - granted resource C00153 20/05/2015 03:04:17 - granted resource IBM.ULT3580-TD5.004 20/05/2015 03:04:17 - granted resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 03:04:19 - Info bpdm(pid=29610) started 20/05/2015 03:04:19 - started process bpdm (29610) 20/05/2015 03:04:19 - Info bpdm(pid=29610) reading backup image 20/05/2015 03:04:19 - Info bpdm(pid=29610) using 512 data buffers 20/05/2015 03:04:19 - Info bpdm(pid=29610) requesting nbjm for media 20/05/2015 03:04:19 - Info bptm(pid=7316) Waiting for mount of media id C00153 (copy 2) on server s-sg-infr-nba01. 20/05/2015 03:04:19 - requesting resource @aaaah 20/05/2015 03:04:19 - started process bptm (7316) 20/05/2015 03:04:19 - mounting C00153 20/05/2015 03:04:19 - Info bptm(pid=7316) INF - Waiting for mount of media id C00153 on server s-sg-infr-nba01 for writing. 20/05/2015 03:04:19 - granted resource MediaID=@aaaah;DiskVolume=PureDiskVolume;DiskPool=dp_disk_s-sg-infr-nba01;Path=PureDiskVolume;StorageServer=s-sg-infr-nba01;MediaServer=s-sg-infr-nbm01.fehem.net 20/05/2015 03:04:21 - begin reading 20/05/2015 03:04:47 - Info bptm(pid=7316) media id C00153 mounted on drive index 3, drivepath /dev/nst7, drivename IBM.ULT3580-TD5.004, copy 2 20/05/2015 03:04:47 - Info bptm(pid=7316) INF - Waiting for positioning of media id C00153 on server s-sg-infr-nba01 for writing. 20/05/2015 03:14:50 - end reading; read time: 0:10:29 20/05/2015 03:14:50 - begin reading 20/05/2015 03:21:21 - end reading; read time: 0:06:31 20/05/2015 03:21:21 - begin reading 20/05/2015 03:27:43 - end reading; read time: 0:06:22 20/05/2015 03:27:43 - begin reading 20/05/2015 03:33:56 - end reading; read time: 0:06:13 20/05/2015 03:33:57 - begin reading 20/05/2015 03:40:54 - end reading; read time: 0:06:57 20/05/2015 03:40:54 - begin reading 20/05/2015 03:46:45 - end reading; read time: 0:05:51 20/05/2015 03:46:46 - begin reading 20/05/2015 03:54:31 - end reading; read time: 0:07:45 20/05/2015 03:54:31 - begin reading 20/05/2015 04:02:34 - end reading; read time: 0:08:03 20/05/2015 04:02:35 - begin reading 20/05/2015 04:09:22 - end reading; read time: 0:06:47 20/05/2015 04:09:22 - begin reading 20/05/2015 04:16:44 - end reading; read time: 0:07:22 20/05/2015 04:16:44 - begin reading 20/05/2015 04:24:50 - end reading; read time: 0:08:06 20/05/2015 04:24:51 - begin reading 20/05/2015 04:30:42 - end reading; read time: 0:05:51 20/05/2015 04:30:43 - begin reading 20/05/2015 04:30:43 - Info bptm(pid=7316) waited for full buffer 101290 times, delayed 142075 times 20/05/2015 04:30:48 - Info bptm(pid=7316) EXITING with status 0 <---------- 20/05/2015 04:30:48 - end reading; read time: 0:00:05 20/05/2015 04:30:49 - Info bpdm(pid=29610) completed reading backup image 20/05/2015 04:30:49 - end Duplicate; elapsed time: 4:00:25 20/05/2015 04:30:49 - Info bpdm(pid=29610) EXITING with status 0 20/05/2015 04:30:49 - Info s-sg-infr-nba01(pid=29610) StorageServer=PureDisk:s-sg-infr-nba01; Report=PDDO Stats for (s-sg-infr-nba01): read: 604499553 KB, CR received: 488975135 KB, CR received over FC: 0 KB, dedup: 0.0% the requested operation was successfully completed (0) Duplication log 2: 20/05/2015 12:50:27 - requesting resource LCM_s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 12:50:27 - granted resource LCM_s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 12:50:27 - started process RUNCMD (4720) 20/05/2015 12:50:27 - ended process 0 (4720) 20/05/2015 12:50:28 - begin Duplicate 20/05/2015 12:50:28 - requesting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 12:50:28 - requesting resource @aaaah 20/05/2015 12:50:28 - reserving resource @aaaah 20/05/2015 12:50:29 - reserved resource @aaaah 20/05/2015 12:50:29 - granted resource C00153 20/05/2015 12:50:29 - granted resource IBM.ULT3580-TD5.005 20/05/2015 12:50:29 - granted resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 12:50:29 - granted resource MediaID=@aaaah;DiskVolume=PureDiskVolume;DiskPool=dp_disk_s-sg-infr-nba01;Path=PureDiskVolume;StorageServer=s-sg-infr-nba01;MediaServer=s-sg-infr-nba01 20/05/2015 12:51:39 - Info bpdbm(pid=7336) cataloguing file number 10000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:52:45 - Info bpdbm(pid=7336) cataloguing file number 20000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:53:30 - Info bpdbm(pid=7336) cataloguing file number 30000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:53:50 - Info bpdbm(pid=7336) cataloguing file number 40000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:54:15 - Info bpdbm(pid=7336) cataloguing file number 50000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:54:49 - Info bpdbm(pid=7336) cataloguing file number 60000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:55:32 - Info bpdbm(pid=7336) cataloguing file number 70000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:55:58 - Info bpdbm(pid=7336) cataloguing file number 80000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:56:39 - Info bpdbm(pid=7336) cataloguing file number 90000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 12:57:00 - Info bpdbm(pid=7336) cataloguing file number 100000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 13:02:39 - Info bpdbm(pid=7336) cataloguing file number 200000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 13:07:37 - Info bpdbm(pid=7336) cataloguing file number 300000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 13:13:36 - Info bpdbm(pid=7336) cataloguing file number 400000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 13:18:31 - Info bpdbm(pid=7336) cataloguing file number 500000 path /Microsoft Exchange Database Availability Groups/exchange-dag/Microsoft Information Store/FE-EXCH-DB-A2/Database/ 20/05/2015 13:21:52 - Info bpdbm(pid=7336) catalogued 559040 entries 20/05/2015 13:21:53 - requesting resource @aaaah 20/05/2015 13:21:53 - granted resource MediaID=@aaaah;DiskVolume=PureDiskVolume;DiskPool=dp_disk_s-sg-infr-nba01;Path=PureDiskVolume;StorageServer=s-sg-infr-nba01;MediaServer=s-sg-infr-bck01.fehem.net 20/05/2015 13:21:55 - Error bpduplicate(pid=4720) db_IMAGE() failed: socket open failed (21) 20/05/2015 13:21:55 - Error bpduplicate(pid=4720) Status = successfully built catalog for 1 of 2 images. 20/05/2015 13:21:55 - Error bpduplicate(pid=4720) Status = the requested operation was partially successful. 20/05/2015 13:21:55 - Info bpduplicate(pid=4720) window close behavior: Suspend 20/05/2015 13:21:56 - Info bptm(pid=17945) start 20/05/2015 13:21:56 - started process bptm (17945) 20/05/2015 13:21:56 - requesting resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 13:22:00 - Info bptm(pid=17945) start backup 20/05/2015 13:22:00 - granted resource C00356 20/05/2015 13:22:00 - granted resource IBM.ULT3580-TD5.002 20/05/2015 13:22:00 - granted resource s-sg-infr-nba01-hcart2-robot-tld-0-SLP 20/05/2015 13:22:01 - Info bpdm(pid=17954) started 20/05/2015 13:22:01 - started process bpdm (17954) 20/05/2015 13:22:01 - Info bpdm(pid=17954) reading backup image 20/05/2015 13:22:01 - Info bptm(pid=17945) Waiting for mount of media id C00356 (copy 2) on server s-sg-infr-nba01. 20/05/2015 13:22:01 - Info bpdm(pid=17954) using 512 data buffers 20/05/2015 13:22:01 - started process bptm (17945) 20/05/2015 13:22:01 - Info bpdm(pid=17954) requesting nbjm for media 20/05/2015 13:22:01 - mounting C00356 20/05/2015 13:22:01 - Info bptm(pid=17945) INF - Waiting for mount of media id C00356 on server s-sg-infr-nba01 for writing. 20/05/2015 13:22:01 - requesting resource @aaaah 20/05/2015 13:22:01 - granted resource MediaID=@aaaah;DiskVolume=PureDiskVolume;DiskPool=dp_disk_s-sg-infr-nba01;Path=PureDiskVolume;StorageServer=s-sg-infr-nba01;MediaServer=s-sg-infr-bck01.fehem.net 20/05/2015 13:22:04 - begin reading 20/05/2015 13:22:29 - Info bptm(pid=17945) media id C00356 mounted on drive index 5, drivepath /dev/nst1, drivename IBM.ULT3580-TD5.002, copy 2 20/05/2015 13:30:58 - end reading; read time: 0:08:54 20/05/2015 13:30:58 - begin reading 20/05/2015 13:33:33 - end reading; read time: 0:02:35 20/05/2015 13:33:33 - begin reading 20/05/2015 13:33:37 - Info bptm(pid=17945) waited for full buffer 7213 times, delayed 7707 times 20/05/2015 13:33:40 - end reading; read time: 0:00:07 20/05/2015 13:33:40 - Info bpdm(pid=17954) completed reading backup image 20/05/2015 13:33:41 - Error bpduplicate(pid=4720) Duplicate of backupid exchange-dag_1431963050 failed, socket open failed (21). 20/05/2015 13:33:41 - Error bpduplicate(pid=4720) Status = successfully duplicated 1 of 2 images. 20/05/2015 13:33:41 - Error bpduplicate(pid=4720) Status = the requested operation was partially successful. 20/05/2015 13:33:41 - end Duplicate; elapsed time: 0:43:13 20/05/2015 13:33:41 - Error bptm(pid=17945) unable to read bpbrm/bpduplicate message, network read error (errno = Connection reset by peer) 20/05/2015 13:33:41 - Error bpdm(pid=17954) unable to read bpbrm/bpduplicate message, network read error (errno = Connection reset by peer) 20/05/2015 13:33:41 - Info bptm(pid=17945) EXITING with status 23 <---------- 20/05/2015 13:33:41 - Info s-sg-infr-nba01(pid=17954) StorageServer=PureDisk:s-sg-infr-nba01; Report=PDDO Stats for (s-sg-infr-nba01): read: 75826776 KB, CR received: 59831989 KB, CR received over FC: 0 KB, dedup: 0.0% the requested operation was partially successful (1) The job was successfully completed, but some files may have been busy or inaccessible. See the problems report or the client's logs for more details.
About Supported Configurations for MS Sharepoint on Netbackup
Hi all, Recently, our company has implemented MS Sharepoint system for file sharing purpose. We have another centralized backup server implemeted using Netbackup 7.6. The mentioned Sharepoint system is also made use of the centralized backup server to backup the database records. However, the implementation vendor reported that database recovery cannot perform in transactional base but only a full recovery at the time of backup can be done. Our configuration is listed below for reference. Backup Server: Windows 2012 Server with Netbackup 7.6 MS Sharepoint system: Sharepoint 2013 with SQL Server 2014 I have found a footnote under NetBackup Database and Application Agent Compatibility List which state as follows. "SharePoint databases are not supported if the SharePoint server is configured to use a SQL Server 2014 instance." I just want to know if there is any workaround so that transactional base recovery for the above configuration can be done. Otherwise, is there any roadmap on the mentioned Sharepoint configuration to be supported in the future release of Netbackup? Mark LeungRestore of Exchange 2010 item to Exchange 2013
We're planning to move to an Exchange 2013 DAG from our current Exchange 2010 CAS/Mailbox server setup. We're using NBU 7.5.0.7 with GRT to backup our Exchange 2010 environment; it's working great. I see from this forum post https://www-secure.symantec.com/connect/forums/exchange-2013-and-grt that as of NBU 7.6.0.3 and up, Exchange 2013 is supported with GRT (allowing for single-item restores). My question is, has anyone been able to restore from an Exchange 2010 GRT backup into an Exchange 2013 (will also be GRT-based) environment? I thought I would ask here before contacting support. Thanks in advance, Michelle
Sharepoint backup/Restore failure Cannot open database "Bdc_Service_DB_"
Friends, NBU 7.5.0.6 Master Windows 2008 R2 64Bit NBU 7.5.0.6 Media Linux Suse 10 SP 2 Sharepoint 2010 W2K8 FEWS+Index Server SQL Server 2008 on W2K8 Backend Server Sharepoint DB Backups running successfully on production setup both full and GRT. Problem: trying to restore the live backups to DR site. DR sharepoint server is all in one running both FEWS and BE SQL Server. followed this technote but no joy 1: http://www.symantec.com/business/support/index?page=content&id=TECH163248 2: can't see the microsoft shrepoint resources in the BAR gui. getting the following error in the SPSWrapper00 logs 0f38] 07/25/14 15:21:01 Total infowrapper counts 1 [0f38] 07/25/14 15:21:01 Application name is Business Data Connectivity Service [0f38] 07/25/14 15:21:01 Application services db name is Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079 [0f38] 07/25/14 15:21:01 Exception is Cannot open database "Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079" requested by the login. The login failed. Login failed for user 'IX\netbackup'. [0f38] 07/25/14 15:21:01 Exception in getting ServerInstanceName using ConnectionString Data Source=MTSHAREPOINT\SharePoint;Initial Catalog=Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079;Integrated Security=True;Enlist=False;Connect Timeout=15 [0f38] 07/25/14 15:21:01 Exception is Cannot open database "Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079" requested by the login. The login failed. Login failed for user 'IX\netbackup'. I have stopped the business data continuity service and application service but no joy. Questions: 1: how can i get rid of this error so that sharepoint resources become visible in the BAR gui? i can tell you for sure there are no permission issues on the account as the same account is being used on the production. 2: does the sharepoint resoources have to be visible for the restore? i would of thought yes because if they are not visible backup wont work so same goes for restore? any suggestion would highly be appreicated.
