Select for Restore - unable to obtain list of files using specified search criteria
We have seen this issue posted already but have been unable to resolve. We are using NetBackup v7.6.1 and have a couple of policies (with identical settings) to backup a number of VMware virtual machines. One of the policies has a problem when trying to select individual files for restore. Like the others it is type VMware and 'Enable file recovery from VM backup" is selected/ticked. Backups are completing successfully every day for this policy (snapshot and backup), over 1.1 gb written). We only get this error for this policy and only when selecting "Restore from Normal Backup..." Restore from "Virtual Machine Backup" does not produce the error and displays results under "Contents" pain without any error. Policy config: C:\Program Files\Veritas\NetBackup\bin\admincmd>bppllist Test_VM_CBT -L Policy Name: Test_VM_CBT Options: 0x0 template: FALSE audit_reason: ? Names: (none) Policy Type: VMware (40) Active: yes Effective date: 13/07/2015 11:46:28 File Restore Raw: yes Block Incremental: yes Application Consistent: yes Mult. Data Stream: no Perform Snapshot Backup: yes Snapshot Method: VMware_v2 Snapshot Method Arguments: Virtual_machine_backup=2,disable_quiesce=0,drive_selection=0,enable_vCloud=0,exclude_swap=1,file_system_optimizat ion=1,ignore_irvm=1,multi_org=0,nameuse=1,post_events=1,rHz=10,rLim=10,rTO=0,serverlist=,skipnodisk=0,snapact=2,trantype=nbd:nbdssl:hotadd:s an Perform Offhost Backup: yes Backup Copy: 0 Use Data Mover: no Data Mover Type: -1 Use Alternate Client: no Alternate Client Name: dnetbackup1.clients.local Use Virtual Machine: 1 Hyper-V Server Name: (none) Enable Instant Recovery: no Policy Priority: 0 Max Jobs/Policy: 8 Disaster Recovery: 0 Collect BMR Info: no Keyword: (none specified) Data Classification: - Residence is Storage Lifecycle Policy: no Client Encrypt: no Checkpoint: no Residence: dnetbackup1_DiskPool-stu Volume Pool: NetBackup Server Group: *ANY* Granular Restore Info: no Exchange Source attributes: no Exchange DAG Preferred Server: (none defined) Application Discovery: no Discovery Lifetime: 28800 seconds ASC Application and attributes: (none defined) Generation: 17 Ignore Client Direct: no Enable Metadata Indexing: no Index server name: NULL Use Accelerator: yes Client/HW/OS/Pri/DMI/CIT: DACSDB.clients.local vmx-08 windows7Server64Guest 0 0 0 0 ? Include: ALL_LOCAL_DRIVES Schedule: Full_CBT Type: FULL (0) Frequency: 1 day(s) (86400 seconds) Excluded Dates---------- No specific exclude dates entered No exclude days of week entered Retention Level: 0 (1 week) u-wind/o/d: 0 0 Incr Type: DELTA (0) Alt Read Host: (none defined) Max Frag Size: 0 MB PFI Recovery: 0 Maximum MPX: 1 Number Copies: 1 Fail on Error: 0 Residence: (specific storage unit not required) Volume Pool: (same as policy volume pool) Server Group: (same as specified for policy) Residence is Storage Lifecycle Policy: 0 Schedule indexing: 0 Daily Windows: Day Open Close W-Open W-Close Sunday 000:00:00 000:00:00 Monday 018:00:00 028:05:00 042:00:00 052:05:00 Tuesday 018:00:00 028:05:00 066:00:00 076:05:00 Wednesday 018:00:00 028:05:00 090:00:00 100:05:00 Thursday 018:00:00 028:05:00 114:00:00 124:05:00 Friday 018:00:00 028:05:00 138:00:00 148:05:00 Saturday 000:00:00 000:00:00
Exchange 2013 GRT Calendar Item Restore issue
We've noticed that it is impossible to restore a Calendar Item which was in Inbox during backup. Following error is generated in restore log: 11:45:27 (823236.001) MNR - error writing file: %1 11:45:46 (823236.001) INF - GRE EXITING WITH STATUS = 0 11:45:46 (823236.001) Status of restore from copy 1 of image created 2015-10-04 18:09:22 = the requested operation was partially successful 11:45:46 INF - Server status = 1 11:45:46 (823236.001) INF - GRE RESTORED 4 OF 5 FILES SUCCESSFULLY 11:45:46 (823236.001) INF - GRE KEPT 0 EXISTING FILES 11:45:46 (823236.001) INF - GRE PARTIALLY RESTORED 1 FILES 11:45:46 (823236.xxx) INF - Status = the requested operation was partially successful. 11:45:46 INF - Server status = 5 11:45:46 Status of restore from copy 1 of image created 2015-10-04 18:09:22 = the restore failed to recover the requested files 11:45:46 The following files/folders were not restored: 11:45:46 UTF - /Microsoft Exchange Database Availability Groups/dag11/Microsoft Information Store/DB1GASP01/Database/****/Top of Information Store/Skrzynka odbiorcza/**** 11:45:47 (823235.xxx) INF - Status = the restore failed to recover the requested files. And in the ncfgre: 0,51216,158,352,122,1444035291376,46056,7376,0:,78:FS_CloseObj() Failure! Extended Error unknown (-536870147) (../Object.cpp:206),15:Object::close(),1 No other errors in another logs have been noticed. Restore has been done to original location. Another mails from this backup image are being restored successfully. Only Calendar Items from Inbox are causing problems. NetBackup version is 7.6.0.3 and Exchange is 2013 (Version 15.0 Build 1076.9).
nblbc.exe crashes on GRT proxy server
Our backup server is NBU Enterprise Server, 7.6.1.1 running on OEL 5.10 (x86), on a Dell R620 server and Dell PVTL 2000 (2 x LTO5 drives), each drive connectedvia 6Gps SAS interface to NBU server. We have two Exchange 2010 servers, each DB over 420GB. I put in place a Windows 2008 R2 proxy server to handle the duplication of images fromdisk (BasicDisk) to tape.We need the GRT option as we need to recover items at a message level. What has been erratically happening is that duplication jobs fail with a 191 status and the dreaded: 04/23/2015 09:08:17 - Error bpduplicate (pid=828) db_IMAGE() failed: database system error (220) 04/23/2015 09:08:17 - Error bpduplicate (pid=828) Status = no images were successfully processed. 04/23/2015 09:08:17 - Error bpduplicate (pid=828) Duplicate of backupid exch2_1429750827 failed, database system error (220). 04/23/2015 09:08:17 - Error bpduplicate (pid=828) Status = no images were successfully processed. So... been going back and forth with support and for some reason, today I looked at the Application Log on the proxy server and found: Error 4/23/2015 9:08:16 AM Application Error 1005 (100) Error 4/23/2015 9:08:16 AM Application Error 1000 (100) Error 4/23/2015 9:08:16 AM Application Error 1000 (100) The detail of the Event ID 1000 is: Log Name: Application Source: Application Error Date: 4/23/2015 9:08:16 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GRTPROXY Description: Faulting application name: nblbc.exe, version: 7.601.115.212, time stamp: 0x54dcea59 Faulting module name: ntdll.dll, version: 6.1.7601.18247, time stamp: 0x521eaf24 Exception code: 0xc0000006 Fault offset: 0x0000000000029c42 Faulting process id: 0x5a0 Faulting application start time: 0x01d07dbf25e6bbf8 Faulting application path: C:\Program Files\Veritas\NetBackup\bin\nblbc.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: cd8dd4eb-e9b9-11e4-8564-0050568d7352 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-23T13:08:16.000000000Z" /> <EventRecordID>4001</EventRecordID> <Channel>Application</Channel> <Computer>GRTPROXY</Computer> <Security /> </System> <EventData> <Data>nblbc.exe</Data> <Data>7.601.115.212</Data> <Data>54dcea59</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.18247</Data> <Data>521eaf24</Data> <Data>c0000006</Data> <Data>0000000000029c42</Data> <Data>5a0</Data> <Data>01d07dbf25e6bbf8</Data> <Data>C:\Program Files\Veritas\NetBackup\bin\nblbc.exe</Data> <Data>C:\Windows\SYSTEM32\ntdll.dll</Data> <Data>cd8dd4eb-e9b9-11e4-8564-0050568d7352</Data> </EventData> </Event> And the detail of EventID 1005 is as follows: Log Name: Application Source: Application Error Date: 4/23/2015 9:08:16 AM Event ID: 1005 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GRTPROXY Description: Windows cannot access the file for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program NetBackup because of this error. Program: NetBackup File: The error value is listed in the Additional Data section. User Action 1. Open the file again. This situation might be a temporary problem that corrects itself when the program runs again. 2. If the file still cannot be accessed and - It is on the network, your network administrator should verify that there is not a problem with the network and that the server can be contacted. - It is on a removable disk, for example, a floppy disk or CD-ROM, verify that the disk is fully inserted into the computer. 3. Check and repair the file system by running CHKDSK. To run CHKDSK, click Start, click Run, type CMD, and then click OK. At the command prompt, type CHKDSK /F, and then press ENTER. 4. If the problem persists, restore the file from a backup copy. 5. Determine whether other files on the same disk can be opened. If not, the disk might be damaged. If it is a hard disk, contact your administrator or computer hardware vendor for further assistance. Additional Data Error value: C00000C4 Disk type: 0 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="49152">1005</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-23T13:08:16.000000000Z" /> <EventRecordID>4003</EventRecordID> <Channel>Application</Channel> <Computer>GRTPROXY</Computer> <Security /> </System> <EventData> <Data> </Data> <Data>NetBackup</Data> <Data>C00000C4</Data> <Data>0</Data> </EventData> </Event> Any ideas as to why nblbc would crash?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 implementedMS Sharepoint system for file sharing purpose. We have anothercentralized backup server implemeted using Netbackup 7.6. The mentionedSharepoint system is also madeuse of thecentralized backup server to backup the database records. However, the implementation vendor reported that database recovery cannot perform intransactional basebut only a full recovery at the time of backup can be done. Our configuration is listed below for reference. Backup Server: Windows 2012 Server withNetbackup 7.6 MS Sharepoint system: Sharepoint 2013 with SQL Server 2014 I have found afootnote underNetBackup 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 thattransactional base recovery forthe above configurationcan 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 posthttps://www-secure.symantec.com/connect/forums/exchange-2013-and-grt that asof 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