Highlighted
Anonymous_User Absent Member.
Absent Member.
2296 views

TSM Client OES/Linux in closed beta

Just for all waiting for a tsm client from ibm ...

I got today a beta version (5.3.4.2) with which we can backup our nss
volumes on oes/linux !

The client is still in closed beta and will be released in jan 2007. We got
it even we are not in that beta program. So there is no support for that
client for us. For now the client can only backup / restore the files
without trustees. For us it's okay right now. So we can migrate some test
netware server to oes/linux. The only requirement the tsm client has right
now is the kernel version 2.6.5.7.276.

Rainer
Labels (2)
0 Likes
9 Replies
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

On Tue, 24 Oct 2006 18:43:34 +0000, Rainer Brunold wrote:

> Just for all waiting for a tsm client from ibm ...
>
> I got today a beta version (5.3.4.2) with which we can backup our nss
> volumes on oes/linux !
>
> The client is still in closed beta and will be released in jan 2007. We
> got it even we are not in that beta program. So there is no support for
> that client for us. For now the client can only backup / restore the files
> without trustees. For us it's okay right now. So we can migrate some test
> netware server to oes/linux. The only requirement the tsm client has right
> now is the kernel version 2.6.5.7.276.


Thanks for the info!

--
Mark Robinson
Novell Volunteer SysOp

One by one the penguins steal my sanity...

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Rainer Brunold wrote:

> Just for all waiting for a tsm client from ibm ...
>
> I got today a beta version (5.3.4.2) with which we can backup our nss
> volumes on oes/linux !
>
> The client is still in closed beta and will be released in jan 2007.
> We got it even we are not in that beta program. So there is no
> support for that client for us. For now the client can only backup /
> restore the files without trustees. For us it's okay right now. So we
> can migrate some test netware server to oes/linux. The only
> requirement the tsm client has right now is the kernel version
> 2.6.5.7.276.
>
> Rainer


you made my day!

--

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Hmmm...we've had no problem backing up/restoring NSS data with the current
production TSM client. It's far from ideal, as it can't handle any NSS
metadata. We use metamig in a preschedulecmd directive to catch the
trustees, but lack of file ownership restores is a big problem for us.

Sorry to be dense, but...just what does this beta client offer over the
previous version if it can't handle trustees?


"Rainer Brunold" <Rainer.Brunold@Brunold.AT> wrote in message
news:q9t%g.18488$0h7.15124@prv-forum2.provo.novell.com...

> For now the client can only backup / restore the files
> without trustees.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Hi Bill,

so I think you are one of the only ones who could do that.

We were waiting very long for nss support from ibm and have currently some
different tsm client versions installed. No one could backup the nss
filesystems except the beta 5.3.4.2. Even we have on some server the latest
version 5.3.4.3 installed, it couldn't backup nss on linux. Maybe you got
as a lucky user just exact that 5.3.4.2 that could do it. But I think many
people here are waiting for the final release of it.

Rainer




Bill wrote:

> Hmmm...we've had no problem backing up/restoring NSS data with the current
> production TSM client. It's far from ideal, as it can't handle any NSS
> metadata. We use metamig in a preschedulecmd directive to catch the
> trustees, but lack of file ownership restores is a big problem for us.
>
> Sorry to be dense, but...just what does this beta client offer over the
> previous version if it can't handle trustees?
>
>
> "Rainer Brunold" <Rainer.Brunold@Brunold.AT> wrote in message
> news:q9t%g.18488$0h7.15124@prv-forum2.provo.novell.com...
>
>> For now the client can only backup / restore the files
>> without trustees.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Yeah, been waiting for this, over 1.5 years now. Policy dictates that we
won't touch anything in beta, so we'll probably be waiting 2+ years for the
final release. Not acceptable.

-Eric

"Rainer Brunold" <Rainer.Brunold@Brunold.AT> wrote in message
news:u%H1h.22276$0h7.8909@prv-forum2.provo.novell.com...
> Hi Bill,
>
> so I think you are one of the only ones who could do that.
>
> We were waiting very long for nss support from ibm and have currently some
> different tsm client versions installed. No one could backup the nss
> filesystems except the beta 5.3.4.2. Even we have on some server the
> latest
> version 5.3.4.3 installed, it couldn't backup nss on linux. Maybe you got
> as a lucky user just exact that 5.3.4.2 that could do it. But I think many
> people here are waiting for the final release of it.
>
> Rainer
>
>
>
>
> Bill wrote:
>
>> Hmmm...we've had no problem backing up/restoring NSS data with the
>> current
>> production TSM client. It's far from ideal, as it can't handle any NSS
>> metadata. We use metamig in a preschedulecmd directive to catch the
>> trustees, but lack of file ownership restores is a big problem for us.
>>
>> Sorry to be dense, but...just what does this beta client offer over the
>> previous version if it can't handle trustees?
>>
>>
>> "Rainer Brunold" <Rainer.Brunold@Brunold.AT> wrote in message
>> news:q9t%g.18488$0h7.15124@prv-forum2.provo.novell.com...
>>
>>> For now the client can only backup / restore the files
>>> without trustees.

>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

