Some log digging came up with this from /var/log/messages: Aug 7 16:09:41 localhost kernel: beremote: segfault at fffffffffffffffc ip 00007f7543fbc8cc sp 00007f75420c29d8 error 5 in libc-2.17.soĪug 7 16:09:41 localhost abrt-hook-ccpp: Saved core dump of pid 10894 (/opt/VRTSralus/bin/beremote) to /var/tmp/abrt/ccpp-16:09:41-10894 (48660480 bytes)Īug 7 16:09:41 localhost abrt-server: Package 'VRTSralus' isn't signed with proper keyĪug 7 16:09:41 localhost abrt-server: 'post-create' on '/var/tmp/abrt/ccpp-16:09:41-10894' exited with 1Īug 7 16:09:41 localhost abrt-server: Deleting problem directory '/var/tmp/abrt/ccpp-16:09:41-10894'Īnd running the agent in debug mode shows this: bin]#. The agent installs and starts but once the Media Server connects to it the agent crashes.
#Symantec backup exec 2014 support install#
But in any case they decided to not support it any more.We just deployed our first CentOS 7 machine and are trying to back it up using Backup Exec 2010 R3 and the RALUS agent.Īfter installing the missing compatibility libraries needed for the RALUS: yum install compat-libstdc++-33.i686 compat-libstdc++-33.x86_64 Not sure if the developers are still on board on either side. My customer has valid maintenance for their product but Veritas does now own the product. Now that Symantec and Veritas are separate companies we have to see what is going to happen ( ). It is not only the current problem but also the way they did not care about the customer problem and that they have vaild support contract and they are not supporting their product on a current Domino release. If someone else is using Backup Exec you should be aware of the situation. I saw multiple customer reports with similar issues and they are all not getting any help. If you are using Backup Exec it sounds like it is time to look for a different backup solution! They closed the support incident and the customer asked for a formal statement from product support in writing. So they have been working on it for a while and had no support for 9.0.1 and finally decided to declare the product end of life instead of fixing issues and supporting 9.0.1!!!
Speaking with during the long going support incident Symantec they finally said that Domino 9.0.1 is not supported and they are declaring end of life for their product and even the customer has valid maintenance they are not getting any updates. They set HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Backup Exec For Windows\Backup Exec\Engine\Domino\DAOS listnlo mode = 3 and the issues have stopped. There is a setting described here -> to disable querying information for the backup and the customer is now doing that operation manually at restore.
Running a daosmgr LISTNLOs for each database during backup does not sound right to me.
It was a surprise that Backup Exec has so "deep" DAOS integration but I think they did not implement it the right way. There is no way to completely separate NSF and DAOS backup. But you cannot separate DAOS NLO backup and NSF backup. The error they got pointed to issues with the back media:įinal Error Code: e00084ca HEX (0xe00084ca HEX) or a00084cd HEX (0xa00084cd HEX)įinal Error Description: The data being read from the media is inconsistent.įinal Error Category: Backup Media Errorsīut it turned out that the backup had issues with querying the DAOS files for databasesĪfter a long discussion with support we turned off the daosmgr commands which are used during the backup of a database (registry settings). The error message pointed to issues with their tapes.īut it turned out it had to do with the DAOS integration which is not fully working with Domino 9.0.1 I have been helping a customer who had issues with Backup Exec for Domino. Symantec Backup Exec End of Life Daniel Nashed 5 December 2015 16:19:05