VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved30KViews2likes9Comments
NBU status: 2074, EMM status: Disk volume is down
Environment: Master Server: Windows Server 2008 R2 Media Server: Windows Server 2008 R2 EMC DataDomain All the backup jobs including catalog backup jobs are running successfully. I tried to cleanup all expired images with bpimage -cleanup –allclients due to increase in size of image catalog and got error. The media server mentioned in the below job details has two storage units, one local drive as basic disk storage unit stu-03 and other one is data domain network drive \\dd670\backup Both storage units are accessible and backup jobs are running fine on them. What could be the cause and possible solutions of this error? Ran bpimage -cleanup –allclients and got the following error from the job details: 1/24/2014 12:49:40 AM - Info nbdelete(pid=7024) deleting expired images. Media Server: enp-en01.xxx.com Media: @aaaaJ 1/24/2014 12:49:40 AM - Error nbdelete(pid=7024) Cannot obtain resources for this job : error [2074] the requested operation was partially successful(1) The job was successfully completed, but some files may have been busy or unaccessible. See the problems report or the client's logs for more details. 1/24/2014 12:49:40 AM - requesting resource @aaaaJ 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is down 1/24/2014 12:49:40 AM - Error nbjm(pid=5692) NBU status: 2074, EMM status: Disk volume is downSolved30KViews1like4Comments
Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks28KViews1like11Commentsunable to log into Netbackup GUI (Status 526)
Hi all i'm having trobule with a box running redhat 5 and netbackup 7.1, i cant connect to the GUI, i get unbale to log in, status 526 From the log, i get the below - Connecting to vnetd service over PBX port = 1556 ServerInterface:Logon:Exception encountered null ServerInterface:Logon - Initial host:null, Current host:valorum, PBX port:1556 Can not connect to the NB-Java authentication service on valorum on port 1556. Exception: vrts.common.server.CantConnectToAuthServViaVNETDException Any ideas what can cause this? ThanksSolved22KViews3likes7Comments
Backup exec management services could not be started
I am facing issue in Backup exec 2014. When i started backup exec console then it first ask for credentials and then gave an error "Backup exec management services could not be started. Backup exec database is offline, turn it online then restart backup exec services" i re install the backup exec 2014 but still have the same issue. Platform consist of Windows server 2008 R2 standard and also it consist of SQL 2008 which is running by client but Backup exec database use its built in database.Solved22KViews1like14CommentsUnable to connect to the selected NetBackup host "masterserver.xxx.com"
Hi All, Windows 2000 (Service Pack 4) X86 Family 6 Model 10 Sepping NBU Master server version 6.5.6 NetBackup console is not opening, giving below error. Unable to connect to the selected NetBackup host "masterserver.xxx.com" 1. Make sure the user "admin" has privileges on the host. 2. Make sure the local host is...... and some more points, can be find in attached screen shot. Below is what I tried..... 1) Restart the services, Console opens...but after some time getting same error. 2) During bpdown, failed to stop some demon. Killed them manually. 3) Not able to stop bpdbm, getting permission issue. 4) Name resolution ok (nslookup, reverse nslookup) 5) Checked in registery, name is defined accurately. 6) Put the entry in HOSTS file. Please assist if anyone has faced such issue earlier. I know that 6.5.6 is EOL, but cant upgrade to 7.x as server is windows2000. But still the things are in progress to upgrade the hardware first then the NBU.Solved19KViews2likes11Commentsbphdb exit status = 6: the backup failed to back up the requested files
Hello, we are getting error on Below RMAN Backup.. please suggest what is the issue with it and what can be done to resolve it..Thanks Master Serve is Windows 2008, Netbackup 7.5 client is Windows Windows 2003 Oracle 10G R1 below is Netbackup error.. 06/08/2014 16:55:46 - connecting 06/08/2014 16:55:49 - Info bpbrm (pid=13560) starting bphdb on client 06/08/2014 16:55:49 - connected; connect time: 0:00:00 06/08/2014 16:55:52 - Info bphdb (pid=5448) Backup started 06/08/2014 16:55:54 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - Script <"C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypp.cmd"> failed with status: <1> 06/08/2014 16:55:56 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - Script <"C:\Program Files\Veritas\NetBackup\scripts\hot_database_backup_hypdb.cmd"> failed with status: <1> 06/08/2014 16:55:56 - Error bpbrm (pid=13560) from client tmgsdhypprddb: ERR - bphdb exit status = 6: the backup failed to back up the requested files 06/08/2014 16:55:59 - Info bphdb (pid=5448) done. status: 6: the backup failed to back up the requested files 06/08/2014 16:55:59 - end writing the backup failed to back up the requested files (6)Solved18KViews1like8Comments
Status Code 59 - Access to the Client was not Allowed
I am receiving this error on a backup job. This is Netbackup 7.1 running on a Windows Server 2008 R2 Enterprise 64bit system. I have looked through other forum discussions on this, but haven't had any luck trying to fix this myself. Below are the job details and i have attached the BPCD log for futher assistance. 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) starting backup job (jobid=200208) for client polaris.daykimball.org, policy PACS.Images.on.Polaris, schedule Incremental 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=200208, request id:{206810E6-849C-4247-B470-B23EC1D76E6E}) 5/23/2012 3:41:52 PM - requesting resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:53 PM - granted resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource 000079 5/23/2012 3:41:53 PM - granted resource IBM.ULTRIUM-TD2.000 5/23/2012 3:41:53 PM - granted resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:53 PM - estimated 0 Kbytes needed 5/23/2012 3:41:53 PM - begin Parent Job 5/23/2012 3:41:53 PM - begin Snapshot, Start Notify Script 5/23/2012 3:41:53 PM - Info RUNCMD(pid=15820) started 5/23/2012 3:41:53 PM - Info RUNCMD(pid=15820) exiting with status: 0 Status 0 5/23/2012 3:41:53 PM - end Snapshot, Start Notify Script; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Step By Condition Status 0 5/23/2012 3:41:53 PM - end Snapshot, Step By Condition; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Stream Discovery Status 0 5/23/2012 3:41:53 PM - end Snapshot, Stream Discovery; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Read File List Status 0 5/23/2012 3:41:53 PM - end Snapshot, Read File List; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Create Snapshot 5/23/2012 3:41:55 PM - started process bpbrm (2552) 5/23/2012 3:41:56 PM - Error bpbrm(pid=2552) bpcd on polaris.daykimball.org exited with status 59: access to the client was not allowed 5/23/2012 3:41:56 PM - Info bpbrm(pid=2552) polaris.daykimball.org is the host to backup data from 5/23/2012 3:41:56 PM - end writing Status 59 5/23/2012 3:41:56 PM - end Snapshot, Create Snapshot; elapsed time: 00:00:03 5/23/2012 3:41:56 PM - begin Snapshot, Stop On Error Status 0 5/23/2012 3:41:56 PM - end Snapshot, Stop On Error; elapsed time: 00:00:00 5/23/2012 3:41:56 PM - begin Snapshot, Delete Snapshot On Exit Status 0 5/23/2012 3:41:56 PM - end Snapshot, Delete Snapshot On Exit; elapsed time: 00:00:00 5/23/2012 3:41:56 PM - begin Snapshot, End Notify Script 5/23/2012 3:41:56 PM - Info RUNCMD(pid=34688) started 5/23/2012 3:41:56 PM - Info RUNCMD(pid=34688) exiting with status: 0 Status 0 5/23/2012 3:41:56 PM - end Snapshot, End Notify Script; elapsed time: 00:00:00 Status 59 5/23/2012 3:41:56 PM - end Parent Job; elapsed time: 00:00:03 access to the client was not allowed(59)Solved18KViews1like3Comments
Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1: Backup- E: DataV-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). When runningVSSADMIN LIST WRITERS - command from prompt I'm given the following output: C:\Documents and Settings\xxx>VSSADMIN LIST WRITERS vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0} State: [10] Failed Last error: Retryable error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a} State: [1] Stable Last error: No error The following warnings and errors is shown in Windows Event Viewer: Event Type: Error Event Source: ESENT Event Category: ShadowCopy Event ID: 2004 Date: 09-10-2012 Time: 01:09:09 User: N/A Computer: SERVER01 Description: wins (3316) Shadow copy 13 time-out (70000 ms). Event Type: Warning Event Source: VSS Event Category: None Event ID: 12290 Date: 09-10-2012 Time: 01:09:29 User: N/A Computer: SERVER01 Description: Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402. hr = 0x00000000. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 09-10-2012 Time: 06:20:30 User: N/A Computer: SERVER01 Description: Backup Exec Alert: Job Failed (Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status. The data selected for the backup-job is pure files and System State. The server is a Windows Small Business Server 2003 SP2.Solved18KViews1like12Comments
(4207) Could not fetch snapshot metadata or state files
hi all please i have netbackup 7.6 on linux wend i tried to backup exchanche i have this error : ²20 avr. 2015 15:47:58 - Info nbjm (pid=4200) starting backup job (jobid=50468) for client mailboxeserver, policy nbuexchgdb, schedule exchbckweek_full 20 avr. 2015 15:47:58 - Info nbjm (pid=4200) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=50468, request id:{9E269824-E774-11E4-A3F7-99E7FA481C67}) 20 avr. 2015 15:47:58 - requesting resource studskfile 20 avr. 2015 15:47:58 - requesting resource netbserver.NBU_CLIENT.MAXJOBS.mailboxeserver 20 avr. 2015 15:47:58 - requesting resource netbserver.NBU_POLICY.MAXJOBS.nbuexchgdb 20 avr. 2015 15:47:58 - granted resource netbserver.NBU_CLIENT.MAXJOBS.mailboxeserver 20 avr. 2015 15:47:58 - granted resource netbserver.NBU_POLICY.MAXJOBS.nbuexchgdb 20 avr. 2015 15:47:58 - granted resource MediaID=@aaaay;DiskVolume=PureDiskVolume;DiskPool=MSDP01;Path=PureDiskVolume;StorageServer=netbserver;MediaServer=netbserver 20 avr. 2015 15:47:58 - granted resource studskfile 20 avr. 2015 15:47:58 - estimated 298453854 kbytes needed 20 avr. 2015 15:47:58 - begin Parent Job 20 avr. 2015 15:47:58 - begin Snapshot: Start Notify Script 20 avr. 2015 15:47:58 - Info RUNCMD (pid=3052) started 20 avr. 2015 15:47:58 - Info RUNCMD (pid=3052) exiting with status: 0 Operation Status: 0 20 avr. 2015 15:47:58 - end Snapshot: Start Notify Script; elapsed time 0:00:00 20 avr. 2015 15:47:58 - begin Snapshot: Step By Condition Operation Status: 0 20 avr. 2015 15:47:58 - end Snapshot: Step By Condition; elapsed time 0:00:00 20 avr. 2015 15:47:58 - begin Snapshot: Stream Discovery Operation Status: 0 20 avr. 2015 15:47:58 - end Snapshot: Stream Discovery; elapsed time 0:00:00 20 avr. 2015 15:47:58 - begin Snapshot: Read File List Operation Status: 0 20 avr. 2015 15:47:58 - end Snapshot: Read File List; elapsed time 0:00:00 20 avr. 2015 15:47:58 - begin Snapshot: Create Snapshot 20 avr. 2015 15:47:59 - started process bpbrm (pid=3058) 20 avr. 2015 15:48:03 - Info bpbrm (pid=3058) mailboxeserver is the host to backup data from 20 avr. 2015 15:48:03 - Info bpbrm (pid=3058) reading file list for client 20 avr. 2015 15:48:03 - Info bpbrm (pid=3058) start bpfis on client 20 avr. 2015 15:48:03 - Info bpbrm (pid=3058) Starting create snapshot processing 20 avr. 2015 15:48:04 - Info bpfis (pid=9244) Backup started 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - vfm_freeze_commit: method: VSS_Writer, type: FIM, function: VSS_Writer_freeze_commit 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - snapshot processing failed, status 156 20 avr. 2015 15:48:31 - Critical bpbrm (pid=3058) from client mailboxeserver: FTL - snapshot creation failed - SNAPSHOT_NOTIFICATION::PostSnapshot failed., status 130 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - NEW_STREAM0 is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - Microsoft Information Store:\mtnmailbox1\ is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - NEW_STREAM1 is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - Microsoft Information Store:\mtnmailbox2\ is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - NEW_STREAM2 is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - Microsoft Information Store:\mtnmailbox3\ is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - NEW_STREAM3 is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - Microsoft Information Store:\mtnmailbox3bis\ is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - NEW_STREAM4 is not frozen 20 avr. 2015 15:48:31 - Warning bpbrm (pid=3058) from client mailboxeserver: WRN - Microsoft Information Store:\mtnmailbox5\ is not frozen 20 avr. 2015 15:48:31 - Info bpfis (pid=9244) done. status: 130 20 avr. 2015 15:48:31 - end Snapshot: Create Snapshot; elapsed time 0:00:33 20 avr. 2015 15:48:31 - Info bpfis (pid=9244) done. status: 130: system error occurred 20 avr. 2015 15:48:31 - end writing Operation Status: 130 20 avr. 2015 15:48:31 - end Parent Job; elapsed time 0:00:33 20 avr. 2015 15:48:31 - begin Snapshot: Stop On Error Operation Status: 0 20 avr. 2015 15:48:31 - end Snapshot: Stop On Error; elapsed time 0:00:00 20 avr. 2015 15:48:31 - begin Snapshot: Delete Snapshot 20 avr. 2015 15:48:31 - started process bpbrm (pid=3261) 20 avr. 2015 15:48:32 - Info bpbrm (pid=3261) Starting delete snapshot processing 20 avr. 2015 15:48:34 - Info bpfis (pid=9560) Backup started 20 avr. 2015 15:48:34 - Critical bpbrm (pid=3261) from client mailboxeserver: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.mailboxeserver_1429544878.1.0 20 avr. 2015 15:48:35 - Info bpfis (pid=9560) done. status: 4207 20 avr. 2015 15:48:35 - end Snapshot: Delete Snapshot; elapsed time 0:00:04 20 avr. 2015 15:48:35 - Info bpfis (pid=9560) done. status: 4207: Could not fetch snapshot metadata or state files 20 avr. 2015 15:48:35 - end writing Operation Status: 4207 20 avr. 2015 15:48:35 - begin Snapshot: End Notify Script 20 avr. 2015 15:48:35 - Info RUNCMD (pid=3266) started 20 avr. 2015 15:48:35 - Info RUNCMD (pid=3266) exiting with status: 0 Operation Status: 0 20 avr. 2015 15:48:35 - end Snapshot: End Notify Script; elapsed time 0:00:00 Operation Status: 4207 Could not fetch snapshot metadata or state files (4207) please i need help !!!Solved17KViews0likes1Comment
Ready; No idle devices are available
I'm new to Symantec Backup Exec as I've taken over the duties of someone else that left the company. The problem that I'm having is I can't get Backup Exec to backup anything, not to tape, not to a shared drive, etc.. Logically I would have thought the issue was that the previous employee had used his account for all Symantec functions, I was able to change his account information for all the services and the connection to the server. Everything appears to be fine, I'm able to do a Test Run without any problems but when I go to do a backup I don't receive any alerts I just get a message that says "Ready; No Idle devices are available". Same result no matter where I try to backup to. Anyone seen this before, have any suggestions of how I can fix it? We're using Backup Exec 2012 S1a. Thanks