windows

2777 Topics

Where install VIOM: on Windows? or on Linux?
Hi every one: I want to install VIOM, I never do it before, and my first question is: Where I should do it? In Windows envioroment? or in Linux Envioroment? All my clusters are in Linux Envioroment: Infoscale 8.0 on Red Hat 8.9. Other question: Is it posible install Cordination Point Service in the same server? All my clusters have 2 nodos: node one in one CPD (site 1) and the node two in other CPD (site 2). I think that the new server (VIOM+CP) shultd be another CPD (site 3). Correct? Thanks Jaime.
sistemasunix
9 months ago Place InfoScale
372Views
0likes
1Comment
Backing up Active Directory: V-79-57344-33928 - (AD LDS) database was not found.
Hello, We have this error from time to time, but it usually fixes itself without any end user intervention. However I am getting this error three nights in a row now on one of our domain controllers. This started happening on Wed morning, and continued through Friday morning. In all three instances the error message in the log is: Job ended: Thursday, October 29, 2009 at 1:18:54 AM Completed status: Failed Final error: 0xe0008488 - Access is denied. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-33928 Errors Click an error below to locate it in the job log Backup- \\dc1.domain.com\System?State V-79-57344-33928 - Unable to complete the operation for the selected resource using the specified options. The Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database was not found. So I checked the selections and under the server in question, I can see System State > Active Directory > C:_WINDOWS_NTDS, and this is all checked off. I did a test Resource Credentials for everything in this backup and it all returned successful so I'm at a loss. Under Settings > Microsoft Active Directory for this job properties we have all three boxes checked (GRC, Consistency Check, Continue if Consistency check fails.) Backup method is greyed out, but says Full - Back up entire Active Directory. We are using Symantec Backup Exec 12.5 for Windows Servers Media Server Version 12.5 Rev 2213 Administration Console 12.5 Rev 2213 Desktop and Laptop Option: Version 3.1 Rev. 3.41.32a Installed updates: Service Pack 2 Hotfixes: 324947 317436 325647 319242 324012 326004 323894 324011 Thanks for the help, we really do appreciate it!
cypher
3 years ago Place Backup Exec
3.2KViews
0likes
11Comments
Restore serial appointment
We tried to restore a Outlook serial appointment which one was edit on element level every time when the meeting occur. After the successful restore we have the only unknown Items in the Series. Is this normal? I'm grateful for any help! Thanks in advance!
Boell
5 years ago Place Backup Exec
630Views
0likes
0Comments
VCS discovery windows
Hello Experts, As part of a monitoring solution, we have been relying upon the presence of below registry keys to detect presence of a VCS on Windows, HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VC HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VCS\Base This however seems to be unreliable leading to false positives. I want an approach(could be a registry key/value) to detect a VCS with certinity on a Windows. Thank you! Ashish
ashish-desai
5 years ago Place Cluster Server
1KViews
0likes
1Comment
Backup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated Thanks
Solved
resolver101
5 years ago Place Backup Exec
12KViews
1like
4Comments
Migrating PST creates multiple Calndars in outlook
we've recently been rolling out enterprise vault for excahnge version 9 throghout our environment. it iahs integrated with our systems really well and we've only had minor issues I've now reached the tedious and painful stage of migrating existing pst files into the new archives. this worked effectively in trial/test, now i'm picking up the server stored PST files held in the head office of our organisation and our users are reporting strange behaviour with their caendars: we've chosen to import shortcuts from PST files to a folder called "legacy archives" and then to place each archive seperately (not merge) this creates a tree structure containing the archvied calendars from the original PST file, all seems fair so far except that, if a user browses their calendar they can see all of these calendars and there is no way of diferentiating between these. (see attached). i'v tried to hunt around and find a way of importing the archived calendar entries (PST files are being deleted afterwards so caldendar entries must not be ignored). we cannot have our users opening multiple calendars and making entries into the wrong one, nor do we want them to be confused by the sight of many calendars. what do people usually do to prevent this from heppening? Thanks Mike
Solved
Mikeydee135
6 years ago Place Enterprise Vault
1.2KViews
0likes
4Comments
BIOS is not ACPI compatible
Hello all, I've got a problem with the backup exec system recovery disc 2010. When I try to boot with the CD (on USB CD Drive) or USB Key, I have this message : Status: 0xc0000225 Info : Windows failed to load beacause the firmware (BIOS) is not ACPI compatible. A kb on symantec website tells to change the option in the BIOS but I don't have any option about ACPI. http://www.symantec.com/business/support/index?page=content&id=TECH57513 I found that the CD BESR is a Windows PE 2.5 (Vista). But the hardware which I try to restore isn't compatible with vista. Is there any solution for this problem like a Windows PE XP ? Thanks.
thecquet
6 years ago Place System Recovery
4.2KViews
1like
12Comments
Cannot back up system state
Good afternoon, We are currently experiencing an issue when attempting to backup one of our servers. We are running full backups on 7 Windows 2008 servers, but one is failing when it comes to back up the system state. The error is reported as: - AOFO: Initialization failure on: "\\<SERVER>\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider that you selected cannot snap this volume. Select the default snapshot provider, and then run the job again. The following volumes are dependent on resource: "C:" "X:" . The issue appears to be "X:" - this is the DVD drive on the server and obviously VSS isn't able to snap it, and this is the only server on which this is apparently a dependent resource. I'm prety sure it shouldn't be listed here at all? I have checked in the seemingly obvious places (I'm not much of an expert with BE) to no avail, would anybody know how to resolve this and remove X: as a dependent resource? Cheers,
JonahIJ
7 years ago Place Backup Exec
2.7KViews
1like
16Comments
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
CAPI2 - 513 : Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object.
Hi, I am running BE12.5 SP4 on a W2003 Server to backup a W2008 file server. On that W2008 file server I got a multiple error in Windows application log: CAPI2 - 513 : Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object. I have checked Symantec doc id 327192 (http://seer.entsupport.symantec.com/docs/327192.htm), but all security settings are ok and the SystemWriter *is shown* in vssadmin and the buckup job does not fail. Anyone any idea how to fix that? Cheers Dirk
Dirk_Loeffler
8 years ago Place Backup Exec
3.3KViews
1like
4Comments