Backup Exec 11d - RALUS 7170 - CentOS5 - SOLVED

SOLVED -

After surfing the Symantec support forums, I found other users that said 64bit CentOS5, and RHEL5 experience this problem, where the 32bit versions don't. I reinstalled with 32bit, and problem now gone!

Now I wish Symantec fixes their software...

Agent installs

I can make selections of folders I want to backup

Backup fails (I had sucessful backups earlier this week).

Symantec does not support RHEL5 or CentOS5 with RALUS. RHEL5 version should be out soon, but no eta.

Debug info:

43204940 Fri Aug 17 12:45:26 2007 : VX_EnumExcludedFiles: FilesNotToBackup and Hardcoded exclusion files:
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\dev\*.* /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\proc\*.* /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\mnt\nss\pools\ /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\mnt\nss\.pools\ /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\sys\*.* /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\_admin\*.* /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\dev\* /s
43204940 Fri Aug 17 12:45:26 2007 : [ROOT]\xfn\* /s
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_GetLocalDeviceName: device_name is [ROOT]
43204940 Fri Aug 17 12:45:26 2007 : B
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 :
43204940 Fri Aug 17 12:45:26 2007 : Detach from: \\server04.embassy.lan\[ROOT]
43204940 Fri Aug 17 12:45:26 2007 : Resetting hard link info
43204940 Fri Aug 17 12:45:26 2007 : Hard link info has been reset
43204940 Fri Aug 17 12:45:26 2007 : Backup Job Start - Fri Aug 17 12:45:26 2007
43204940 Fri Aug 17 12:45:26 2007 : ====>VX_AttachToDLE
43204940 Fri Aug 17 12:45:26 2007 : Resetting hard link info
43204940 Fri Aug 17 12:45:26 2007 : Hard link info has been reset
43204940 Fri Aug 17 12:45:26 2007 : VX_AttachToDLE: initializing mount list
43204940 Fri Aug 17 12:45:26 2007 : VX_AttachToDLE: create mount list returned 0
43204940 Fri Aug 17 12:45:26 2007 : Attach to: \\server04.embassy.lan\[ROOT]
Segmentation fault

Found this:

https://forums.symantec.com/syment/board/message?board.id=115&message.id=11114#M11114

https://forums.symantec.com/syment/board/message?board.id=115&message.id=2053&query.id=178181#M2053

NO SOLUTION...

https://forums.symantec.com/syment/board/message?board.id=115&message.id=19371&query.id=6596#M19371

CentOS5 (RHEL5) + 9TB Drive + AD + Win/OSX clients + BackupEXEC

I have setup a CentOS5 file server for a client.

Here is a log of what I did to get it working:

• CentOS5 install following - http://www.howtoforge.com/perfect_setup_centos5.0
  
  • Selecting to install the following packages - Select Editors, Text-based Internet, Development Libraries, Development Tools, Mail Server, Server Configuration Tools, Administration Tools, Base, and System Tools
