Unable to backup sharepoint
Hi everybody! I'm having troubles while backing up Sharepoint 2010 over Windows Server 2008 R2. The job ends with status 2 and don't backup anything. This is the end of the detailed status of the job. Also I attach the bpresolver log, where I believe the problem is. I really can't see where is the problem, I followed all the steps from the Sharepoing GRT guide (HOWTO73100) but the error still.. Hope somebody can help me with this. Thansk a lot in advance.Solved5.6KViews0likes14CommentsNDMP error 99
Hi, Since fewdays, I have some trouble on my NDMP backups. My backup selection is shared between many streams. All full backup are OK, but some of incr backup failswith status 99. Apparently, the level 0 dump is post-dated, and I have this error : "Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump." 14/02/2016 22:36:37 - connecting 14/02/2016 22:36:37 - connected; connect time: 00:00:00 14/02/2016 22:36:38 - mounting CAD126 14/02/2016 22:38:15 - Info bptm(pid=17364) media id CAD126 mounted on drive index 2, drivepath nrst1a, drivename HP.ULTRIUM5-SCSI.002, copy 1 14/02/2016 22:38:15 - mounted; mount time: 00:01:37 14/02/2016 22:38:20 - Info ndmpagent(pid=18976) bstou103: SCSI: TAPE READ: short read for nrst1a 14/02/2016 22:38:21 - positioning CAD126 to file 44 14/02/2016 22:39:35 - Info ndmpagent(pid=18976) bstou103: DUMP: creating "/vol/volpoles/../snapshot_ for_backup.3112" snapshot. 14/02/2016 22:39:35 - positioned CAD126; position time: 00:01:14 14/02/2016 22:39:35 - begin writing 14/02/2016 22:39:37 - Info ndmpagent(pid=18976) bstou103: DUMP: Using subtree dump 14/02/2016 22:39:51 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of this level 1 dump snapshot: Sun Feb 14 22:40:46 2016. 14/02/2016 22:39:52 - Info ndmpagent(pid=18976) bstou103: DUMP: Date of last level 0 dump: Tue Jan 19 04:14:07 2038. 14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Aborting the incremental dump of level (1) because the snapshot specified for this backup is older than the one used in the previous dump. 14/02/2016 22:39:52 - Error ndmpagent(pid=18976) bstou103: DUMP: Dump failed to initialize. 14/02/2016 22:39:53 - Error ndmpagent(pid=18976) bstou103: DUMP: DUMP IS ABORTED 14/02/2016 22:39:54 - Info ndmpagent(pid=18976) bstou103: DUMP: Deleting "/vol/volpoles/../snapshot_ for_backup.3112" snapshot. 14/02/2016 22:39:56 - Error ndmpagent(pid=18976) bstou103: DATA: Operation terminated: EVENT: INTERNAL ERROR (for /vol/volpoles/qtpoles/PRP/ SERIS) 14/02/2016 22:39:56 - Error ndmpagent(pid=18976) NDMP backup failed, path = /vol/volpoles/qtpoles/PRP/ SERIS 14/02/2016 22:39:57 - Error bptm(pid=17364) none of the NDMP backups for client bstou103 completed successfully 14/02/2016 22:40:23 - Info bptm(pid=17364) EXITING with status 99 <---------- 14/02/2016 22:40:24 - end writing; write time: 00:00:49 NDMP backup failure(99) Any idea ? My version is 7.5.0.4 Thanks !Solved4.6KViews0likes22Commentssnapshot error encountered (156)
Hello Friends, i am facing an issue in VMWare VSphereBackup issue with the error code snampshot error encountered - 156. Master Server :- 7.6.1.1 / Windows 2008 Enterprise 64 bit Media Server:- 7.6.1.1/Red Hat Linux VMWare : - VMWare VSphere 6.0 Job Details: - 5/25/2016 1:31:05 PM - Info nbjm(pid=6932) starting backup job (jobid=872704) for client pbad-vc, policy VMWare-vCenter, schedule Daily 5/25/2016 1:31:05 PM - Info nbjm(pid=6932) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=872704, request id:{02BE2026-FC59-47A1-A179-F4F9CA96A5E3}) 5/25/2016 1:31:05 PM - requesting resource pbad_fsmedia_Dedup_STU 5/25/2016 1:31:05 PM - requesting resource pbad-netbackup.pbad.sbg.com.sa.NBU_CLIENT.MAXJOBS.pbad-vc 5/25/2016 1:31:05 PM - requesting resource pbad-netbackup.pbad.sbg.com.sa.NBU_POLICY.MAXJOBS.VMWare-vCenter 5/25/2016 1:31:05 PM - granted resource pbad-netbackup.pbad.sbg.com.sa.NBU_CLIENT.MAXJOBS.pbad-vc 5/25/2016 1:31:05 PM - granted resource pbad-netbackup.pbad.sbg.com.sa.NBU_POLICY.MAXJOBS.VMWare-vCenter 5/25/2016 1:31:05 PM - granted resource MediaID=@aaaay;DiskVolume=PureDiskVolume;DiskPool=pbad_fsmedia_Dedup_Pool;Path=PureDiskVolume;StorageServer=pbad-fsmedia.pbad.sbg.com.sa;MediaServer=pbad-fsmedia.pbad.sbg.com.sa 5/25/2016 1:31:05 PM - granted resource pbad_fsmedia_Dedup_STU 5/25/2016 1:31:05 PM - estimated 0 Kbytes needed 5/25/2016 1:31:05 PM - begin Parent Job 5/25/2016 1:31:05 PM - begin VMware, Start Notify Script 5/25/2016 1:31:05 PM - started 5/25/2016 1:31:06 PM - Info RUNCMD(pid=15444) started 5/25/2016 1:31:07 PM - Info RUNCMD(pid=15444) exiting with status: 0 Status 0 5/25/2016 1:31:07 PM - end VMware, Start Notify Script; elapsed time: 0:00:02 5/25/2016 1:31:07 PM - begin VMware, Step By Condition Status 0 5/25/2016 1:31:07 PM - end VMware, Step By Condition; elapsed time: 0:00:00 5/25/2016 1:31:07 PM - begin VMware, Read File List Status 0 5/25/2016 1:31:07 PM - end VMware, Read File List; elapsed time: 0:00:00 5/25/2016 1:31:07 PM - begin VMware, Create Snapshot 5/25/2016 1:31:08 PM - started process bpbrm (12023) 5/25/2016 1:33:57 PM - end writing Status 156 5/25/2016 1:33:57 PM - end VMware, Create Snapshot; elapsed time: 0:02:50 5/25/2016 1:33:57 PM - begin VMware, Stop On Error Status 0 5/25/2016 1:33:57 PM - end VMware, Stop On Error; elapsed time: 0:00:00 5/25/2016 1:33:57 PM - begin VMware, Delete Snapshot 5/25/2016 1:33:59 PM - started process bpbrm (13061) 5/25/2016 1:34:01 PM - end writing Status 4207 5/25/2016 1:34:01 PM - end VMware, Delete Snapshot; elapsed time: 0:00:04 5/25/2016 1:34:01 PM - begin VMware, End Notify Script 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) pbad-vc is the host to backup data from 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) reading file list for client 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) start bpfis on client 5/25/2016 1:49:46 PM - Info bpbrm(pid=12023) Starting create snapshot processing 5/25/2016 1:49:48 PM - Info bpfis(pid=12029) Backup started 5/25/2016 1:49:48 PM - snapshot backup of client pbad-vc using method VMware_v2 5/25/2016 1:49:52 PM - Info bpbrm(pid=12023) INF - vmwareLogger: ChangeTracking not supported 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware error received: The operation is not allowed in the current state. 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot processing failed, status 156 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot creation failed, status 156 5/25/2016 1:52:32 PM - Warning bpbrm(pid=12023) from client pbad-vc: WRN - ALL_LOCAL_DRIVES is not frozen 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156 5/25/2016 1:52:32 PM - end VMware, End Notify Script; elapsed time: 0:18:31 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156: snapshot error encountered 5/25/2016 1:52:35 PM - Info bpbrm(pid=13061) Starting delete snapshot processing 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) Backup started 5/25/2016 1:52:35 PM - Critical bpbrm(pid=13061) from client pbad-vc: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.pbad-vc_1464172265.1.0 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207 5/25/2016 1:52:35 PM - end Parent Job; elapsed time: 0:21:30 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207: Could not fetch snapshot metadata or state files 5/25/2016 1:34:01 PM - Info RUNCMD(pid=4756) started 5/25/2016 1:34:02 PM - Info RUNCMD(pid=4756) exiting with status: 0 Status 0 5/25/2016 1:34:02 PM - end Parent Job; elapsed time: 0:02:57 Status 156 5/25/2016 1:34:02 PM - end Parent Job; elapsed time: 0:02:57 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) pbad-vc is the host to backup data from 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) reading file list for client 5/25/2016 1:49:44 PM - Info bpbrm(pid=12023) start bpfis on client 5/25/2016 1:49:46 PM - Info bpbrm(pid=12023) Starting create snapshot processing 5/25/2016 1:49:48 PM - Info bpfis(pid=12029) Backup started 5/25/2016 1:49:48 PM - snapshot backup of client pbad-vc using method VMware_v2 5/25/2016 1:49:52 PM - Info bpbrm(pid=12023) INF - vmwareLogger: ChangeTracking not supported 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - VMware error received: The operation is not allowed in the current state. 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:31 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot processing failed, status 156 5/25/2016 1:52:32 PM - Critical bpbrm(pid=12023) from client pbad-vc: FTL - snapshot creation failed, status 156 5/25/2016 1:52:32 PM - Warning bpbrm(pid=12023) from client pbad-vc: WRN - ALL_LOCAL_DRIVES is not frozen 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156 5/25/2016 1:52:32 PM - end operation 5/25/2016 1:52:32 PM - Info bpfis(pid=12029) done. status: 156: snapshot error encountered 5/25/2016 1:52:35 PM - Info bpbrm(pid=13061) Starting delete snapshot processing 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) Backup started 5/25/2016 1:52:35 PM - Critical bpbrm(pid=13061) from client pbad-vc: cannot open /usr/openv/netbackup/online_util/fi_cntl/bpfis.fim.pbad-vc_1464172265.1.0 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207 5/25/2016 1:52:35 PM - end operation 5/25/2016 1:52:35 PM - Info bpfis(pid=13065) done. status: 4207: Could not fetch snapshot metadata or state files snapshot error encountered (156) Please help me to resolve the above issue.Solved8.4KViews1like24CommentsRestore full folder with permissions to another location
Hello Windows client , drive c:\ have two folders - test1 and test2 . Test2 folder have file aa.txt I want to restore folder test2 with all related folders and files and with same permissions to c:\restore. I expect to find c:restore\test2\aa.txt , but found c:\restore\aa.txt The only way to achive what I want is to restore both folders to c:\restore and than remove folder test1 Is there a easy way to do that ? Regards Asher2.7KViews0likes10CommentsGetting "credentials already exist" when creating Media Server DeDuplication Pool
Hi, I am getting error "credentials already exist" when creating the MSDP. I have attached an iSCSI drive on a media server with letter E:\ and created a folder MSDP in there. For the storage path, i am using e:\MSDP. The error is attached. Hopefully someone has seen this before. Thanks, Sean8.1KViews0likes11CommentsError occurred during initialization. Could not read logging configuration file.
Hi every body, As the title indicates, I have this message on my Media Server which is also the Master Server.(NetBackup 7.0.1) In the bpdm log Here the details : 14:04:33.379 [7760.6476] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:04:33.394 [7760.6476] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172004 -jm 14:04:33.394 [7760.6476] <2> main: Sending [EXIT STATUS 0] to NBJM 14:04:33.394 [7760.6476] <2> bptm: EXITING with status 0 <---------- 14:14:33.382 [6000.8320] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:14:33.382 [6000.8320] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172009 -jm 14:14:33.397 [6000.8320] <2> main: Sending [EXIT STATUS 0] to NBJM 14:14:33.397 [6000.8320] <2> bptm: EXITING with status 0 <---------- 14:24:33.385 [5968.4128] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:24:33.401 [5968.4128] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172014 -jm 14:24:33.401 [5968.4128] <2> main: Sending [EXIT STATUS 0] to NBJM 14:24:33.401 [5968.4128] <2> bptm: EXITING with status 0 <---------- 14:34:33.357 [9932.8988] <16> initialize: Error occurred during initialization. Could not read logging configuration file. 14:34:33.373 [9932.8988] <2> bptm: INITIATING (VERBOSE = 0): -rptdrv -jobid -1401172019 -jm 14:34:33.373 [9932.8988] <2> main: Sending [EXIT STATUS 0] to NBJM This error happened since 2 days. Someone has an idea ? Thank you very much.Solved6.7KViews1like6CommentsNetbackup single file restore from linux
Hi, I am experiencing an issuewhile doingsingle file restore from Linux VM. I am using the following: Netbackup 7.6.0.2 on Windows 2008 server Backup policy - VMware (enabled file recovery) What i am trying to do is restore a single file using Backup, Archive and Restore client on my Master server. I know that restore on the linux VM doesn't work if i don't have an agent installed, that is why the destination of the restore is the master server itself. Nevertheless, my restore is failing momentarily with errors 2820, 2817,2800.The error number depends on the restore policy I am using (VMware, Standard, Flashbackup). VMware policy restore error (2820) FlashBackup-Windows policy restore error (2817) Standard policy restore error (2800) Can anyone help me with this issue? Regards, JanaSolved3.7KViews0likes6CommentsLow Scratch Script
Hello, I am looking for a Script or way to monitor our scratch poolto send an alert(email) when remaining available tapes reach a threshold of 8. We are running NB 7.6.0.1. I am New to the Netbackup world any advice or direction would be appreciated. ThanksSolved2.6KViews2likes7CommentsExchange Backup Failing 'file read failed(13)'
Our Netbackup 7.5.0.5Exchange backups have started failing with 'file read failed(13)' errors. Both servers (Exchange and Netbackup) are running on Server 2008 R2. The mailstores (database & logs)are residing ona Netapp FAS2040 with SnapDrive managing snapshots which are created frequently without error. The Netbackup policy itself is set to perform snapshot backups using VSS Provider Type 1 (System), without a DAG database source, has been backing up without any problems until some Windows updates including SP3 for Exchange 2010 were installed. The job fails as follows: 28/11/2014 10:32:33 - Info nbjm(pid=5940) starting backup job (jobid=186119) for client exchange, policy EXCHANGE, schedule Full_Disc 28/11/2014 10:32:33 - estimated 0 Kbytes needed 28/11/2014 10:32:33 - Info nbjm(pid=5940) started backup (backupid=exchange_1417170753) job for client exchange, policy EXCHANGE, schedule Full_Disc on storage unit NexsanDSU 28/11/2014 10:32:34 - started process bpbrm (484288) 28/11/2014 10:32:40 - Info bpbrm(pid=484288) exchange is the host to backup data from 28/11/2014 10:32:40 - Info bpbrm(pid=484288) reading file list from client 28/11/2014 10:32:40 - connecting 28/11/2014 10:32:43 - Info bpbrm(pid=484288) starting bpbkar32 on client 28/11/2014 10:32:43 - connected; connect time: 00:00:03 28/11/2014 10:33:27 - Info bpbkar32(pid=11548) Backup started 28/11/2014 10:33:27 - Info bptm(pid=484816) start 28/11/2014 10:33:28 - Info bptm(pid=484816) using 262144 data buffer size 28/11/2014 10:33:28 - Info bptm(pid=484816) setting receive network buffer to 1049600 bytes 28/11/2014 10:33:28 - Info bptm(pid=484816) using 30 data buffers 28/11/2014 10:33:29 - Info bptm(pid=484816) start backup 28/11/2014 10:33:30 - Info bptm(pid=484816) backup child process is pid 482596.479660 28/11/2014 10:33:30 - Info bptm(pid=482596) start 28/11/2014 10:33:30 - begin writing 28/11/2014 11:07:53 - Error bpbrm(pid=484288) from client exchange: ERR - Terminating backup. 28/11/2014 11:07:53 - Error bpbrm(pid=484288) from client exchange: ERR - failure reading file: Microsoft Information Store:\1GB Limit Mailbox Database\Logs_1417170539 (BEDS 0x0: ) 28/11/2014 11:08:03 - Error bpbrm(pid=484288) could not send server status message 28/11/2014 11:08:04 - Error bpbrm(pid=484288) cannot send mail to... 28/11/2014 11:08:05 - Info bpbkar32(pid=11548) done. status: 13: file read failed 28/11/2014 11:08:05 - end writing; write time: 00:34:35 file read failed(13) I have checked the VSS Writers on Exchange and all are showing as stable with no errors. The Event Viewer on Exchange shows the following events just before the Netbackupjob fails: Log Name: Application Source: MSExchangeIS Date: 28/11/2014 11:06:35 Event ID: 9606 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: exchange Description: Exchange VSS Writer (instance 8315289c-83fc-4e18-95c6-2f9e76f0f821) has prepared for backup successfully. Log Name: Application Source: SnapManager for Exchange Date: 28/11/2014 11:06:36 Event ID: 200 Task Category: Backup Level: Information Keywords: Classic User: N/A Computer: exchange Description: SnapManager VSS asynchronous DoSnapshotSet operation started. Log Name: Application Source: ESE Date: 28/11/2014 11:06:39 Event ID: 2007 Task Category: ShadowCopy Level: Error Keywords: Classic User: N/A Computer: exchange Description: Information Store (6236) Shadow copy instance 3 aborted. Log Name: Application Source: MSExchangeIS Date: 28/11/2014 11:06:39 Event ID: 9609 Task Category: Exchange VSS Writer Level: Error Keywords: Classic User: N/A Computer: exchange Description: Exchange VSS Writer (instance 8315289c-83fc-4e18-95c6-2f9e76f0f821:3) failed with error code -2403 when preparing for Snapshot. I appreciate this is probably an Exchange issue rather than a Netbackup one, but if anyone has an ideas as to why it is failing I'd be grateful for some help. I have attached some log files, let me know if there is any other information that may help. Thanks1.6KViews0likes3Comments