If you are thinking about Enterprise backup solutions when implementing Novell OES2 SP1 Linux, please be aware of the following regarding Symantec NetBackup v6.5.x (formerly known as Veritas NetBackup).
- NSS volumes on OES2 SP1 Linux are supported with NBU 6.5.1 using the Linux Agent (the SLES agent)
- You need to make sure to edit your /etc/opt/novell/nss/nssstart.cfg file (or use nsscon) to have the following two settings:
- Symantec has a bug where your backup jobs will be marked as “failed” because it does not exclude the mount point of /opt/novell/nss/mnt/.pools However, even if you are able to create the exclude mount point file and put that exclusion list in, NBU does not read this file properly. Unfortunately the fix is a binary level patch from Symantec (specific to each version of the agent, 6.5.2, 6.5.3, 6.5.4, etc.) This patch can only be obtained from Symantec. They were supposed to include this in 6.5.4 and have not. The latest we have heard is that Symantec “may” include this in 6.5.7 or 7.0 of the NBU product. You may have to refer to case #320-151-041 to get the patch.
- If you use Compression on your NSS volumes, NBU will decompress the files every time they are backed up. This is because NBU does not use ANY TSA code from Novell at all. Only Linux APIs. You will need to buy more disks. This means you also will have problems with the following
- You cannot backup your GroupWise data because NBU won’t use TSAFS /enableGW=yes, or TSAFSGW. Your only choice will be to double your drive space in your entire Enterprise for your GroupWise data and spend the time to use dbcopy to copy the data to a secondary storage volume and then use NBU to back up the copy. Or switch to MS Exchange or another backup product.
- Also, if you use iFolder, this means you cannot use TSAIFS to properly backup iFolder either.
- Beginning in NBU v6.5.2 (server-side, not agent side), Symantec introduced a bug where a TIR (True Image Restore) option will cause any differential (or incremental) backups on any platform (We tested on NetWare, SLES 10 SP2/OES2 SP1, and Sun Solaris) to take about 5x longer than previous backups. Symantec was supposed to have fixed this in 6.5.4, but our testing says it’s not fixed. The only workaround is to not use TIR (turn off the option).
- The only good thing about item #4 (not using any TSA code) is that you can now utilize Synthetic backups and checkpoint restarts on your OES2 servers.
If you are already a Symantec NBU customer with NetWare and are thinking about converting to OES2 SP1 Linux, please let Novell and Symantec know that the above items should be addressed in a timely matter.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.