cancel
Showing results for 
Search instead for 
Did you mean: 

MSEO: vmtape driver not loaded

evargas
Level 4
Certified

Hi,

I am trying to install MSEO on a Linux RHEL 5 and I am getting these errors

on the server side

error: Failed dependencies:
        libXtst.so.6 is needed by mseo-server-6.1.3-rhel5.x86_64
Upgrade failed. Your old configuration is saved in /tmp/server.tar.
Please do a fresh installation and then restore the configuration.

I installed the package but still no luck

rpm -qa |grep -i libXtst
libXtst-1.0.1-3.1

on the client side

Starting install
Agent driver /opt/vormetric/mseo/agent/drv/2.6.18-194.el5/vmtape.ko not found
** Install failed **
/var/tmp/rpm-tmp.4109: line 5: return: can only `return' from a function or sourced script
insmod: can't read '/opt/vormetric/mseo/agent/drv/2.6.18-194.el5/vmtape.ko': No such file or directory
mseo.agent: vmtape failed to load

whe i run the cgconfig device I get this

./cgconfig device
OS = LINUX
/opt/vormetric/mseo/agent/lib/cgc.lin: line 223: [: -gt: unary operator expected
vmtape driver not loadedI

I tried different versions with same result

MSEO 6.1.1

MSEO 6.1.2

MSEO 6.1.3

MSEO 6.1.4

Any insite will be appreciated, did i miss something?

Thanks

 

Efrain Vargas
1 ACCEPTED SOLUTION

Accepted Solutions

CRZ
Level 6
Employee Accredited Certified

Riann's post is better than mine, but here's some general info for you:

MSEO is supported on RedHat 5 update 2 and above from version 6.1.3:

NetBackup (tm) 7.x Operating System Compatibility List (Updated July 28, 2014)
 http://symantec.com/docs/TECH76648 (see page 67)

HOWEVER, MSEO 6.x will be EOSL in December...

NetBackup Product Group End of Support Life matrix
 http://symantec.com/docs/TECH74757

...so I would recommend trying to install MSEO 7.6, which came out the same time NetBackup 7.6 did.

MSEO 7.6 is available from FileConnect if you do not already have it.  (You will need a license to access it.)

 http://fileconnect.symantec.com/

You will still probably need to heed Riann's advice.

(But do make sure you're at Update 2 or later first!)

Here's a link to the MSEO 7.6 documentation:

NetBackup Media Server Encryption Option (MSEO) 7.6 Documentation
 http://symantec.com/docs/DOC7051

View solution in original post

3 REPLIES 3

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified

Which versions are you using?

 

These are from the release notes and refer to rhel 6, but I'm sure it would apply to 5 too.

 

  1. X11 X Window packages must be running for you to install MSEO software on a Linux or Solaris host. The installer will fail without X Window libraries Also, X Window is required to run the MSEO server or agent GUI remotely. That is, X Window is required if you want to run the MSEO server or agent on a remote system but display the MSEO server interface or agent interface locally. The installer checks X Window dependencies and returns an error if the required packages are not installed. For example

    ...
    Enter port number for CA server 10.3.1.121 [8085] or type quit: Enter the server key size [1024]:
    Starting install
    error: Failed dependencies:

    libX11.so.6()(64bit) is needed by mseo-server-6.1.7-rhel6.x86_64 libXext.so.6()(64bit) is needed by mseo-server-6.1.7-rhel6.x86_64 libXi.so.6()(64bit) is needed by mseo-server-6.1.7-rhel6.x86_64 libXt.so.6()(64bit) is needed by mseo-server-6.1.7-rhel6.x86_64 libXtst.so.6()(64bit) is needed by mseo-server-6.1.7-rhel6.x86_64

Not all the missing libraries may be displayed at one time. You will have to run the installer iteratively until it completes successfully. If the installer fails, or you are unable to display the MSEO interface remotely, run the native installer (pkginfo or rpm) on the system that is hosting MSEO and verify that the libX11 and libXt libraries are installed. The required X Window libraries for a Red Hat 6 host are:

libICE-1.0.6-1.el6.x86_64.rpm libSM-1.1.0-7.1.el6.x86_64.rpm libX11-1.3-2.el6.x86_64.rpm libX11-common-1.3-2.el6.noarch.rpm libXau-1.0.5-1.el6.x86_64.rpm libXext-1.1-3.el6.x86_64.rpm libXi-1.3-3.el6.x86_64.rpm libXt-1.0.7-1.el6.x86_64.rpm libXtst-1.0.99.2-3.el6.x86_64.rpm libxcb-1.5-1.el6.x86_64.rpm

yum --nogpgcheck localinstall

Refer to the X Window user documentation, or search online, to solve X Window configuration issues. (MSEO-2168)

 

 

 

CRZ
Level 6
Employee Accredited Certified

Riann's post is better than mine, but here's some general info for you:

MSEO is supported on RedHat 5 update 2 and above from version 6.1.3:

NetBackup (tm) 7.x Operating System Compatibility List (Updated July 28, 2014)
 http://symantec.com/docs/TECH76648 (see page 67)

HOWEVER, MSEO 6.x will be EOSL in December...

NetBackup Product Group End of Support Life matrix
 http://symantec.com/docs/TECH74757

...so I would recommend trying to install MSEO 7.6, which came out the same time NetBackup 7.6 did.

MSEO 7.6 is available from FileConnect if you do not already have it.  (You will need a license to access it.)

 http://fileconnect.symantec.com/

You will still probably need to heed Riann's advice.

(But do make sure you're at Update 2 or later first!)

Here's a link to the MSEO 7.6 documentation:

NetBackup Media Server Encryption Option (MSEO) 7.6 Documentation
 http://symantec.com/docs/DOC7051

mph999
Level 6
Employee Accredited

I didn't have time to post previouly, but I've had a look in the sym DB and this type of issue seems often to be down to something being incompatible. I'm sure you've checked, but f not have a peep in the compatibility guide.

Other notes: Back up the keys, best to create a new profile and not use default ('cos if 'someone' reinstalled mseo it would carry on working but with new keys which you would be unaware of ...) See the release notes for DISABLE_WRITE_IMMEDIATE_EOF touchfile, which MUST be in place if you are at NBU 7.1 or above.

If you are using LTO4 or above, or other drives that support hardware encryption, I'd recomend KMS, not MSEO. It's far simplier, for a start it's already installed, you just have to generate keys to activate it. It's 'faster', more or less no overhead on the servers and just a superior solution.