• Don't bother installing CentOS onto a server that has that onboard SATA raid controllers! I had a dead drive in testing, and the server didn't just keep going on the redundant mirrored drive... :(
• Webmin
  • http://www.hornfordassociates.com/resources/how-to-library/virtual-centos-5.html
  • change port to 10001 because BackupExec agent also uses port 10000
  • Also used their instructions for cleaning up the basic CentOS install (sans gui)
    
    • yum remove finger gaim cups-libs bluez-libs desktop-file-utils
    • yum remove Deployment_Guide-en-US<
    • yum install postfix
    • yum remove sendmail
• RPM Forge
  • http://wiki.centos.org/Repositories/RPMForge
• Samba
  
  • http://www.brentnorris.net/blog/?p=179
  • http://www.howtoforge.com/samba_ads_security_mode
  • yum install samba
  • /etc/hosts - have the fqdn for the server and all DCs
• fstab
• krb5.conf
• nsf: - /etc/exports
  
  • I setup NFS using these instructions: http://www.jontodd.com/2006/07/24/setting-up-nfs-server-on-fedora-core-5-with-os-x-nfs-client/
  • And when I dug into the site, I may have found a solution to the file transfer speed: http://www.bresink.de/osx/143439/issues.html
    • I made the changes as suggested to /etc/exports
    • /mnt/raid03 192.168.23.0/255.255.255.0(rw,insecure,async)
    • Automounting from another server was a prob, this was the solution: http://crazytoon.com/2007/05/11/centos-and-redhat-problem-nfs-mount-at-boot-up-fails-with-error-system-error-no-route-to-host/
      

formatting the 9TB --F switch

• As for formatting the data store raid, I found out I needed to use a -F switch to force/push it over 8TB.
  Also use -m 0 so that it only uses 0% reserved for root
  Also -T largefile4

• [root@server03 ~]# mke2fs -j -b 4096 /dev/sdc
  mke2fs 1.39 (29-May-2006)
  /dev/sdc is entire device, not just one partition!
  Proceed anyway? (y,n) y
  mke2fs: Filesystem too large. No more than 2**31-1 blocks
  (8TB using a blocksize of 4k) are currently supported.
  

  [root@server03 ~]# mke2fs -j -F -b 4096 /dev/sdc
  mke2fs 1.39 (29-May-2006)
  Filesystem label=
  OS type: Linux
  Block size=4096 (log=2)
  Fragment size=4096 (log=2)
  1188610048 inodes, 2377197056 blocks
  118859852 blocks (5.00%) reserved for the super user
  First data block=0
  Maximum filesystem blocks=4294967296
  72547 block groups
  32768 blocks per group, 32768 fragments per group
  16384 inodes per group
  Superblock backups stored on blocks:
  32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
  4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
  102400000, 214990848, 512000000, 550731776, 644972544, 1934917632

  Writing inode tables: done
  Creating journal (32768 blocks): done
  Writing superblocks and filesystem accounting information: done
  

  So now...

  [root@server03 ~]# df -h
  Filesystem Size Used Avail Use% Mounted on
  /dev/md1 287G 2.4G 270G 1% /
  /dev/md0 99M 15M 79M 16% /boot
  tmpfs 2.0G 0 2.0G 0% /dev/shm
  /dev/sdc 8.8T 170M 8.3T 1% /raid03
  [root@server03 ~]# df
  Filesystem 1K-blocks Used Available Use% Mounted on
  /dev/md1 300708280 2442184 282744500 1% /
  /dev/md0 101018 15189 80613 16% /boot
  tmpfs 2023964 0 2023964 0% /dev/shm
  /dev/sdc 9359579336 173276 8883966652 1% /raid03
  [root@server03 ~]#

mount the drive - mount -t ext3 /dev/sdb /mnt/sharename

chmod -R 777 /mnt/sharename

start ntpd on startup - add server 0.pool.ntp.org

OSX uid/gid issue

To install the latest version of the BackupExec Agent for linux, I followed this tip: RALUS + RHEL 5 libstdc++so.6

• yum update (to bring your system up to date with RHN.)
• yum search compat-libstdc (this should list the two current versions of the compatible libraries)
• yum install compat-libstdc++-33 (this will install the GCC version)

Nic bonding:

• https://www.openfiler.com/community/forums/viewtopic.php?id=917
• http://linux-net.osdl.org/index.php/Bonding#Configuring_Bonding_for_Maximum_Throughput
• http://linux-net.osdl.org/index.php/Bonding
• http://www.howtoforge.com/network_card_bonding_centos

Configure HP ProCurve for LACP port trunking...

Setup rsync between servers:

• /etc/fstab -> server03:/mnt/raid03 /mnt/raid03 nfs defaults 0 0
• rsync --delete --archive --stats --progress /mnt/raid03/ /mnt/raid04/
• setup cron job
• echo "`date +"%F %R"`: Start backup" >> /root/rsync/log.txt
  rsync --archive --delete --stats --ignore-errors --exclude=**/BNR/build --exclude=**/BNR4/build --exclude=**/.TemporaryItems /mnt/raid03/ /mnt/raid04/ >> /root/rsync/log.txt
  echo "`date +"%F %R"`: Finish backup-jd" >> /root/rsync/log.txt
  cp /root/rsync/log.txt /mnt/raid03/rsynclog/
• This excludes the BNR open files and stops it from crashing