Server

5 Topics

BE Slow SystemState Backup
Was wondering if anyone has seen this issue or has a fix We have been noticing that for some of our customers that the backup jobs been taking longer than they used to and it seems to come down to the SystemState portion of the backup. It seems to have almost doubled / two and half times increase in the amount of time it takes vs before. (where it used to be about 45 min now closer to 2hrs) This seems to be across BE verions (20.3 and 20.5) and Server verions (2016, 2019) and it just seems for 1 customer it seems to have been the latest November Windows Updates, but have been seeing this before with different customers as well prior to the november updates Been doing tests as well in my test enviroment to try to find a cause / common reason but cant seem to find one
TimPoulter
5 years ago Place Backup Exec
578Views
0likes
0Comments
Install DLO in Active Directory
Hallo, In my office i want to install DLO for file backup, but due to limited cost i want to use AD server for DLO. Is it safe enough DLO to install on AD server? The user that the backups will be at about 80 users. PS: For AD server that will be installed DLO is second AD server
Solved
jaka_sanjaya
8 years ago Place Desktop and Laptop Option
2.3KViews
0likes
7Comments
Solution 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 Rossmark
Solved
frossmark
8 years ago Place Backup Exec
14KViews
2likes
10Comments
[PROBLEM] AgentConfig Oracle Linux 7.2
Hi all, note: oradev (oracle user. In DBA and BEoper group) backup (has SYSDBA and SYSBACKUP privilege) Backup Exec: 15 FP 5 Database: Oracle 12.c (12.1) OS: Oracle Linux Server 7.2 i have a problem: I use 'root' for running ./AgentConfig . I choose option 1 (Configure Database Access) and put 'oradev' user as system credential for oracle operation and has local system. Everything is fine. But when i choose option 2 (Configure Oracle Instance Information), i can't put 'backup' user. It always says failed to login. Then i use 'oradev' for running ./AgentConfig. I can put 'backup' userforoption 2 (Configure Oracle Instance Information). But can't put 'oradev' user for option1 (Configure Database Access). It always says "Either incorrect credentials were used, or the user account is not a member of the beoper group. Ensure that the correct credentials are entered, that the user account is a member of the beoper group, and then try again.".I'm sure that i put the right password and is in BEoper group. Do i miss something? I'm sorry if my english isn't good. I hope you guys get my message.
abeherm
8 years ago Place Backup Exec
1KViews
0likes
1Comment
Backup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers
VALEXEC15
8 years ago Place Backup Exec
3.3KViews
0likes
3Comments