snmdla-tm
2 Iron

backup SLES 12

Jump to solution

October 27, 2014 saw the general availability of SUSE Enterprise Server 12 (SLES 12).

Today I tried to install a SLES 12 VM, but was disappointed to learn that there appears to be no EMC Networker client available for it.

When installing, you will run into something like


   error: Failed dependencies:

       libstdc++.so.5()(64bit) is needed by lgtoclnt-8.2.0.5-1.x86_64

       libstdc++.so.5(CXXABI_1.2)(64bit) is needed by lgtoclnt-8.2.0.5-1.x86_64

       libstdc++.so.5(GLIBCPP_3.2)(64bit) is needed by lgtoclnt-8.2.0.5-1.x86_64

       libstdc++.so.5(GLIBCPP_3.2.2)(64bit) is needed by lgtoclnt-8.2.0.5-1.x86_64

Has anybody managed to backup a SLES 12 VM using the networker client?

Thanks, TM

0 Kudos
1 Solution

Accepted Solutions
snmdla-tm
2 Iron

Re: Re: backup SLES 12

Jump to solution

With the help of Novell Support we found the following clean solution,

which utilizes the service channel "Legacy_Module_12_86_64", to

provide the - as novell support call it - ancient Version of libstdc++

that the Networker client needs:

1.) Installation of Legacy Module 12

  host:/ # yast2 repositories

  <add>

  Available Extensions and Modules

  ...

  Legacy Module 12 x86_64

  ...

  <Finish>

  after that:

  host:/ #  zypper lr

  #  | Alias                                                          | Name                                  | Enabled | Refresh

  ---+-----------------------------------------------------------------+---------------------------------------+---------+--------

    1 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Debuginfo-Pool      | SLE-Module-Legacy12-Debuginfo-Pool    | Yes    | No

    2 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Debuginfo-Updates  | SLE-Module-Legacy12-Debuginfo-Updates | Yes    | Yes

    3 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Pool                | SLE-Module-Legacy12-Pool              | Yes    | No

    4 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Updates            | SLE-Module-Legacy12-Updates          | Yes    | Yes

    ...

  host:/ #

2.) Installation of libstdc++

  zypper in libstdc++33 libstdc++33-32bit

now we have:

  host:/dir/# # rpm -ql libstdc++33

  /usr/lib64/libstdc++.so.5

  /usr/lib64/libstdc++.so.5.0.7

  host:/dir/ # rpm -ql libstdc++33-32bit

  /usr/lib/libstdc++.so.5

  /usr/lib/libstdc++.so.5.0.7

  host:/dir/ #

3.) finally, the installation of Legato Client, e.g. Version 8.2

  host:/dir/ # rpm -U lgtoclnt-8.2.0.5-1.x86_64.rpm

  host:/dir/ #

The networker service is now running cleanly, as does the backup of

the SLES 12 host   

Regards, Thomas

0 Kudos
4 Replies
crazyrov
4 Tellurium

Re: backup SLES 12

Jump to solution

Have you tried resolving the dependencies and re-trying ?

0 Kudos
snmdla-tm
2 Iron

Re: backup SLES 12

Jump to solution

Yes, we did, to no avail. We even tried a forced install, but the utilities like "save" and "recover" won't run.

0 Kudos
Highlighted
bingo.1
4 Germanium

Re: backup SLES 12

Jump to solution

I am pretty sure that the latest client will work ... even it has not been approved yet.

What you are missing are some older libraries which are not part of the EMC software. Search the internet for download locations. As soon as they do exist, I expect NW to install just fine.

snmdla-tm
2 Iron

Re: Re: backup SLES 12

Jump to solution

With the help of Novell Support we found the following clean solution,

which utilizes the service channel "Legacy_Module_12_86_64", to

provide the - as novell support call it - ancient Version of libstdc++

that the Networker client needs:

1.) Installation of Legacy Module 12

  host:/ # yast2 repositories

  <add>

  Available Extensions and Modules

  ...

  Legacy Module 12 x86_64

  ...

  <Finish>

  after that:

  host:/ #  zypper lr

  #  | Alias                                                          | Name                                  | Enabled | Refresh

  ---+-----------------------------------------------------------------+---------------------------------------+---------+--------

    1 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Debuginfo-Pool      | SLE-Module-Legacy12-Debuginfo-Pool    | Yes    | No

    2 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Debuginfo-Updates  | SLE-Module-Legacy12-Debuginfo-Updates | Yes    | Yes

    3 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Pool                | SLE-Module-Legacy12-Pool              | Yes    | No

    4 | Legacy_Module_12_x86_64Smiley FrustratedLE-Module-Legacy12-Updates            | SLE-Module-Legacy12-Updates          | Yes    | Yes

    ...

  host:/ #

2.) Installation of libstdc++

  zypper in libstdc++33 libstdc++33-32bit

now we have:

  host:/dir/# # rpm -ql libstdc++33

  /usr/lib64/libstdc++.so.5

  /usr/lib64/libstdc++.so.5.0.7

  host:/dir/ # rpm -ql libstdc++33-32bit

  /usr/lib/libstdc++.so.5

  /usr/lib/libstdc++.so.5.0.7

  host:/dir/ #

3.) finally, the installation of Legato Client, e.g. Version 8.2

  host:/dir/ # rpm -U lgtoclnt-8.2.0.5-1.x86_64.rpm

  host:/dir/ #

The networker service is now running cleanly, as does the backup of

the SLES 12 host   

Regards, Thomas

0 Kudos