Netbackup Status 4207 - cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim
We are receiving errors status 4207 and 71. As far as we can tell, the backups are functioning properly. (I was able to restore test files on all drives on this server) See logs below. I have checked to make sure that the C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim location exists and is writable. However, the folder is empty..is that normal? See logs below 1/5/2017 11:30:28 PM - end Parent Job; elapsed time: 0:00:23 1/5/2017 11:30:28 PM - Info nbjm(pid=4748) snapshotid=******************_1483687805 1/5/2017 11:30:28 PM - begin Snapshot, Policy Execution Manager Preprocessed Status 71 1/6/2017 5:16:58 AM - end Snapshot, Policy Execution Manager Preprocessed; elapsed time: 5:46:30 1/6/2017 5:16:58 AM - begin Snapshot, Stop On Error Status 0 1/6/2017 5:16:58 AM - end Snapshot, Stop On Error; elapsed time: 0:00:00 1/6/2017 5:16:58 AM - begin Snapshot, Delete Snapshot 1/6/2017 5:17:00 AM - started process bpbrm (4812) 1/6/2017 5:17:01 AM - Info bpbrm(pid=4812) Starting delete snapshot processing 1/6/2017 5:17:03 AM - Info bpfis(pid=21836) Backup started 1/6/2017 5:17:03 AM - Critical bpbrm(pid=4812) from client *********************: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.*******************_1483687805.1.0 1/6/2017 5:17:03 AM - end writing Status 4207 1/6/2017 5:17:03 AM - end Snapshot, Delete Snapshot; elapsed time: 0:00:05 1/6/2017 5:17:03 AM - begin Snapshot, End Notify Script 1/6/2017 5:17:04 AM - Info bpfis(pid=21836) done. status: 4207 1/6/2017 5:17:04 AM - end Snapshot, End Notify Script; elapsed time: 0:00:01 1/6/2017 5:17:04 AM - Info bpfis(pid=21836) done. status: 4207: Could not fetch snapshot metadata or state files 1/6/2017 5:17:04 AM - Info RUNCMD(pid=7376) started 1/6/2017 5:17:04 AM - Info RUNCMD(pid=7376) exiting with status: 0 Status 0 1/6/2017 5:17:04 AM - end operation Status 71 1/6/2017 5:17:04 AM - end operation None of the files mentioned in the file list exist or may not be accessible(71) 1/6/2017 5:17:07 AM - Info bpbrm(pid=2320) Starting delete snapshot processing 1/6/2017 5:17:08 AM - Info bpfis(pid=19912) Backup started 1/6/2017 5:17:08 AM - Critical bpbrm(pid=2320) from client *****************: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.*******************nal.us_1483687805.1.0 1/6/2017 5:17:08 AM - Info bpfis(pid=19912) done. status: 4207 1/6/2017 5:17:08 AM - end operation 1/6/2017 5:17:08 AM - Info bpfis(pid=19912) done. status: 4207: Could not fetch snapshot metadata or state files8.9KViews0likes3CommentsList of Netbackup clients
Hello, people... I have upgraded our Netbackup from 7.6.0.4 to 7.7.2. I need a list with all clients with agent installed( to upgrade it) , but the GUI only shows part of them. The clients in policy with qVMware Intelligent Policy query are not in the list... Anyone know how to get this? Thanks in advance...7KViews0likes13Comments8.0 : NetBackup Web Management Console service
Upgraded one of my environments from 7.5.7 to 8.0 - no significant issues, backups and restores are working like they should. This server is a combined media/master and is running windows 2008 R2 The Java console seems to be running fine, but i receive the attached error everytime i go into the java console. During the 8.0 install, you had to create a new local user (nbwebsvc) for the "web mangement console", which i did, and the service does actually start without error. But when you connect with the java console, it stops within a few seconds, and the event log is pretty generic. Any ideas ? thanks6.7KViews0likes6CommentsLot of nbtelesched.exe & nbtelemetry.exe processes even though TELEMETRY_UPLOAD is set to NO
Seen on Netbackup 7.7.2 on Windows 2012 R2. The problem is that all these processes use up the desktop heap, which makes some services crash so that the backups are not running. Wondered if others had seen anything similar ? The only seemly related information on the support is http://www.veritas.com/docs/000024576for Netbackup 7.6.0.1 on AIX.5.6KViews0likes2CommentsBackup Exec 16 VSS issues with server 2012 R2
I have a new setup with Backup Exec 16 installed on Windows Server 2012 R2 64-bit. Mostly working fine with 2 virtual hosts and an exchange server, and speed is good. However, we also have a new file server to back up which is experiencing some difficulty. The server is running windows server 2012 R2 and has over 64TB of storage, so we initially ran into the error: Final error: 0x8004230c - 0x8004230c (2147754764) Backup - Snapshot Technology: Initialization failure on: "System?State". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume. Some reasons for this could be: - The snapshot provider that you selected does not support the volume that you are trying to snap. Try selecting the default snapshot provider, and then run the job again. -A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot. We reconfigured the storage in the RAID controller so that all disks presented to the OS are 62TB or less. All disks are also either 512 or 512E sectors. After running a test backup, the error was gone. However, a week later after migrating data to the new server, the same error returned. Data backs up OK, but volume shadow copy is not used. I've tried the following to resolve the issue: * Rebooting the target server * Removing and re-installing the remote agent, 3 times so far. * Completely rebuilding the Backup Exec 16 server from bare metal. There are no errors in any logs for VSS or VSC. vssadmin list writers shows no issues.(All writers present and stable) When the backup starts, the VSSVC.exe and VDS.exe services show up in task manager temporarily, but the system quickly falls back to normal file copies. VSS fails on all volumes and system state, not just the large ones. All other servers back up correctly. Testing with Windows Server Backup, Veeam Endpoint Backup FREE, and just manually creating a shadow copy on the server all succeed. The only thing I can think of is that the agent is timing out too early or testing for an issue and failing too quickly? I also don't know why the job succeeded once before more data was copied to the server.Solved5.6KViews0likes8CommentsUnable to Connect Backup Exec 16 to Azure Cloud Storage
Hi to All, Have been Fighting for 2 days now trying to connect backup exec 16 to Azure Cloud Storage am using windows 2008 server R2 with backup Exec 16 And Symantec Endpoint protection 12.1 MP6, have read all about the way to do it correctley that exists on the internet, am connecting to server Azure:azure.com, have made sure that outgoing ports 80 and 443 are allowing trafic correctley have made sure that both outgoing and incoming port 10000 is open, and every time I try to connect the connector keeps throwing back BEMSDK Failure code A0009B23 it seems to do this without even trying to connect as the error is immediate any great ideas would be great a thousand thanks in advance to all.5.3KViews0likes10CommentsInvalid Physical Volume Library Media Identifier
Hello, I have W2008R2, BEX 2012 doing duplicate backup to tapes at the end of each month. I tried to do a restore from these backupsets (Dec, Nov, Oct, Sept) and got the "0xe0008105Invalid Physical Volume Library Media Identifier" error for the failed job. Aug works. All of these(Dec, Nov, Oct, Sept) duplicate backup jobs completed without error messages. For each of these sets I tried an inventory and catalog where they scan the first tape in the set, prompt for the second, and then also fail with the same error message. I went back to my Aug backup set of tapes and I am able to do a restore from that set. Also, I can restore from all the tape backup sets if the data exists on the first tape only. Please advise. ThanksSolved5.2KViews0likes4CommentsConfiguring VMware that protect Exchange 2010 DAG
Hi All, I have to implement same configuration as describe in this post: https://vox.veritas.com/t5/NetBackup/Configuring-GRT-based-Exchange-Backup-using-vmware-backup-policy/m-p/824660#M223697 Note that I have implement tranditional backup of exchange and it works. But for perfomance issue, I want to implement VM backup that protects exchange and disable traditional backup. I have an error 13. I'm troubleshooting... Can you help? About DAR configuration, must I use FQDN or short name? I will post job details in fex time. Tnahk for your help.Solved5.2KViews0likes21CommentsNetbackup DFSR backup very slow
Hello, we recently deployed netback 7.7.3 on windows 2012. we have a Data domain storage. Everything is configured by following the veritas and emc guides. eveything is superb except when it comes to DFSR folders. After some reading we understood "Use Journal" is not supported with dfsr. we understood we should add the backup select like Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\LosAngeles Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\NewYork Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Denver we have a 2 TB of data and the backup durations of full and incrimental backup are not ecceptable. I read a lot of posts from people complaining from the same issue when backing up the shadow copy components bot none was helpful. i think i missed something. your help will be much appreciated. let me know if i should provide more info.4.8KViews0likes38CommentsThe Activity Monitor failed because of cannot connect to socket
*** Moved to new post fromhttps://vox.veritas.com/t5/NetBackup/The-Activity-Monitor-failed-because-of-cannot-connect-to-socket/m-p/756768 *** i have the same problem, i have upgrade my NBU to 7.7, is there other reason (except server's resource) ? because this problem is recuring again and again. note: When the backup's job running= Usage CPU 9% Usage Memory 85%4KViews0likes1Comment