Cannot backup Ubuntu 12.04 with Backup Exec 2014 SP2
I have not being able to backup Ubuntu 12.04 with backup exec 2014. some results from my ubuntu server ps -elf | grep beremote | grep -v grep 4 S root 1558 1 0 80 0 - 107294 hrtime 23:37 ? 00:00:00 /opt/VRTSralus/bin/beremote sudo strings /opt/VRTSralus/bin/beremote | grep -i version _ZN21type_conversion_errorD1Ev _ZN21type_conversion_errorD0Ev _ZTS21type_conversion_error _ZTI21type_conversion_error _ZNK21type_conversion_error4whatEv _ZTV21type_conversion_error _Z14ndmpSetVersionPvt _Z14ndmpGetVersionPv 21type_conversion_error conversion of data to type " ndmpdApiLog: version:%u ndmpdConnectOpen: protocol_version:%ld. VMWARE_AGENT_CREATE_VERSION_7_VM V2V_VM_VERSION P2V_VM_VERSION NDMP_PROP_PEER_PROTOCOL_VERSION Engine doesn't use the minimum protocol version supported by this agent. Engine rev is VERITAS_Backup_Exec_File_Version=14.1.1786.1093 I seen this message, but I am not sure if it means anything Engine doesn't use the minimun protocol...... I disabled IPV6, on my windows Backup Exec 2014 server I get the Browser Failure Failure to browse [ROOT] A network connection could not be established. Thanks
Bug - 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".
Please help to upgrade agent on Red Hat Linux
Recently i have upgraded backup exec 2012 to 2014. Server upgrade is fine. We have redhatlinux server which is being backed up daily. The agent in this server is still using 2012 version, every day backup is completed with warning messege that agent is running old version need to upgrade. Please some one provide steps to upgrade the agent. Thanks
Backup Exec 2010 incremental Backup from Synology DS1813+ with RALUS ?
Hello, we need to do regular Backups from Synology DS1813+ NAS. On the server side we use Backup Exec 2010 on a Windows Server 2008. Here´s the question: We need incremental backups. And incremental Backups are only supported via a remote Agent, am I right? I know that Synology DS1813+ is not supported for RALUS, but maybe someone tried to install the Remote Agent on the DS anyway and can give me feedback if it works? Or maybe there is another solution for my Problem (not iSCSI) ? I am looking forward for helpful answers :) Kind Regards Erik
Location of CdbsMutex file on Linux (RHEL)
Is the location of where beremote creates the CdbsMutex file configurable? I've noticed that it gets created in the current working directory where the process was started. At boot time through the /etc/rc.d/init.d/VRTSralus.init file, it is created as /CdbsMutex. I were to log in as root and execute "/etc/rc.d/init.d/VRTSralus.init start" it is created as /root/CdbsMutex. I would think that this should be configurable somewhere in the /etc/VRTSralus/ralus.cfg file, but it seems there is no document that contains *complete* information on what is and could be in that file. I would like to have the process always create CdbsMutex in /var/run, /var/run/VRTSralus, or somewhere down the /var/VRTSralus directory tree. As a matter of fact, a best practice would be to not have it be created in whichever directory you happen to be in when starting beremote. Thanks in advance for any information. - Bruce S.