Where are the Linux logs?
Using BEWS 12 with linux agents on SLES11. Installed the 64 bit agent and started ./VRTSralus.init start, then login to the BEWS and run the backup job for said linux server and there is always a communication error or agent may not be running error. I login to the linux server and start BE agent. The agent never seems to stay running. Where would i find the logs to see what is going on? I looked on the linux server /var/logs/messages, nothing found in reference to BE agent. Are there any issues with the 64 bit agent on SLES11. Oh, btw, it is BEWS12 agent. I started beremote with debug options and tried to browse the linux server using the BEWS, the debug file just cuts off, i never see the error! This server has 2 NICs in it; 1 on the trusted network which is where the BEWS is and 1 on the optional network. A netstat shows beremote bound to 0.0.0.0. Is there a way to bind beremote to 1 ip? And would this even help.Solved781Views16likes2CommentsHOW TO install BackupExec 2010 agent on Debian (RALUS)
I hope this post will be useful to many people (please vote for it or mark it as solution if it helps you). Installing directly RALUS on Debian will not always work. First problem : ../perl/Linux/bin/perl: No such file or directory Second problem : at the end "was not successfully installed" and "impossible to add VRTSralus to (server)" And some others that will get solved when following my solution This is a simple way to install it and avoid these (and other) problems : 1. (optional) Create a folder to keep all RALUS files and copy the archive into it : mkdir /root/BE mkdir /root/BE/RALUS2010 mv RALUS_RMALS_RAMS-2896.9.tar.gz /root/BE/RALUS2010/ cd /root/BE/RALUS2010 2. Unpack the archive provided by Symantec tar xzf RALUS_RMALS_RAMS-2896.9.tar.gz 3. Stop the RALUS service if it is already installed and runnig /etc/init.d/VRTSralus.init stop 4. Very important, if you are under a 64 bit Linux you have to this Extract debian package : tar xzf RALUS64/pkgs/Linux/VRTSralus.tar.gz Install debian package : dpkg -i VRTSralus-13.0.2896-0.x86_64.deb Start installation : ./RALUS64/installralus 5. But if you are under a 32 bit Linux you have to this (I didn't tested under 32 bits) : Extract debian package : tar xzf pkgs/Linux/VRTSralus.tar.gz Install debian package : VRTSralus-13.0.2896-0.i386.deb Start installation : ./RALUSx86/installralus or ./installralus 6. Be sure to answer all questions correctly especially the one about the host server (XXX.XXX.XXX.XXX), you must give the IP of the Backup Exec server. 7. Do a restart of the RALUS Backup Exec agent, and it should say "[ OK ]" /etc/init.d/VRTSralus.init start I hope it will help ! Send me questions if you have other problems... Denis P.S. Tested with Debian 5.0.3 P.P.S. If you still have some problems : A) If you get "ERROR: VXIF_HOME is invalid. It must point to the root of VxIF. Exiting ...", simply edit ./RALUS64/installralus, and change line 3 : from : VXIF_HOME=../;export VXIF_HOME to : VXIF_HOME=/root/BE/RALUS2010/;export VXIF_HOME B) If you get "./RALUS64/installralus: line 50: ../perl/Linux/bin/perl: No such file or directory", simply edit ./RALUS64/installralus, and change line 50 : from : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ../installralus.pl $* to : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ./installralus.pl $* or to : perl -I.. -I$PATH -I$VXIF_HOME ./installralus.pl $* (to be clear, remove one dot in front of"/installralus.pl", keep only one dot instead of two) C) If the installation is sucessful but VRTSralus refuses to start, launch /opt/VRTSralus/bin/beremote –-log-console to see the error. If you get error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory you simply need to install the package : Under Debian 6.0.3 : apt-get install libstdc++5 (Thanks to RockwellMuseum)3.2KViews9likes17CommentsBackup Exec Linux Agent - change port Agent for single server
Dear All, I have Backup Exec 2012 running on Windows Server 2008 R2, this server is backuping about 30 servers, nearly all are Windows servers (2003 2008 2012) and 2 of them are Linux Servers. One Linux server is running on the standard port and this is ok, the other one can't use the port 10000 because i already have this port used by one other service and this can not be changed. I've already switched the port of the linux agent to port 12000 (http://www.symantec.com/docs/TECH37415), but when i browse the server on the BackupExec console i get an error. I suspect that it is necessary to change from port 10000 to port 12000 for all 30 servers that I'm backuping (obviously not possible), but I have not found this information written officially anywhere. is this correct or not? It is possible to change the port for only a single agent? there is something that I have to change on the backupexec console for this single linux server? Thanks for your advices, Davide2KViews5likes5CommentsInstalling RALUS agent on ESXI 5.1
Hi folks, I have been trying to get the RALUS agent installed on my newly upgraded ESXI box. This box was upgraded from version 4.0 to version 5.1 (licenced) Unfortunately I am running into a few problems and was wondering if you might have some thoughts. I have managed to copy over the 237 MB of the RALUS_RMALS_RAMS-5204.4.tar.gz file to a folder on my ESXI box. From there I unzipped the file with the following command gunzip RALUS_RMALS_RAMS-5204.4.tar.gz Also the contents were extrated from the .tar file tar -xvf gunzip RALUS_RMALS_RAMS-5204.4.tar I now have a folder full of files. So far so good. According to the Backup and Administer Symantec 2010 guide I should now be able to run the installation by using this command ./installralus This does not seem to work. I get a "Not Supported" message doing so. The ESXI isnewly upgraded to version 5.1 with a license for the Storage API's Can someone perhaps advise what I am doing wrong? Also, I noticed that there are several hotfixes for the RALUS agent. I could not find much documentation on this. Does anyone no were I can find instructions for installing these hotfixes? Your thoughts or ideas are much appreciated. Thanks, RemkoSolved1.4KViews3likes10CommentsProviding self help recovery portal for user to file level recovery
Hi Everyone, I'd like to simplify the restore process in my Linux file server for the Windows desktop user, How can I provide some sort of website to restore file from the Backup Exec 2010 so the user doesn't have to bother the backup operator to restore single file from Linux server ? I've heard a product named Backup Exec Retrieve is that what I should look for ? Thanks.Solved1.1KViews3likes5CommentsBug - Backup Exec 2010 returns "Access denied" if a directory is moved during the backup
It's a bug report. When we're running a backup of a file using RALUS, if the directory which contains the file is moved (for example, renamed), the backup of this file (and of all the other files inside this dir) will fail with the error "Access is denied to directory ...". However, we had permission to access this directory during all the backup time. The log error is wrong. Description (step-by-step) We have a "Selection List" with one resource: \\backup.2aliancas.com.br\[ROOT]/var/exports/backups/mydir/*.* /SUBDIR The directory mydir is a directory (EXT4 backend) in the backup.2aliancas.com.br server (a Linux server with RALUS) with the following structure: /mydir |-> dir1 |-> file1.txt |-> file2.txt For simplicity, consider that these files are big (like 10G each one). So, it will be easier to reproduce the problem. Now, let's start the RALUS deamon in debug mode: $ /opt/VRTSralus/bin/beremote --log-file /tmp/bug.log & $ ps aux | grep beremote root 21725 0.1 0.1 222900 14540 pts/0 Sl 13:27 0:00 /opt/VRTSralus/bin/beremote --log-file /tmp/bug.log $ ls -lh /proc/21725/fd total 0 lrwx------ 1 root root 64 2015-07-01 13:29 0 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:29 1 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:28 2 -> /dev/pts/0 l-wx------ 1 root root 64 2015-07-01 13:29 3 -> /tmp/bug.log lrwx------ 1 root root 64 2015-07-01 13:29 4 -> socket:[18882216] lrwx------ 1 root root 64 2015-07-01 13:29 5 -> socket:[18882217] Now, let's start a backup (the used settings are attached). After some time, we can see that RALUS is backing up the file file1.txt and also two file descriptors are opened (one for the directory dir1 , and one for the file file1.txt ): $ ls -lh /proc/21725/fd total 0 lrwx------ 1 root root 64 2015-07-01 13:29 0 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:29 1 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:28 2 -> /dev/pts/0 l-wx------ 1 root root 64 2015-07-01 13:29 3 -> /tmp/bug.log lrwx------ 1 root root 64 2015-07-01 13:29 4 -> socket:[18882216] lrwx------ 1 root root 64 2015-07-01 13:29 5 -> socket:[18882217] lrwx------ 1 root root 64 2015-07-01 13:42 6 -> socket:[18886347] lr-x------ 1 root root 64 2015-07-01 13:42 7 -> /var/exports/backups/mydir/dir1 lrwx------ 1 root root 64 2015-07-01 13:42 8 -> socket:[18886422] lr-x------ 1 root root 64 2015-07-01 13:42 9 -> /var/exports/backups/mydir/dir1/file1.txt Now, let's rename dir1 (same inode and file descriptor, different name) and create a new dir1 directory (a new inode): $ mv /var/exports/backups/mydir/dir1 /var/exports/backups/mydir/dir2 $ mkdir /var/exports/backups/mydir/dir1 Now, let's check the opened file descriptors: $ ls -lh /proc/21725/fd total 0 lrwx------ 1 root root 64 2015-07-01 13:29 0 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:29 1 -> /dev/pts/0 lrwx------ 1 root root 64 2015-07-01 13:28 2 -> /dev/pts/0 l-wx------ 1 root root 64 2015-07-01 13:29 3 -> /tmp/bug.log lrwx------ 1 root root 64 2015-07-01 13:29 4 -> socket:[18882216] lrwx------ 1 root root 64 2015-07-01 13:29 5 -> socket:[18882217] lrwx------ 1 root root 64 2015-07-01 13:42 6 -> socket:[18886347] lr-x------ 1 root root 64 2015-07-01 13:42 7 -> /var/exports/backups/mydir/dir2 lrwx------ 1 root root 64 2015-07-01 13:42 8 -> socket:[18886422] lr-x------ 1 root root 64 2015-07-01 13:42 9 -> /var/exports/backups/mydir/dir2/file1.txt PS: This is the expected behavior of Linux at this point. After some time, the backup of file1.txt ends, and RALUS logs some errors. After, RALUS tries to get the next files to backup and logs another error. When the backup ends, Backup Exec logs "Access denied to directory /var/exports/backups/mydir/dir1.", which is a unuseful message. There is not access denied (both the old dir1 (now dir2 ) and the new dir1 are accessible all the time). The RALUS log file is attached at this bug report also. Expected behavior There's no well defined expected behavior for this. However, good solutions could be: Keep copying the others files in the directory dir1 ; It is, at the end of the backup, both files would be backed up at mydir/dir1/file1.txt and mydir/dir1/file2.txt ; This is what cp and rsync would do; This is possible because the file descriptor, the directory stream, the inode number and all the other attributes of the directory are still the same after the rename; After realise that dir1 was renamed, stop copying the other files (only mydir/dir1/file1.txt would be backed up) inside dir1 . A warning "Directory renamed: Skipping directory /var/exports/backups/mydir/dir1" could be logged instead of "Access denied".326Views2likes0CommentsBackup Exec 2010 R3 pops up logon account selection while trying to connect to Ubuntu Server
Hello, I just upgraded toBackupExec2010R3 on a Win 2k8 R2 virtual machine with no problem. I currently have a dozens Ubuntu Servers I need to backup.I have installed a Ubuntu server 12.04 as a test machine. I have installed the RALUS (remote agent for linux servers) version 5204.4 on the linux server with the help from following link https://www-secure.symantec.com/connect/forums/how-install-backupexec-2010-agent-debian-ralus. Everything went well. When trying to creat a jobfrom the BackupExec Media server I receive the following "logon Account Selection" pop up windows: I can successfully ping the Media server from the Ubuntu server and vice versa. logon to the Ubuntu server with username: root and with the same password set in the logonaccount selection start VRTSralusservice Output of ralus.cfg I may have missed something somewhere and I can't just seem to figure it out? Any help will be appreciated.Solved564Views2likes1CommentHow do i backup FreeNAS shares?
Hi, FreeNAS 8.3. Server 2008 R2 Backup Exec 2010 R3 I am implementing a FreeNAS server onto my network for additional file storage. How do i backup the data in these shared folders on the FreeNAS box??? FreeNAS box is joined to my Active Directory. I can browse to the freenas server in the selection list, expand it and select the content. However the job fails with: (Server: "server") (Job: "FreeNas Test") FreeNas Test -- The job failed with the following error: The logon account that was provided does not have valid credentials. Ensure that the user name and password are correct, and then try again. The job runs as a Backup Exec domain user account, that is a member of the Domain Admins group. I cant put a remote agent onto the FreeNAS box - but my media server is fully licenced with the remote agent. How do i backup FreeNAS please with Backup Exec 2010R3? ThanksSolved3.9KViews2likes4CommentsSynthetic Backup with RALUS
Hi, I'm trying to find out if synthetic backups of Linux file systems (specificallyOES2)are officially supported by Backup Exec 2012 . This isn’t noted in any Symantec compatibility list. They work in my test environment with CentOS and this was fully supported in older versions of Backup Exec as per the following tech note:http://www.symantec.com/business/support/index?page=content&id=TECH38377 Thanks, NickSolved678Views2likes3CommentsBMR error SUSE 10 SP1 x64
Hi all I have a master server with Netbackup 7.5.0.6 on Windows 2008 R2 My client is en SUSE 10 SP1 with Netbackup client 7.5.0.6 When i launch a full backup with BRM options activated, 2 jobs appear First job is tfinished in state partial successfully 20/09/2013 11:40:14 - Error bpbrm(pid=3260) BMRERR: Received BMR error: Failed to import Config file. (1) 20/09/2013 11:40:14 - Error bpbrm(pid=3260) BMRERR: Received BMR error: Failed sending the discovery. (1) 20/09/2013 11:40:14 - Error bpbrm(pid=3260) BMRERR: Received BMR error: BMR information discovery failed. (1) 20/09/2013 11:40:14 - Info bmrsavecfg(pid=0) done. status: 1: the requested operation was partially successful Second job is finished successfully Any idea ?Solved1.1KViews2likes6Comments