snapshot failed quiesce the virtual machine
Hi All, Vm backup failling with snapshot error (156)An error occurred while saving the snapshot: Failed to quiesce the virtual machine. below is the error message: 4-03-2016 23:17:20 - Critical bpbrm(pid=13524) from client : FTL - VMware_freeze: VIXAPI freeze (VMware snapshot) failed with -1: Unrecognized error 14-03-2016 23:17:20 - Critical bpbrm(pid=13524) from client : FTL - VMware error received: An error occurred while saving the snapshot: Failed to quiesce the virtual machine. 14-03-2016 23:17:20 - Critical bpbrm(pid=13524) from client : FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 14-03-2016 23:17:24 - Critical bpbrm(pid=13524) from client : FTL - 14-03-2016 23:17:24 - Critical bpbrm(pid=13524) from client : FTL - vfm_freeze: method: VMware_v2, type: FIM, function: VMware_v2_freeze 14-03-2016 23:17:24 - Critical bpbrm(pid=13524) from client : FTL - 14-03-2016 23:17:24 - Critical bpbrm(pid=13524) from client : FTL - snapshot processing failed, status 156 14-03-2016 23:17:24 - Critical bpbrm(pid=13524) from client : FTL - snapshot creation failed, status 156 Please help on this.Solved22KViews0likes4CommentsNetbackup port range
Hi Team, Can you please suggest the below mentioned ports are enough for Netbackup communication and data transfer from client to Netbackup Master /Media server. Client machines are VM ( snapshot backups) , Exchnage , SQL agent base backup Please suggest , if more portsare required to open for data transfer -- Source Destination Source Port Destination Ports Bi-Directional Master Server Media server Any TCP/1556 TCP/2821 TCP/13724 TCP/13782 TCP/13720 TCP/4032 TCP/10102 TCP/10082 TCP/443 TCP/111 TCP/7394 TCP/902 Yes VM Client machines Media server Any TCP/1556 TCP/13724 TCP/10102 TCP/10082 TCP/443 TCP/2821 Yes VM Client machines Master Server Any TCP/1556 TCP/13724 TCP/10102 TCP/10082 TCP/443 TCP/2821 YesSolved16KViews1like17CommentsSolution for VSS exceptions with VMware guests / VM tools
Hi everyone, We have been experiencing VSS issues with VMware guests in regards to the installed Backup Exec Agent and a previously installed VMware Tools VSS option. Uninstalling the VMware Tools VSS option in various ways including restarts did not fix our issues. If you search the internet for solutions, you find many attempts but no real solution or explanation. One of our admins spend several hours with the Veritas support without a solution, he was about to escalate the issue with them, when we found the root cause and could actually fix our issues. First the steps to solve this: Uninstall the VMware Tools VSS option (no restart will be requiered) Make sure VMware VSS service was deleted If this is not the case, you might need to do so manually and remove additional DLL's etc. as well as restart the system, but this is independent from this solution You might have already done steps 1 and 2 but you still get VSS exceptions from the backup that says you have more than one VSS agent installed: V-79-8192-38331 - The backup has detected that both the VMware VSS Provider and the Symantec VSS Provider have been installed on the virtual machine 'hostname'. However, only one VSS Provider can be used on a virutal machine. You must uninstall the VMware VSS Provider. Now you wonder what causes this and you get stuck You could uninstall the Veritas/Symantec Backup Exec Agent and only back the system up per VMDK You would lose the GRT / granular backup / restore capabilities Check your registry for the following reg key HKLM\System\CurrentControlSet\Services\BeVssProviderConflict If this key exists, but your VMware VSS provider is uninstalled, you need to follow up with step 5 Open a notepad as administrator Open this file in the notepad C:\ProgramData\VMware\VMware Tools\manifest.txt Search for the following two entries: Vcbprovider_2003.installed vcbprovider.installed Make sure both of them are set to FALSE, most likely one of them is TRUE Run a test backup This test backup now should not show the exception anymore The registry key should vanish (refresh/press F5) without you taking action So what happened? You uninstalled the VMware Tools VSS provider, but this manifest file did not get updated. We actually could see that it sometimes does get updated and sometimes does not. This seems to be some kind of issue with the VMware Tools uninstalled/installer. But why this manifest.txt file? As we found out, there scripts that get executed by Symantec/Veritas Backup Exec before the backup. You might find them in two locations, and it seems to depend a bit on the Windows version which script is executed (at which location). You could edit them both and just undo the checks in the scripts, but this wouldn't be correct. It is more correct to update the manifest.txt file. If you want to, you can check the date/time of the manifest.txt file before you change it - you might see it was not updated while you uninstalled the VMware Tools VSS provider (assuming you did only do this and not do additional installs/uninstalls within the VMware Tools / please note as well that this only is true when you still experienced those issues). Now, back to those scripts, you find them here: C:\Windows C:\Program Files\Symantec\Backup Exec\RAWS\VSS Provider The name of the script that matters: pre-freeze-script.bat This script checks several DLLs, registry entries, paths and on Windows 2008 and newer the ProgramData-Path for this specific manifest.txt file and the two entries mentioned. Once you uninstall the VMware VSS provider, and the file did not get updated, you might see this issue and wonder how to solve it. The solution is to simply update it to mirror the uninstallation of the VMware VSS provider (vcbprovider). We double checked this with several installations and could see if the file actually gets updated, those two values are set to FALSE, if it doesn't, at least one of the values remains true, what causes the pre-freeze-script.bat to write the registry key mentioned earlier and therefor causing the issue in the backup - exceptions. If you still have the same issues after updating the manifest.txt, simply check all the DLL's that are mentioned in the script and make sure they don't exist. You might also consider to manually delete the registry-key (it seems to be just a dumy-key) to make sure there is no issue that prevents the script from deleting it. Make sure it does not re-appear after a backup! Otherwise you might still have some DLLs left on your system that cause the script to re-create the registry key. Hope this helps a few of you out there. This was an ongoing issue for a while and I came accross those issues many times ever since Windows 2008. This applies to Windows 2008 R2, Windows 2012, Windows 2012 R2 and pretty sure to Windows 2016 as well. It helped us getting rid of those issues completely and actually not even needing a single restart of the guest VM to solve the issues (removing the VMware VSS provide did not need a restart). Regards Florian RossmarkSolved14KViews2likes10CommentsEvent 1023 Windows cannot load the extensible counter DLL Backup Exec.
I am getting the following events from our newly build server 2012 r2 server with BE 15. I am not sure what is causing this issue, but it appears to be related to BE and performance counters. Log Name: Application Source: Microsoft-Windows-Perflib Date: 4/24/2015 11:02:17 AM Event ID: 1008 Task Category: None Level: Error Keywords: Classic User: N/A Computer: XXXXXXX Description: The Open Procedure for service "BITS" in DLL "C:\Windows\System32\bitsperf.dll" failed. Performance data for this service will not be available. The first four bytes (DWORD) of the Data section contains the error code. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" /> <EventID Qualifiers="49152">1008</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-24T18:02:17.000000000Z" /> <EventRecordID>3405</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXXXXXX</Computer> <Security /> </System> <UserData> <EventXML xmlns="Perflib"> <param1>BITS</param1> <param2>C:\Windows\System32\bitsperf.dll</param2> <binaryDataSize>4</binaryDataSize> <binaryData>02000000</binaryData> </EventXML> </UserData> </Event> Log Name: Application Source: Microsoft-Windows-Perflib Date: 4/24/2015 10:53:43 AM Event ID: 1023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: XXXXX Description: Windows cannot load the extensible counter DLL Backup Exec. The first four bytes (DWORD) of the Data section contains the Windows error code. Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" /> <EventID Qualifiers="49152">1023</EventID> <Version>0</Version> <Level>2</Level> <Task>0</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2015-04-24T17:53:43.000000000Z" /> <EventRecordID>3403</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>XXXXXX</Computer> <Security /> </System> <UserData> <EventXML xmlns="Perflib"> <param1>Backup Exec</param1> <binaryDataSize>4</binaryDataSize> <binaryData>7E000000</binaryData> </EventXML> </UserData> </Event>12KViews0likes4CommentsAdd media server in Master server
hi Team, I have got one media server for my master server. I have finished installing Netbackup media server software . Now Need help inadding this media server in Master server console. Master / Media server - windows 2012 R2 , Netbackup version - 7.6.0.3Solved12KViews1like4CommentsA guide to booting HP Elitepad to recovery environment using USB flash drive
Hi, Back in October 2013, a support case that I opened with Symantec in relation to failure of the Elitepad 900 G1 to boot into the Symantec recovery environment from a USB or DVD drive etc, was ultimately closed with no resolution due to a compatibility issue or similar. I recently decided to pick this up again and am pleased to report a successful outcome but not without issues. Here's what I did: > Note: I have SP2 installed on my SSR client (Ver. 11.0.2.49853)but this is immaterial to process described below. > Grabbed a copy of the latest 32bit recovery ISO (SSR11.0.2.49853_AllWin_English_SrdOnly.iso)from here:https://www4.symantec.com/Vrt/offer?a_id=88724 > Obtained and formatted thumb drive as FAT32 (I did not have to bother with the diskpart procedure that is referenced as required from several sources) > Used WinZip to extract the contents of the ISO to the USB flash drive. Note: DO NOT use the Customer Recovery Disk wizard in the SSR 2013 client. > That's it, plugged it in to one of 2 x USB sockets available on the Elitepad productivity jacket. (Note: if you don't have a jacket you might be in trouble having access to only 1 x USB port. > A USB keyboard needs to be connected to the 2nd USB port as there is no touch panel functionality in the recovery environment. Note that If you wish to use a USB Ext Drive to store the recovery points, the USB Boot Flash drive can be safely removed once the environment is entered, allowing you to connect your USB Ext Drive. > In Elitepad Advanced Startup options, selected USB EFI Boot Device option. > Elitepad booted into recovery environment with navigation by keyboard thereafter (Some useful keyboard shortcuts are:- TAB to cycle the focus between objects; enter to select; [space] to check/uncheck a checkbox; right arrow key to expand a file folder to show subfolder) > Ripped a Windows 8.1 image from one Elitepad and then restored using this image to a factory state Windows 8.0 device with no issues whatsoever, just had to re-activate Windows after the restore. So anyway, the critical step in the process described above is to use WinZip or a similar archiving utility to get the ISO contents onto the flash drive because for some bizarre reason, if you use the Symantec Custom Recovery Disk wizard to burn the ISO, this causes all of the files on the flash drive to become hidden (even with "Show Hidden Files / Folders" checked in file explorer?) with the exception of autorun.inf. The problem appears to be that the Elitepad 900 GI apparently can't see these files because it does not recognise a flash drive prepared in this manner, as a valid EFI USB boot device. It seems unlikely that the Elitepad 900 is the only tablet that might be affected by this issue. Hopefully this guide might save somebody some time at some stage. Orson.12KViews1like8CommentsBE2014 DLM not delete already expired backup sets
Hello, I have upgraded a BE2012 SP4 installation to BE2014. The backups go to a DataDomain DD160 using as a OpenStorage device. There a lot of backup sets which are already have been expired. The DLM of BE2014 seems not deleting already expired backup sets (e.g. from BE2012). For new expired backup sets the deletion works. How can I delete the >1000 expired backup sets?11KViews3likes44CommentsSystem Recovery 2013 R2 - Service Pack 6 now available!
System Recovery 2013 R2 Service Pack 6 is now available. New features in SP6 include support for Symantec Management Platform (SMP) 8.0, SharePoint 2016 and Amazon S3 Cloud Storage support for Offsite Copy. For more details, please refer to the release notes: http://www.veritas.com/docs/000114407 Service Pack download: http://www.veritas.com/docs/000114408 (note that SP6 is not available via LiveUpdate) Updated compatibility list: http://www.veritas.com/docs/000004208 Full builds are available at https://my.veritas.com/ Trialware available at https://www.veritas.com/trial/en/us/system-recovery-2013-server-edition.html Management Solution trialware available at https://www.veritas.com/content/trial/en/us/system-recovery-management-solution.html Please use this thread for any questions about SP6.11KViews2likes14CommentsList of NetBackup Blueprints...
FYI - just sharing a list of really useful documents posted byGFK... [edit - updated links to new locations] NetBackup v2.6 Appliance Whitepaper - WAN Optimization https://vox.veritas.com/t5/Articles/NetBackup-Appliances-Network-Optimization/ta-p/808956 NetBackup v7.6 Blueprints - Accelerator https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Accelerator/ta-p/808665 NetBackup v7.6 Blueprints - Accelerator for VMware https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Accelerator-for-VMware/ta-p/808644 NetBackup v7.6 Blueprints - Active Directory https://vox.veritas.com/t5/Articles/Netbackup-7-6-Blueprints-Active-Directory/ta-p/808669 NetBackup v7.6 Blueprints - AIR https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-AIR/ta-p/808731 NetBackup v7.6 Blueprints - BMR https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-BMR/ta-p/808847 NetBackup v7.6 Blueprints - Enterprise Vault https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Enterprise-Vault/ta-p/808853 NetBackup v7.6 Blueprints - Exchange https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Exchange/ta-p/808682 NetBackup v7.6 Blueprints - Hyper-V https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Hyper-V/ta-p/808652 NetBackup v7.6 Blueprints - IRV (Instant Recovery for VMware) https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-IRV/ta-p/808861 NetBackup v7.6 Blueprints - Media Server Deduplication Pool https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Media-Server-Deduplication-Pool/ta-p/808697 NetBackup v7.6 BluePrints - NDMP https://vox.veritas.com/t5/Articles/Netbackup-7-6-Blueprints-NDMP/ta-p/808953 NetBackup v7.6 Blueprints - NetBackup Catalog https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Netbackup-Catalog/ta-p/808872 NetBackup v7.6 Blueprints - OpsCenter https://vox.veritas.com/t5/Articles/Netbackup-7-6-Blueprints-OpsCenter/ta-p/808748 NetBackup v7.6 Blueprints - Oracle https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-Oracle/ta-p/808685 NetBackup v7.6 Blueprints - RD (Replication Director) https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-RD/ta-p/808702 NetBackup v7.6 Blueprints - SAN Client https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-SANClient/ta-p/808964 NetBackup v7.6 Blueprints - Security https://vox.veritas.com/t5/Articles/NBU-7-6-Blueprint-Security-Feb-2015/ta-p/809111 NetBackup v7.6 Blueprints - SharePoint https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-SharePoint/ta-p/808694 NetBackup v7.6 Blueprints - SLP (Storage Lifecycle Policy) https://vox.veritas.com/t5/Articles/Netbackup-7-6-Blueprints-SLP/ta-p/808877 NetBackup v7.6 Blueprints - SQL https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-SQL/ta-p/808675 NetBackup v7.6 Blueprints - VMware https://vox.veritas.com/t5/Articles/NetBackup-7-6-Blueprints-VMware/ta-p/808617 NetBackup v7.6 Technical Brief - Vault Extension https://vox.veritas.com/t5/Articles/NetBackup-7-6-Vault-Extension-Technical-Brief/ta-p/808705 . ...and another that I have found very useful: NetBackup v7.x Whitepaper - Encryption and Key Management Solutions http://www.veritas.com/docs/000087894 [end]Solved11KViews6likes21Comments