The Linux client we are using is 5.3.2, and is working fine on numerous
servers, with the exception of the previously mentioned NSS metadata
problem. For other Tivoli customers out there, perhaps some more details
might be helpful...

- We've used the standard Tivoli Linux agent successfully on every version
of OES since 1.0, up to and including servers with all of the lastest
patches.

- All of our OES Linux servers are Dell boxes, with one large physical RAID
array, containing two logical drives. One relatively small logical drive for
the OS, the remainder for the NSS volume.

- At some point in time, the NSS volumes did start failing to get backed up.
Sorry, I don't recall if it was due to a Tivoli agent upgrade, or an OES
service pack/patch. Regardless, when this happened, we referenced the NSS
volumes with the VIRTUALMountpoint directive. You can issue multiple
directives if you have more than one NSS volume. An example from one of our
dsm.sys configs:

VIRTUALMountpoint /media/nss/DATA

- As has been mentioned a few times here, running metamig prior to a backup
allows you to catch trustees. For Tivoli, the following directive in the
dsm.sys file handles it for us. It creates a trustee export file, with the
current date/time appended. Adjust the NSS volume/export file name as
necessary:

preschedulecmd "metamig save DATA > /backup/nss-trustees-data_`date
+%Y-%m-%d-%k:%M:%S`"

<rant>
Can't wait for true NSS support, though...and while I'm glad IBM is finally
getting around to it, there's simply no excuse for the delay. Companies with
far fewer resources have had NSS solutions for well over a year now...
</rant>

Bill

"Rainer Brunold" <Rainer.Brunold@Brunold.AT> wrote in message
news:u%H1h.22276$0h7.8909@prv-forum2.provo.novell.com...
> Hi Bill,
>
> so I think you are one of the only ones who could do that.
>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Right, the issue here is -support-. IBM doesn't support it.

Think about this:
We are not betting our jobs and our company's data on an unsupported backup
solution, are you?

Hope not,
Eric

"Bill" <replyhere@noemail.com> wrote in message
news:yjM1h.22517$0h7.15207@prv-forum2.provo.novell.com...
> <rant>
> Can't wait for true NSS support, though...and while I'm glad IBM is
> finally getting around to it, there's simply no excuse for the delay.
> Companies with far fewer resources have had NSS solutions for well over a
> year now...
> </rant>



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

> We are not betting our jobs and our company's data on an unsupported
> backup solution, are you?


Sure...and I sleep fine at night. But I don't view vendor support as some
sort of holy grail. While important, it's certainly not the determining
factor in every technology decision.

We have plenty of critical data being backed up using this unsupported
method, for one simple reason. My marching orders were clear - "Get off of
Netware."

Given that we have obscene amounts of money invested in Tivoli, any solution
that involved another enterprise backup product for 20+ servers would
quickly get kicked to the curb. So...if I wanted a supported Tivoli
solution, that meant migrating from Netware to Windows Server (for which we
have sufficient CAL's), or a non-OES version of Linux running Samba. Excuse
me while I walk down to the pub, and get seriously inebriated trying to pick
one of those options...

Or, I could go with a temporarily unsupported backup solution that we've
tested thoroughly and know to work, along with OES Linux.

Now...which of those choices involves more risk? Which has more user and
administrative impact? Which continues to work with our existing Novell
tools? Which can be done in a reasonable amount of time by one
Novell-skilled person? Which avoids touching 2500 PC's due to an installed
Novell Client?

I'll take "Unsupported backup solutions for $1000", Alex. 😉


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: TSM Client OES/Linux in closed beta

Well, I do agree with your points. We have a serious Tivoli and Netware
investment as well. Thing is, we've been seriously burned in the past for
having unsupported configurations. It's really surprising how quickly you
will be refused support no matter how business-critical the situation is 😞

At least in your case, you have those "marching orders" that you can blame,
if something does go catastrophically wrong with your environment.

-Eric

"Bill" <replyhere@noemail.com> wrote in message
news:DuQ1h.22842$0h7.9081@prv-forum2.provo.novell.com...
>> We are not betting our jobs and our company's data on an unsupported
>> backup solution, are you?

>
> Sure...and I sleep fine at night. But I don't view vendor support as some
> sort of holy grail. While important, it's certainly not the determining
> factor in every technology decision.
>
> We have plenty of critical data being backed up using this unsupported
> method, for one simple reason. My marching orders were clear - "Get off of
> Netware."
>
> Given that we have obscene amounts of money invested in Tivoli, any
> solution that involved another enterprise backup product for 20+ servers
> would quickly get kicked to the curb. So...if I wanted a supported Tivoli
> solution, that meant migrating from Netware to Windows Server (for which
> we have sufficient CAL's), or a non-OES version of Linux running Samba.
> Excuse me while I walk down to the pub, and get seriously inebriated
> trying to pick one of those options...
>
> Or, I could go with a temporarily unsupported backup solution that we've
> tested thoroughly and know to work, along with OES Linux.
>
> Now...which of those choices involves more risk? Which has more user and
> administrative impact? Which continues to work with our existing Novell
> tools? Which can be done in a reasonable amount of time by one
> Novell-skilled person? Which avoids touching 2500 PC's due to an installed
> Novell Client?
>
> I'll take "Unsupported backup solutions for $1000", Alex. 😉
>



0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.