Connect
email: vic @ hong . com . au
mobile: +1 604-783-6519
office: +1 604-677-2829


Search
Twitter Updates

    Blog Categories
    Section2

    Entries in backupexec (2)

    Tuesday
    Oct202009

    Nexenta + NDMP Backup with BackupExec 12.5 + low free space issues

    NexentaStor has been lots of fun to work with, there are still a few hickups as mentioned earlier in my blog, but it is turning out to be a pretty cool solution for clients that are not wanting to throw down big bucks on boutique NAS/SANes during this recession. Oh, and do I hear de-dupe is around the corner for ZFS?! :)

    I was experimenting around with the NDMP Backup options in NexentaStor. I enabled the service, and punched in the details of our Symantec BackupExec 12.5 server, with NDMP option enabled.

    Not being really familiar with this option in BackupExec, I just set everything pretty much with the default, and unfortunately, when browsing for backup devices, Nexenta does not appear in the NDMP devices, so off I went and logged a support ticket with Nexenta.

    Here is their response, not holding my breath, but it would be seriously kick ass if NDMP backups did work with BackupExec (not to mention would get great speed, and can point backups to "latest" folders within a special backup snapshot for example - nice point in time backups/archives to tape!)

    Looks like we do not have many customers using BackupExec. In general, this is our policy to support 3rd party software only if there is enough evidence that this is either a standard, or used by a significant number of users (which would make it de-facto standard). BackupExec is neither. We may be able though to get to it after the next major release 3.0 planned for end of November, early Dec.

    Now onto free space in NexentaStor. I do encourage you to keep a close eye on available space on your volumes. We were in a situation where a slight mistake in a rsync script, filled up our Nexenta box. We had on or less than 10% space left, and it ended up with some strange behaviour.

    Everything from no access via web interface, the console on the server locking up when trying to remove snapshots via the web interface, and errors and dead drives appearing after scrub jobs were issued (which weren't really dead drives!). After we blew away a bunch of stuff, and snapshots via command line (setup snapshot destroy), things settled down again.

    I really like the weekly reports that the system can send to you, surf through them just to make sure available space is in check, and all should be fine.

    Monday
    Jul232007

    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:

  • 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