job status - complete with exceptions
there are some backup jobs run in Backup Exec 2012 , only two full backup jobs complete with exceptions in the lastest backup task. The credential of this backup job test result was failed. we haven't change any password or credential of this job. Exceptions Details: can't open this item \\posdb1\[ROOT]/oracle/app/grid/product/11.2.0/log/posdb1/srvm/eonsd_0.log.lck - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsid.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/multipathd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/atd.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sm-client.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/sendmail.pid - skiped. can't open this item \\posdb1\[ROOT]/var/run/iscsiuio.pid - skiped.Solved2.4KViews1like8CommentsBackup mediante Bit de archivo Linux?
Hola amigos. Tengo el siguiente inconveniente. Necesito ejecutar Backups Diferenciales/Completos en Linux. Pero los backups mediante "Fecha de modificacion" no me sirven, ya que aveces copio archivos a los directorios y estos tienen una fecha anterior a la de la copia completa, y no se toman en cuenta en las copias diferenciales. Existe alguna forma de utilizar el Backup mediante Bit de archivo en Linux? U alguna otra alternativa? Muchas Gracias! Saludos!Solved521Views1like1CommentUnable to install RALUS on sun Sparc Server- Solaris 5.10
We are doing a trial of Backup exec 2014 in a Mix of windows /Linux/ Sun environment. The Sun solaris operating system version is SunOs 5.10 When we try to install RALUS on SunOs, we get a message "Not Supported" Any help is appriciated. ThanksSolved825Views1like1CommentCentOS
Why is Symantec dragging its feet when it comes to the support of CentOS? It is a direct BINARY clone of Red Hat Enterprise Linux. Anyone in the Linux world knows this except Symantec. This means, that it is the SAME operating system with the RedHat copyrighted logos and name removed and you don't pay for support that isn't needed. I'm tired of getting the run around from the support team. "It's not supported." This is BS! RHEL = CENTOS This is the final nail in the coffin for Backup Exec. 2012 put it in the box, this seals the lid and puts it in the ground. RIP Backup Exec.Solved289Views1like1CommentOracle on Linux backup issue - TNS:Permission access denied.
Hi, We have the following. Backup Exec 2010 R2 on Windows 2003 Ent. SP2 (32bit). As Master and Media server RALUS of BE 2010 R2 installed on RHEL 5.4 64 Bit. as BE Client. Now, we are configing the RALUS for Oracle backup. We have completed the RALUS installation and the Linux server is showing the root folder. Now, we have tried configuration of Oracle authentication and instance authentication. I have done this above task using a seperate User ID other then root. I have selected not to use the recovery catalog for taking backup and default templet. ************** In the BE server side console. I see the all the instance and are in open state... I can able to select the instance and recovery catlog fron the selection list. But when executing the job its givind the error... The script have a error. in the script it give the below error. ORA-12546: TNS:permission denied Please, help... Thanks891Views1like7CommentsMedia Server unable to login to Linux Server
Hello, I have a Windows 2008 Backup Exec Media 2010 R3 Server that is trying to connect to a Suse Linux Enterprise Server 10 SP4. However the BE server is unable to authenticate to the SLES server. I get the following error when trying to browse into the server: "The logon account that was provided does not have valid credentials. Ensure that the user name and password are correct, and then try again." This is the error that appear in the Job Log when it trys to run: Error category : Security Errors Error : e0009b61 - The logon account that was provided does not have valid credentials. Ensure that the user name and password are correct, and then try again. This server worked fine prior to an update I had to apply to move from SLES SP3 to SLES SP4. After SP4 was applied I was no longer able to authenticate to the server from the BE Media Server I'm currently working with Support on this, but I wanted to post here to see if anyone had any ideas. So far I have uninstalled the RALUS agent, Reinstalled the RALUS agent. Re-entered the login credentials Confirmed that port 10000 is open. Restarted several times, before and after RALUS reinstalls. Originally Symantec Support suggest that I update from BE 2010 R2 to BE 2010 R3 - which I did (which is how I got to R3). Liveupdate has been run on the BE server and all available packages have been applied. When I do a RALUS reinstall and browse for the server, I get a popup that needs me to confirm the trust relationship between the SLES box and the BE Media server. I approve it, and then the logon error occurs. I think this would imply that the Media server and the SLES box are communicating. Did I mention other SLES 10 SP4 linux servers are able to be browsed? Thank you everyone for your help, I really appreciate it. JonathanSolved599Views1like1Comment