Log prune on non-standard log names?

[Large, M (Matthew)]

Hi All,

One of my customers recently came to me to say that they had a 100MB log
file from TSM sitting in their file system, which confused me since the
setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlognamedsmsched_1yr.log

Does anyone know if I should expect these settings to prune the
dsmsched_1yr.log or must I manually trim this file when necessary?

Clients - 5.2.4.4
Server - 5.2.7.1

Many Thanks,
Matthew

TSM Consultant
ADMIN ITI
Rabobank International
1 Queenhithe, London
EC4V 3RL

0044 207 809 3665


_

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_

Incremental Forever Question

[Adrian Compton]

Hello all

Can anyone confirm for me that when using the Incremental Forever method of
backing up, do you get a full offsite copy of the particular node in
question (AIX, 2003, etc) when doing an OFFSITE Create each day.

I am presumeing that one does from my understanding of this approach.

Thanks in advance.

Adrian Compton

Aspen Pharmacare Port Elizabeth
Tel: +27 (0) 41 407 2070
Fax: +27 (0) 41 453 7452
Cell: 082 320 4495
Email : [EMAIL PROTECTED]   This email is solely for the named
addressee.   Any unauthorised use or interception of this email, or the
review, retransmission, dissemination or other use of, or taking of any
action in reliance upon the contents of this email, by persons or entities
other than the intended recipient, is prohibited. If you are not the named
addressee please notify us immediately by way of a reply e-mail, and also
delete this email and any attached files.

Disclaimer:  You must scan this email and any attached files for viruses
and/or any other defects.  Pharmacare Limited accepts no liability for any
loss, damages or consequence, whether direct, indirect, consequential or
economic, however caused, and whether by negligence or otherwise, which may
result directly or indirectly from this communication or of any attached
files.

Re: Log prune on non-standard log names?

[David McClelland]

Hi Matthew,

Is your customer's TSM client scheduled using the TSM Central Scheduler
(I guess so if it's growing to over 100MBs) for backup operations? This
kind of log pruning only happens during a TSM scheduled backup operation
(not when the backup operation is scheduled via TWS/cron/Windows
Scheduler etc). There's certainly nothing in the docs that I've found to
suggest that changing the schedlogname will prevent pruning (it would be
a travesty if it did). As an off-the-wall suggestion, have you tried
switching the order in which the two options appear in the dsm.opt? 

Rgds,

David McClelland
Data Protection Specialist
IBM Tivoli Storage Manager Certified Consultant
Shared Infrastructure Architecture and Design 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Large, M (Matthew)
Sent: 12 September 2006 08:27
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Log prune on non-standard log names?

Hi All,

One of my customers recently came to me to say that they had a 100MB log
file from TSM sitting in their file system, which confused me since the
setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlognamedsmsched_1yr.log

Does anyone know if I should expect these settings to prune the
dsmsched_1yr.log or must I manually trim this file when necessary?

Clients - 5.2.4.4
Server - 5.2.7.1

Many Thanks,
Matthew

TSM Consultant
ADMIN ITI
Rabobank International
1 Queenhithe, London
EC4V 3RL

0044 207 809 3665


_

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_


To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender, except 
where the sender specifically states them to be the views of Reuters Ltd.

Re: Log prune on non-standard log names?

[Richard Sims]

On Sep 12, 2006, at 3:27 AM, Large, M (Matthew) wrote:


One of my customers recently came to me to say that they had a
100MB log
file from TSM sitting in their file system, which confused me since
the
setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlognamedsmsched_1yr.log

...

Matthew -

Get the specifics ... the file name, and latest timestamp (for context).
What they're looking at may be a dsmerror.log file, which can be large
as it accumulates endlessly over time - ignored until it gets huge.
If some other log, its timestamp will provide evidence as to what is
writing to it, in terms of scheduled or invoked events.

   Richard Sims

Re: Incremental Forever Question

[Richard Sims]

On Sep 12, 2006, at 4:27 AM, Adrian Compton wrote:


Can anyone confirm for me that when using the Incremental Forever
method of
backing up, do you get a full offsite copy of the particular node in
question (AIX, 2003, etc) when doing an OFFSITE Create each day.


Adrian -

I think you are referring to a Backup Stgpool operation - which is as
incremental as the client backups usually are - and will cumulatively
generate a complete image for offsite if allowed to run to completion.

Richard Sims http://people.bu.edu/rbs

Re: Log prune on non-standard log names?

[Large, M (Matthew)]

Hi David,

We're using the TSM scheduler so it should be managed properly. I'll put
them in a different order on this machine and see if it makes a
difference.

Thanks for the suggestion. 

Regards,
Matthew
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David McClelland
Sent: 12 September 2006 10:53
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log prune on non-standard log names?

Hi Matthew,

Is your customer's TSM client scheduled using the TSM Central Scheduler
(I guess so if it's growing to over 100MBs) for backup operations? This
kind of log pruning only happens during a TSM scheduled backup operation
(not when the backup operation is scheduled via TWS/cron/Windows
Scheduler etc). There's certainly nothing in the docs that I've found to
suggest that changing the schedlogname will prevent pruning (it would be
a travesty if it did). As an off-the-wall suggestion, have you tried
switching the order in which the two options appear in the dsm.opt? 

Rgds,

David McClelland
Data Protection Specialist
IBM Tivoli Storage Manager Certified Consultant Shared Infrastructure
Architecture and Design 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Large, M (Matthew)
Sent: 12 September 2006 08:27
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Log prune on non-standard log names?

Hi All,

One of my customers recently came to me to say that they had a 100MB log
file from TSM sitting in their file system, which confused me since the
setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlognamedsmsched_1yr.log

Does anyone know if I should expect these settings to prune the
dsmsched_1yr.log or must I manually trim this file when necessary?

Clients - 5.2.4.4
Server - 5.2.7.1

Many Thanks,
Matthew

TSM Consultant
ADMIN ITI
Rabobank International
1 Queenhithe, London
EC4V 3RL

0044 207 809 3665


_

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_


To find out more about Reuters visit www.about.reuters.com

Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
Reuters Ltd.

Re: Log prune on non-standard log names?

[Large, M (Matthew)]

Hi Richard,

The filename is as it states in the first mail - dsmsched_1yr.log -
unfortunately they've deleted it as they needed to free up space. It was
definitely the schedule log, and besides, wouldn't the setting
ERRORLOGRETENTION manage the dsmerror.log file? (which is also set to 7
days)

I think we'll upgrade to 5.3.x soon so we'll just use the SCHEDLOGMAX
setting along with the SCHEDLOGRETENTION to ensure that these file sizes
to not become unreasonably sized.

Cheers,
Matthew

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: 12 September 2006 12:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log prune on non-standard log names?

On Sep 12, 2006, at 3:27 AM, Large, M (Matthew) wrote:

> One of my customers recently came to me to say that they had a 100MB 
> log file from TSM sitting in their file system, which confused me 
> since the setting clearly stated in the options file (Win2K) says
>
> SCHEDLOGRETENTION  7
> schedlogname  dsmsched_1yr.log
...

Matthew -

Get the specifics ... the file name, and latest timestamp (for context).
What they're looking at may be a dsmerror.log file, which can be large
as it accumulates endlessly over time - ignored until it gets huge.
If some other log, its timestamp will provide evidence as to what is
writing to it, in terms of scheduled or invoked events.

Richard Sims
_

This email (including any attachments to it) is confidential, legally 
privileged, subject to copyright and is sent for the personal attention of the 
intended recipient only. If you have received this email in error, please 
advise us immediately and delete it. You are notified that disclosing, copying, 
distributing or taking any action in reliance on the contents of this 
information is strictly prohibited. Although we have taken reasonable 
precautions to ensure no viruses are present in this email, we cannot accept 
responsibility for any loss or damage arising from the viruses in this email or 
attachments. We exclude any liability for the content of this email, or for the 
consequences of any actions taken on the basis of the information provided in 
this email or its attachments, unless that information is subsequently 
confirmed in writing. If this email contains an offer, that should be 
considered as an invitation to treat.
_

Re: Log prune on non-standard log names?

[goc]

hi,
what about the missing "D" (as for days) behind 7 ?

goran


- Original Message -
From: "Large, M (Matthew)" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, September 12, 2006 1:48 PM
Subject: Re: Log prune on non-standard log names?


Hi Richard,

The filename is as it states in the first mail - dsmsched_1yr.log -
unfortunately they've deleted it as they needed to free up space. It was
definitely the schedule log, and besides, wouldn't the setting
ERRORLOGRETENTION manage the dsmerror.log file? (which is also set to 7
days)

I think we'll upgrade to 5.3.x soon so we'll just use the SCHEDLOGMAX
setting along with the SCHEDLOGRETENTION to ensure that these file sizes
to not become unreasonably sized.

Cheers,
Matthew

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: 12 September 2006 12:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log prune on non-standard log names?

On Sep 12, 2006, at 3:27 AM, Large, M (Matthew) wrote:


One of my customers recently came to me to say that they had a 100MB
log file from TSM sitting in their file system, which confused me
since the setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlogname dsmsched_1yr.log

..

Matthew -

Get the specifics ... the file name, and latest timestamp (for context).
What they're looking at may be a dsmerror.log file, which can be large
as it accumulates endlessly over time - ignored until it gets huge.
If some other log, its timestamp will provide evidence as to what is
writing to it, in terms of scheduled or invoked events.

   Richard Sims
_

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention of
the intended recipient only. If you have received this email in error,
please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on the
contents of this information is strictly prohibited. Although we have taken
reasonable precautions to ensure no viruses are present in this email, we
cannot accept responsibility for any loss or damage arising from the viruses
in this email or attachments. We exclude any liability for the content of
this email, or for the consequences of any actions taken on the basis of the
information provided in this email or its attachments, unless that
information is subsequently confirmed in writing. If this email contains an
offer, that should be considered as an invitation to treat.
_

Re: Log prune on non-standard log names?

[Richard Sims]

Hello, Matthew -

I sought certainty on the customer-reported log name, as it was not
cited in the original posting: we knew what *you* thought the log
was, but not what the customer complained about.  (End users are
typically vague in problem descriptions, which can result in a lot of
wasted time by systems people trying to resolve their issues.)

The simplest explanation for such a log not being pruned is that the
scheduler process was launched prior to the time that the options
file was updated to contain the SCHEDLOGRetention specification.

If upgrading to TSM 5, get at least to 5.3.2, to avoid another
pitfall (IC45287).  And watch out for conflicts between
SCHEDLOGRetention and SCHEDLOGMAX.

   Richard Sims

On Sep 12, 2006, at 7:48 AM, Large, M (Matthew) wrote:


Hi Richard,

The filename is as it states in the first mail - dsmsched_1yr.log -
unfortunately they've deleted it as they needed to free up space.
It was
definitely the schedule log, and besides, wouldn't the setting
ERRORLOGRETENTION manage the dsmerror.log file? (which is also set
to 7
days)

I think we'll upgrade to 5.3.x soon so we'll just use the SCHEDLOGMAX
setting along with the SCHEDLOGRETENTION to ensure that these file
sizes
to not become unreasonably sized.

Re: Log prune on non-standard log names?

[Large, M (Matthew)]

Hi Goran,

There is no setting for 'Days' in the SCHEDLOGRETENTION parameters -
just  and  - check the manual.

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/
com.ibm.itsmc.doc/ans3241.htm

Regards,
Matthew

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
goc
Sent: 12 September 2006 12:57
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log prune on non-standard log names?

hi,
what about the missing "D" (as for days) behind 7 ?

goran


- Original Message -
From: "Large, M (Matthew)" <[EMAIL PROTECTED]>
To: 
Sent: Tuesday, September 12, 2006 1:48 PM
Subject: Re: Log prune on non-standard log names?


Hi Richard,

The filename is as it states in the first mail - dsmsched_1yr.log -
unfortunately they've deleted it as they needed to free up space. It was
definitely the schedule log, and besides, wouldn't the setting
ERRORLOGRETENTION manage the dsmerror.log file? (which is also set to 7
days)

I think we'll upgrade to 5.3.x soon so we'll just use the SCHEDLOGMAX
setting along with the SCHEDLOGRETENTION to ensure that these file sizes
to not become unreasonably sized.

Cheers,
Matthew

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: 12 September 2006 12:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Log prune on non-standard log names?

On Sep 12, 2006, at 3:27 AM, Large, M (Matthew) wrote:

> One of my customers recently came to me to say that they had a 100MB 
> log file from TSM sitting in their file system, which confused me 
> since the setting clearly stated in the options file (Win2K) says
>
> SCHEDLOGRETENTION  7
> schedlogname dsmsched_1yr.log
..

Matthew -

Get the specifics ... the file name, and latest timestamp (for context).
What they're looking at may be a dsmerror.log file, which can be large
as it accumulates endlessly over time - ignored until it gets huge.
If some other log, its timestamp will provide evidence as to what is
writing to it, in terms of scheduled or invoked events.

Richard Sims
_

This email (including any attachments to it) is confidential, legally
privileged, subject to copyright and is sent for the personal attention
of the intended recipient only. If you have received this email in
error, please advise us immediately and delete it. You are notified that
disclosing, copying, distributing or taking any action in reliance on
the contents of this information is strictly prohibited. Although we
have taken reasonable precautions to ensure no viruses are present in
this email, we cannot accept responsibility for any loss or damage
arising from the viruses in this email or attachments. We exclude any
liability for the content of this email, or for the consequences of any
actions taken on the basis of the information provided in this email or
its attachments, unless that information is subsequently confirmed in
writing. If this email contains an offer, that should be considered as
an invitation to treat.
_

Re: SQL TDP Encryption

[Del Hoobler]

Hi Kelly,

You can encrypt any application that uses the TSM API (v5.3 or later)
using transparent encryption. This include Data Protection for SQL.
Take a look at this IBM technote (1213548) for details
on encrypting Data Protection for SQL backups:

   http://www-1.ibm.com/support/docview.wss?uid=swg21213548

Thanks,

Del



"ADSM: Dist Stor Manager"  wrote on 09/11/2006
03:24:16 PM:

> Folks,
>
> A quick perusal of the archive suggests that API Clients/TDPs are unable
> to offer encryption services.  The entries from Del (thanks) were all
> older.  Has anything changed in this regard?  Is encryption supported
> now in the TDP for SQL?
>
> If not we're thinking of going the Export the DB and use the BA client
> route.  Thoughts on that approach while I'm bothering al of you!

Re: Deleting a tape that doesn't exist

[William Boyer]

This is on your library manager instance. If you delete the volhist TYPE=REMOTE 
entries, the next time you do an AUDIT LIBRARY from
the library client they will re-sync all the volume information from the client 
and build new TYPE=REMOTE entries for only the
volumes that the client has assigned.

Or run this select command to a file and then feed it back in on your library 
manager:

select 'del volhist type=remote tod=+0 force=yes volume=' || volume_name from 
volhistory where devclass=''

Bill Boyer
"A life? Cool! Where can I download one of those?" - ??


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy 
Huebner
Sent: Monday, September 11, 2006 7:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deleting a tape that doesn't exist

We have about 800 volumes that are Remote Type.  We only need to delete the 
ones with a specific device class.  Is there a way to
accomplish this?  If we delete all of the remote types from the volhist, will 
the in use volumes generate new history if we delete
their old history?



Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Dennis, 
Melburn W IT743
Sent: Thursday, June 29, 2006 11:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deleting a tape that doesn't exist

I had a similar problem once and TSM gave me this nifty command:

delete volhist todate=today type=remote volume=volumename force=yes

Works well if somehow a tape's status has been lost between server to server 
communications, where your library manager shows the
tape as type remote (meaning that it has been given control over to another 
server), and the server that is supposed to be using it
shows either no info in the volhist or the last entry shows it as being 
stgdelete.  Hope this helps.


Mel Dennis
Systems Engineer - IT743
Siemens Power Generation
4400 Alafaya Trail
Orlando, FL 32826
MC Q1-108
Tel:  (407) 736-2360
Win:  439-2360
Fax: (407) 243-0260
Email:  [EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan 
Forray/AC/VCU
Sent: Thursday, June 29, 2006 12:42 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Deleting a tape that doesn't exist

I have this problem tape.  The library manager server says the tape is 
owned/used by a "remote" system/server.

When I check the "remote" system, it says it knows nothing about the tape.

How can I convince the library manager server that the tape is 
gone/deleted/kaput  so I can relabel the tape and reuse it ?

DELETE VOLUME ...  DISCARDDATA=YES does nothing.

Is there some kind of hidden "force=yes IreallyMeanIt=yes" option I can use ?


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited from 
using, copying or distributing the information in this
e-mail or its attachments. If you have received this e-mail in error, please 
notify the sender immediately by return e-mail and
delete all copies of this message and any attachments.
Thank you.

Changing management class

[Kauffman, Tom]

I've changed the management class several Windows drives point to, to
get the backups into a different storage pool. How do I move the current
data? Will it migrate properly by storage pool reclaim, or do I need to
do an export/import?

TIA

Tom Kauffman
NIBCO, Inc
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.

Re: Deleting a tape that doesn't exist

[Andy Huebner]

Perfect.  I am guessing that volume is an under documented option.

Andy Huebner

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
William Boyer
Sent: Tuesday, September 12, 2006 8:13 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deleting a tape that doesn't exist

This is on your library manager instance. If you delete the volhist
TYPE=REMOTE entries, the next time you do an AUDIT LIBRARY from
the library client they will re-sync all the volume information from the
client and build new TYPE=REMOTE entries for only the
volumes that the client has assigned.

Or run this select command to a file and then feed it back in on your
library manager:

select 'del volhist type=remote tod=+0 force=yes volume=' || volume_name
from volhistory where devclass=''

Bill Boyer
"A life? Cool! Where can I download one of those?" - ??


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andy Huebner
Sent: Monday, September 11, 2006 7:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deleting a tape that doesn't exist

We have about 800 volumes that are Remote Type.  We only need to delete
the ones with a specific device class.  Is there a way to
accomplish this?  If we delete all of the remote types from the volhist,
will the in use volumes generate new history if we delete
their old history?



Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Dennis, Melburn W IT743
Sent: Thursday, June 29, 2006 11:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deleting a tape that doesn't exist

I had a similar problem once and TSM gave me this nifty command:

delete volhist todate=today type=remote volume=volumename force=yes

Works well if somehow a tape's status has been lost between server to
server communications, where your library manager shows the
tape as type remote (meaning that it has been given control over to
another server), and the server that is supposed to be using it
shows either no info in the volhist or the last entry shows it as being
stgdelete.  Hope this helps.


Mel Dennis
Systems Engineer - IT743
Siemens Power Generation
4400 Alafaya Trail
Orlando, FL 32826
MC Q1-108
Tel:  (407) 736-2360
Win:  439-2360
Fax: (407) 243-0260
Email:  [EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Zoltan Forray/AC/VCU
Sent: Thursday, June 29, 2006 12:42 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Deleting a tape that doesn't exist

I have this problem tape.  The library manager server says the tape is
owned/used by a "remote" system/server.

When I check the "remote" system, it says it knows nothing about the
tape.

How can I convince the library manager server that the tape is
gone/deleted/kaput  so I can relabel the tape and reuse it ?

DELETE VOLUME ...  DISCARDDATA=YES does nothing.

Is there some kind of hidden "force=yes IreallyMeanIt=yes" option I can
use ?


This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this
e-mail or its attachments. If you have received this e-mail in error,
please notify the sender immediately by return e-mail and
delete all copies of this message and any attachments.
Thank you.


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.

Re: Log prune on non-standard log names?

[Gee, Norman]

This has happen to us every so often that the sched log does not get
prune.  Usually if I restart the Schedule process in the control panel
services panel, the log file will trim it self correctly.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David McClelland
Sent: Tuesday, September 12, 2006 2:53 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Log prune on non-standard log names?

Hi Matthew,

Is your customer's TSM client scheduled using the TSM Central Scheduler
(I guess so if it's growing to over 100MBs) for backup operations? This
kind of log pruning only happens during a TSM scheduled backup operation
Hi All,

One of my customers recently came to me to say that they had a 100MB log
file from TSM sitting in their file system, which confused me since the
setting clearly stated in the options file (Win2K) says

SCHEDLOGRETENTION  7
schedlognamedsmsched_1yr.log

ANS1009W with TSM Windows client 5.3.4.6

[Neil Schofield]

I've just encountered the problem documented here:
http://www-1.ibm.com/support/docview.wss?uid=swg21243837

While it's not a TSM problem per se, I thought it might be useful to let
people know about it as it probably affects all Windows 2003 SP1 clients
(as well as Windows XP SP1 clients).

Regards
Neil Schofield
Yorkshire Water Services Ltd.


-
For tips on how you can save water in your garden this summer visit
http://www.yorkshirewater.com/waterefficiency

YORKSHIRE WATER - WINNER OF THE UTILITY OF THE YEAR AWARD 2004 AND
2005

The information in this e-mail is confidential and may also be
legally privileged. The contents are intended for recipient only
and are subject to the legal notice available at
http://www.keldagroup.com/email.htm Yorkshire Water Services
Limited
Registered Office Western House Halifax Road Bradford BD6 2SZ
Registered in England and Wales No 2366682

setup library client manager LAN

[Kurt Beyers]

Hello,



I've got a question about the setup of a library client and manager. Both
TSM servers are of the version 5.3.2 and run on AIX.



* The library manager would run on TSM server A that has access to the
library across the SAN.

* The library client would run on TSM server B and has no access to the
library of TSM server A across the SAN, the TSM server B has it's own
library.



Is it possible to send backups on TSM server B to the library on TSM server
A. The backup would then go over the LAN.



In the admin guide I only find a discussion about 'Configuring SCSI
libraries shared among servers on a SAN'. Nothing is found about sharing a
library across the LAN. Is such a setup possible at all?



Thanks in advance for the responses.



Best regards,

Kurt

Groupwise Backup

[Sam Sheppard]

We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the Netware
client.  Client/Server connection is over a GigE VLan.  Server options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

 COMMMETHOD TCPip
 TCPSERVERADDRESS   172.18.16.6
 TCPBUFFSIZE32
 TCPWINDOWSIZE  64
 TCPPORT1500
 TXNB   2097152
 PASSWORDACCESSGENERATE
 PROCESSORUTILIZATION 100
 MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down. For reasons I
won't go into, NDMP was removed as an option when putting this
configuration together.

Stats show 60%+ Comm. Wait, so I'm assuming this is a client-side or
network issue, but I'm at a loss as to what to try next.  FTP tests from
the client show excellent throughput (200+GB/hour), so I don't believe
it's a network issue.  We're going to up the client-side TCPW to 128,
but I'm not optomistic.  Can anyone else out there give me their
experiences, performance-wise, with large Groupwise backups and any
hints at how to increase this throughput?  I'm beginning to think it
may be limitations of the Netware OS/client.  We're hoping to get near
40GB/hour to make our window.

Thanks in advance,
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668

Re: setup library client manager LAN

[Zoltan Forray/AC/VCU]

If I understand you correctly, the answer is yes and I do this daily.

I have 3-tape libraries (1-3493 2-3583) and they are shared by all 4-TSM
servers (2-AIX and 2-Linux) across our SAN.

1-AIX server is the Library Manager for the 3494-ATL and the other AIX
server is the LM for the 2-3583 libraries.

Now that we have our new 3592E05 drives installed in the 3494, they are
used exclusively by the AIX TSM server that owns the 2-LTO libraries
(since the LTO libraries are so problematic and constantly fail - we are
phasing out their usage to just offsite copies), not the AIX server that
owns/manages the 3494, via IP connection.

All traffic is across the SAN. The various servers intercommunication to
juggle the resources. For instance, server A will ask server B for a
drives and scratch tape.  Once server B finished that part, it turns
control over to server A, who then sends the data over the SAN and tracks
the tapes it uses, in it's own database. Server B volhist shows the tape
as being in "REMOTE" status, i.e. used by another server.



Kurt Beyers <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
09/12/2006 02:31 PM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] setup library client manager LAN






Hello,



I've got a question about the setup of a library client and manager. Both
TSM servers are of the version 5.3.2 and run on AIX.



* The library manager would run on TSM server A that has access to the
library across the SAN.

* The library client would run on TSM server B and has no access to the
library of TSM server A across the SAN, the TSM server B has it's own
library.



Is it possible to send backups on TSM server B to the library on TSM
server
A. The backup would then go over the LAN.



In the admin guide I only find a discussion about 'Configuring SCSI
libraries shared among servers on a SAN'. Nothing is found about sharing a
library across the LAN. Is such a setup possible at all?



Thanks in advance for the responses.



Best regards,

Kurt

Re: setup library client manager LAN

[Kurt Beyers]

Zoltan,

In my setup the TSM server B does not have access to the library of TSM
server A through the SAN.

But I would like to sent the TSM database backup from server B to the
library owned and used by TSM server A.

By server-to-server communication between the 2 TSM servers and a library
manager on TSM server A and a library client on TSM server B.

Regards,
Kurt

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Zoltan Forray/AC/VCU
Sent: dinsdag 12 september 2006 21:44
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] setup library client manager LAN

If I understand you correctly, the answer is yes and I do this daily.

I have 3-tape libraries (1-3493 2-3583) and they are shared by all 4-TSM
servers (2-AIX and 2-Linux) across our SAN.

1-AIX server is the Library Manager for the 3494-ATL and the other AIX
server is the LM for the 2-3583 libraries.

Now that we have our new 3592E05 drives installed in the 3494, they are
used exclusively by the AIX TSM server that owns the 2-LTO libraries
(since the LTO libraries are so problematic and constantly fail - we are
phasing out their usage to just offsite copies), not the AIX server that
owns/manages the 3494, via IP connection.

All traffic is across the SAN. The various servers intercommunication to
juggle the resources. For instance, server A will ask server B for a
drives and scratch tape.  Once server B finished that part, it turns
control over to server A, who then sends the data over the SAN and tracks
the tapes it uses, in it's own database. Server B volhist shows the tape
as being in "REMOTE" status, i.e. used by another server.



Kurt Beyers <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
09/12/2006 02:31 PM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
[ADSM-L] setup library client manager LAN






Hello,



I've got a question about the setup of a library client and manager. Both
TSM servers are of the version 5.3.2 and run on AIX.



* The library manager would run on TSM server A that has access to the
library across the SAN.

* The library client would run on TSM server B and has no access to the
library of TSM server A across the SAN, the TSM server B has it's own
library.



Is it possible to send backups on TSM server B to the library on TSM
server
A. The backup would then go over the LAN.



In the admin guide I only find a discussion about 'Configuring SCSI
libraries shared among servers on a SAN'. Nothing is found about sharing a
library across the LAN. Is such a setup possible at all?



Thanks in advance for the responses.



Best regards,

Kurt

Re: Groupwise Backup

[Troy Frank]

Couple suggestions...

Server side - groupwise tends to work better with a smaller TXNGROUPMAX
(ours is 1024).  Since groupwise is a lot of small files, and they can
change rapidly, big TXNGROUPMAX settings can equal a lot of aggregate
rebuilding before going to the server.

Client Side - Set RESOURCEUTILIZATION to 4 or so.  Netware seems to
have issues with going higher than 5 or 6, but 4 seems to work well.
You'll get more filesystem reader/data sender threads.  I've included
some of our client-side dsm.opt settings below...

ResourceUtilization  4
TCPBUFFSIZE   127
TCPWINDOWSIZE 64
TXNBYTELIMIT  25600
LARGECOMmbuffers   Yes

I've read some things that suggest LARGECOMmbuffers on netware is a
completely useless command, but it doesn't seem to hurt anything, so I
haven't taken it out.  Also keep in mind that groupwise backups will
always be slower than most other types of systems.  It's a pretty
worst-case scenario for an incremental backup since it involves a huge
number of very small files.  An ftp transfer doesn't really accurately
tell you anything, since that's only testing speed of reading a
single/few very large files, and filling the network pipe.  Disk
performance will likely be the dominating factor in this kind of
scenario, so I'd look at what kind of raid set you have, how many
spindles, on how many controllers, with what block size, what rpm your
drives are, ect.

>>> [EMAIL PROTECTED] 9/12/2006 1:45 PM >>>
We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the
Netware
client.  Client/Server connection is over a GigE VLan.  Server
options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

COMMMETHOD TCPip
TCPSERVERADDRESS   172.18.16.6
TCPBUFFSIZE32
TCPWINDOWSIZE  64
TCPPORT1500
TXNB   2097152
PASSWORDACCESSGENERATE
PROCESSORUTILIZATION 100
MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after
upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down. For reasons
I
won't go into, NDMP was removed as an option when putting this
configuration together.

Stats show 60%+ Comm. Wait, so I'm assuming this is a client-side or
network issue, but I'm at a loss as to what to try next.  FTP tests
from
the client show excellent throughput (200+GB/hour), so I don't believe
it's a network issue.  We're going to up the client-side TCPW to 128,
but I'm not optomistic.  Can anyone else out there give me their
experiences, performance-wise, with large Groupwise backups and any
hints at how to increase this throughput?  I'm beginning to think it
may be limitations of the Netware OS/client.  We're hoping to get near
40GB/hour to make our window.

Thanks in advance,
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

Re: Groupwise Backup

[Sam Sheppard]

 Top of message 
>>--> 09-12-06  13:43  S.SHEPPARD (SHS)Re: Groupwise Backup

I'll try scaling back the TXNG, but the data is static (snapshot copy),
so nothing is changing. My understanding of RESOURCEUTILIZATION is that
you need multiple volumes (filespaces) to use multiple producer threads
and since we're only backing up the one Groupwise volume I don't think
RESOURCEUTILIZATION will buy us anything.  I'll also try upping the
TCPBUFFSIZE.  I was taking the recommendation from the Performance
Tuning Guide, but I have plenty of memory to play with.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message 
>>--> 09-12-06  13:38  ..NETMAIL () Re: [ADSM-L] Groupwise Ba
Date: Tue, 12 Sep 2006 15:32:11 -0500
From: "Troy Frank" <[EMAIL PROTECTED]>
Subject: Re: [ADSM-L] Groupwise Backup
To: ADSM-L@VM.MARIST.EDU
_Top_of_Message_

Couple suggestions...

Server side - groupwise tends to work better with a smaller TXNGROUPMAX
(ours is 1024).  Since groupwise is a lot of small files, and they can
change rapidly, big TXNGROUPMAX settings can equal a lot of aggregate
rebuilding before going to the server.

Client Side - Set RESOURCEUTILIZATION to 4 or so.  Netware seems to
have issues with going higher than 5 or 6, but 4 seems to work well.
You'll get more filesystem reader/data sender threads.  I've included
some of our client-side dsm.opt settings below...

ResourceUtilization  4
TCPBUFFSIZE   127
TCPWINDOWSIZE 64
TXNBYTELIMIT  25600
LARGECOMmbuffers   Yes

I've read some things that suggest LARGECOMmbuffers on netware is a
completely useless command, but it doesn't seem to hurt anything, so I
haven't taken it out.  Also keep in mind that groupwise backups will
always be slower than most other types of systems.  It's a pretty
worst-case scenario for an incremental backup since it involves a huge
number of very small files.  An ftp transfer doesn't really accurately
tell you anything, since that's only testing speed of reading a
single/few very large files, and filling the network pipe.  Disk
performance will likely be the dominating factor in this kind of
scenario, so I'd look at what kind of raid set you have, how many
spindles, on how many controllers, with what block size, what rpm your
drives are, ect.

>>> [EMAIL PROTECTED] 9/12/2006 1:45 PM >>>
We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the
Netware
client.  Client/Server connection is over a GigE VLan.  Server
options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

COMMMETHOD TCPip
TCPSERVERADDRESS   172.18.16.6
TCPBUFFSIZE32
TCPWINDOWSIZE  64
TCPPORT1500
TXNB   2097152
PASSWORDACCESSGENERATE
PROCESSORUTILIZATION 100
MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after
upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down. For reasons
I
won't go into, NDMP was removed as an option when putting this
configuration together.

Stats show 60%+ Comm. Wait, so I'm assuming this is a client-side or
network issue, but I'm at a loss as to what to try next.  FTP tests
from
the client show excellent throughput (200+GB/hour), so I don't believe
it's a network issue.  We're going to up the client-side TCPW to 128,
but I'm not optomistic.  Can anyone else out there give me their
experiences, performance-wise, with large Groupwise backups and any
hints at how to increase this throughput?  I'm beginning to think it
may be limitations of the Netware OS/client.  We're hoping to get near
40GB/hour to make our window.

Thanks in advance,
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may 

Weekly, Monthly, Yearly Selectives

[Scott, Brian]

Fellow TSM'rs,

I have been tasked to provide a backup schedule to provide weekly, monthly, and 
yearly full backups for a 5 year duration. The weekly would be retained for a 
month, monthly for a year, and yearly for 5 years. I've created separate 
policies, nodenames, etc. to keep the policy retentions separate. The problem I 
have is the actual TSM client schedule on the server.

How do I keep the weekly selective backup from running at the end of the month 
when the monthly selective is supposed to kickoff? Same thing for the monthly 
at the end of the year when the yearly selective will kickoff?

I'm running TSM server 5.3.3.0 and BA 5.3.4 and I see the Enhanced Schedule 
capability to provide DAYOFWEEK and WEEKOFMONTH to which I can set Saturday as 
DAYOFWEEK and First,Second,Third as WEEKOFMONTH but some months have 4 weeks 
while others have 5. Also, I can't set the weekly to be every Saturday BUT the 
last Saturday of the month and the montly to be every last Saturday BUT the 
last Saturday of the year.

Any suggestions?

Regards,
Brian

Brian Scott
EDS
Global Client Engineering-GM
MS 3234
4594 W Nancy Dr.
Kankakee, IL 60901
 
( Phone:+1-815-939-2684)
+ mailto:[EMAIL PROTECTED]

Memory Allocation Backup Failure

[Kimberly N Williams]

All,

I having an issue backing up a Windows 2000 server using TSM.  We are
trying to backup about 9 TB of FS data which has a very large file
structure.  We are getting a memory allocation request denied error.  The
operating system is reaching the 2 GB memory threshold per thread
limitation and TSM is killing the backup.  Bellow I have provided the error
we are seeing on the client.  Please let me know if you have any thoughts
or ideas to fix this issue.

09/11/2006 18:26:01 ANS1030E The operating system refused a TSM request for
memory allocation.
09/11/2006 18:26:01 ANS1512E Scheduled event 'E_CLUSTER1' failed.  Return
code = 12.

Regards,

Kimberly N. Williams
Backup/Recovery Admin.
Enterprise Storage Services (ESS)
IBM Global Services
External Phone: (859) 243-1453 or T/L 545-1453
Pager : 1-877-611-4734
E-Mail Address: [EMAIL PROTECTED]


"Unless you try to do something beyond what you have already mastered, you
will never grow up"---Ronald E. Osbornh

Re: Groupwise Backup

[Marco Malgarini]

One more suggestion:

Have you tried the following TSAFS settings?

Tsafs /enableGroupwise=true this is a TSAFS load switch
And have you tried tsafs /nocachingmode this is an online switch which we
use as a pre-schedule command.

Our post offices have about 1,500,000 objects and inspection time alone
takes between 30min to 1 1/2 hours depending of other backups running on the
same box. i.e. file and print data.




Kind Regards

Marco Malgarini

Malga Consulting
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Sam
Sheppard
Sent: Wednesday, 13 September 2006 06:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Groupwise Backup

 Top of message 
>>--> 09-12-06  13:43  S.SHEPPARD (SHS)Re: Groupwise Backup

I'll try scaling back the TXNG, but the data is static (snapshot copy),
so nothing is changing. My understanding of RESOURCEUTILIZATION is that
you need multiple volumes (filespaces) to use multiple producer threads
and since we're only backing up the one Groupwise volume I don't think
RESOURCEUTILIZATION will buy us anything.  I'll also try upping the
TCPBUFFSIZE.  I was taking the recommendation from the Performance
Tuning Guide, but I have plenty of memory to play with.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message 
>>--> 09-12-06  13:38  ..NETMAIL () Re: [ADSM-L] Groupwise Ba
Date: Tue, 12 Sep 2006 15:32:11 -0500
From: "Troy Frank" <[EMAIL PROTECTED]>
Subject: Re: [ADSM-L] Groupwise Backup
To: ADSM-L@VM.MARIST.EDU
_Top_of_Message_


Couple suggestions...

Server side - groupwise tends to work better with a smaller TXNGROUPMAX
(ours is 1024).  Since groupwise is a lot of small files, and they can
change rapidly, big TXNGROUPMAX settings can equal a lot of aggregate
rebuilding before going to the server.

Client Side - Set RESOURCEUTILIZATION to 4 or so.  Netware seems to
have issues with going higher than 5 or 6, but 4 seems to work well.
You'll get more filesystem reader/data sender threads.  I've included
some of our client-side dsm.opt settings below...

ResourceUtilization  4
TCPBUFFSIZE   127
TCPWINDOWSIZE 64
TXNBYTELIMIT  25600
LARGECOMmbuffers   Yes

I've read some things that suggest LARGECOMmbuffers on netware is a
completely useless command, but it doesn't seem to hurt anything, so I
haven't taken it out.  Also keep in mind that groupwise backups will
always be slower than most other types of systems.  It's a pretty
worst-case scenario for an incremental backup since it involves a huge
number of very small files.  An ftp transfer doesn't really accurately
tell you anything, since that's only testing speed of reading a
single/few very large files, and filling the network pipe.  Disk
performance will likely be the dominating factor in this kind of
scenario, so I'd look at what kind of raid set you have, how many
spindles, on how many controllers, with what block size, what rpm your
drives are, ect.

>>> [EMAIL PROTECTED] 9/12/2006 1:45 PM >>>
We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the
Netware
client.  Client/Server connection is over a GigE VLan.  Server
options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

COMMMETHOD TCPip
TCPSERVERADDRESS   172.18.16.6
TCPBUFFSIZE32
TCPWINDOWSIZE  64
TCPPORT1500
TXNB   2097152
PASSWORDACCESSGENERATE
PROCESSORUTILIZATION 100
MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after
upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down. For reasons
I
won't go into, NDMP was removed as an option when putting this
configuration together.

Stats show 60%+ Comm. Wait, so I'm assuming this is a client-side or
network issue, but I'm at a loss as to what to try next.  FTP tests
from
the client show excellent throughput (200+GB/hour), so I don't believe
it's a network issue.  We're going to up the client-side TCPW to 128,
but I'm not optomistic.  Can anyone else out there give me their
experiences, performance-wise, with large Gro

Re: Groupwise Backup

[Troy Frank]

ResourceUtilization will use multiple producer threads whether you've
got multiple volumes or not.  In your case,  you may be right about
snapshots negating the need for lower TXNG though.  Are all the
groupwise po's on this one netapp device, and are the servers connected
to the storage via FC/iSCSI/or what?  Also, how many drives is the data
spread across, and in what kind of raidset (with what blocksize)?


>>> [EMAIL PROTECTED] 9/12/2006 3:57 PM >>>
 Top of message

>>--> 09-12-06  13:43  S.SHEPPARD (SHS)Re: Groupwise Backup

I'll try scaling back the TXNG, but the data is static (snapshot
copy),
so nothing is changing. My understanding of RESOURCEUTILIZATION is
that
you need multiple volumes (filespaces) to use multiple producer
threads
and since we're only backing up the one Groupwise volume I don't think
RESOURCEUTILIZATION will buy us anything.  I'll also try upping the
TCPBUFFSIZE.  I was taking the recommendation from the Performance
Tuning Guide, but I have plenty of memory to play with.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message

>>--> 09-12-06  13:38  ..NETMAIL () Re: [ADSM-L] Groupwise Ba
Date: Tue, 12 Sep 2006 15:32:11 -0500
From: "Troy Frank" <[EMAIL PROTECTED]>
Subject: Re: [ADSM-L] Groupwise Backup
To: ADSM-L@VM.MARIST.EDU
_Top_of_Message_

Couple suggestions...

Server side - groupwise tends to work better with a smaller
TXNGROUPMAX
(ours is 1024).  Since groupwise is a lot of small files, and they can
change rapidly, big TXNGROUPMAX settings can equal a lot of aggregate
rebuilding before going to the server.

Client Side - Set RESOURCEUTILIZATION to 4 or so.  Netware seems to
have issues with going higher than 5 or 6, but 4 seems to work well.
You'll get more filesystem reader/data sender threads.  I've included
some of our client-side dsm.opt settings below...

ResourceUtilization  4
TCPBUFFSIZE   127
TCPWINDOWSIZE 64
TXNBYTELIMIT  25600
LARGECOMmbuffers   Yes

I've read some things that suggest LARGECOMmbuffers on netware is a
completely useless command, but it doesn't seem to hurt anything, so I
haven't taken it out.  Also keep in mind that groupwise backups will
always be slower than most other types of systems.  It's a pretty
worst-case scenario for an incremental backup since it involves a huge
number of very small files.  An ftp transfer doesn't really accurately
tell you anything, since that's only testing speed of reading a
single/few very large files, and filling the network pipe.  Disk
performance will likely be the dominating factor in this kind of
scenario, so I'd look at what kind of raid set you have, how many
spindles, on how many controllers, with what block size, what rpm your
drives are, ect.

>>> [EMAIL PROTECTED] 9/12/2006 1:45 PM >>>
We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the
Netware
client.  Client/Server connection is over a GigE VLan.  Server
options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

COMMMETHOD TCPip
TCPSERVERADDRESS   172.18.16.6
TCPBUFFSIZE32
TCPWINDOWSIZE  64
TCPPORT1500
TXNB   2097152
PASSWORDACCESSGENERATE
PROCESSORUTILIZATION 100
MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after
upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down. For reasons
I
won't go into, NDMP was removed as an option when putting this
configuration together.

Stats show 60%+ Comm. Wait, so I'm assuming this is a client-side or
network issue, but I'm at a loss as to what to try next.  FTP tests
from
the client show excellent throughput (200+GB/hour), so I don't believe
it's a network issue.  We're going to up the client-side TCPW to 128,
but I'm not optomistic.  Can anyone else out there give me their
experiences, performance-wise, with large Groupwise backups and any
hints at how to increase this throughput?  I'm beginning to think it
may be limitations of the Netware OS/client.  We're hoping to get near
40GB/hour to make our window.

Thanks in advance,
Sam Sheppard
Sa

Re: Weekly, Monthly, Yearly Selectives

[Troy Frank]

This sounds like a classic request from management that doesn't
understand TSM works differently from typical backup software, and
they're trying to shoehorn it into behaving as they're used to.  If you
make your normal retention policy 30 versions or more, you can at least
get rid of the weekly/monthly full backups.  In our case, we do 60
versions held for 60 days.  So if/when we do longer term archives, it
would have to be at most bi-monthly.

Also, as others have mentioned before, there's no need to make these
monthly/yearly backups a selective(full).  You can just make a 12
version & 5 version management policy for the monthly & yearly backups,
respectively.  All the backups can be incremental this way, and you save
bookoo tapes & DB entries (not to mention faster backups).


>>> [EMAIL PROTECTED] 9/12/2006 4:12 PM >>>
Fellow TSM'rs,

I have been tasked to provide a backup schedule to provide weekly,
monthly, and yearly full backups for a 5 year duration. The weekly would
be retained for a month, monthly for a year, and yearly for 5 years.
I've created separate policies, nodenames, etc. to keep the policy
retentions separate. The problem I have is the actual TSM client
schedule on the server.

How do I keep the weekly selective backup from running at the end of
the month when the monthly selective is supposed to kickoff? Same thing
for the monthly at the end of the year when the yearly selective will
kickoff?

I'm running TSM server 5.3.3.0 and BA 5.3.4 and I see the Enhanced
Schedule capability to provide DAYOFWEEK and WEEKOFMONTH to which I can
set Saturday as DAYOFWEEK and First,Second,Third as WEEKOFMONTH but some
months have 4 weeks while others have 5. Also, I can't set the weekly to
be every Saturday BUT the last Saturday of the month and the montly to
be every last Saturday BUT the last Saturday of the year.

Any suggestions?

Regards,
Brian

Brian Scott
EDS
Global Client Engineering-GM
MS 3234
4594 W Nancy Dr.
Kankakee, IL 60901

( Phone:+1-815-939-2684)
+ mailto:[EMAIL PROTECTED]

Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

Re: Groupwise Backup

[Troy Frank]

TSM does not support the use of the /enableGroupwise switch, as it is
the replacement for tsagw, which tsm also didn't support.  It doesn't
stop backups from running, but it caused more errors in my experience.
The /nocachingmode switch is important to do though...had forgotten
about that one.  You can also set it permanently by editing the
sys:/etc/sms/tsa.cfg file, and changing the "Enable Caching" option from
"yes", to "no".


>>> Marco Malgarini <[EMAIL PROTECTED]> 9/12/2006 4:49 PM >>>
One more suggestion:

Have you tried the following TSAFS settings?

Tsafs /enableGroupwise=true this is a TSAFS load switch
And have you tried tsafs /nocachingmode this is an online switch which
we
use as a pre-schedule command.

Our post offices have about 1,500,000 objects and inspection time
alone
takes between 30min to 1 1/2 hours depending of other backups running
on the
same box. i.e. file and print data.




Kind Regards

Marco Malgarini

Malga Consulting
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of Sam
Sheppard
Sent: Wednesday, 13 September 2006 06:58 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Groupwise Backup

 Top of message

>>--> 09-12-06  13:43  S.SHEPPARD (SHS)Re: Groupwise Backup

I'll try scaling back the TXNG, but the data is static (snapshot
copy),
so nothing is changing. My understanding of RESOURCEUTILIZATION is
that
you need multiple volumes (filespaces) to use multiple producer
threads
and since we're only backing up the one Groupwise volume I don't think
RESOURCEUTILIZATION will buy us anything.  I'll also try upping the
TCPBUFFSIZE.  I was taking the recommendation from the Performance
Tuning Guide, but I have plenty of memory to play with.
Thanks
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message

>>--> 09-12-06  13:38  ..NETMAIL () Re: [ADSM-L] Groupwise Ba
Date: Tue, 12 Sep 2006 15:32:11 -0500
From: "Troy Frank" <[EMAIL PROTECTED]>
Subject: Re: [ADSM-L] Groupwise Backup
To: ADSM-L@VM.MARIST.EDU
_Top_of_Message_


Couple suggestions...

Server side - groupwise tends to work better with a smaller
TXNGROUPMAX
(ours is 1024).  Since groupwise is a lot of small files, and they can
change rapidly, big TXNGROUPMAX settings can equal a lot of aggregate
rebuilding before going to the server.

Client Side - Set RESOURCEUTILIZATION to 4 or so.  Netware seems to
have issues with going higher than 5 or 6, but 4 seems to work well.
You'll get more filesystem reader/data sender threads.  I've included
some of our client-side dsm.opt settings below...

ResourceUtilization  4
TCPBUFFSIZE   127
TCPWINDOWSIZE 64
TXNBYTELIMIT  25600
LARGECOMmbuffers   Yes

I've read some things that suggest LARGECOMmbuffers on netware is a
completely useless command, but it doesn't seem to hurt anything, so I
haven't taken it out.  Also keep in mind that groupwise backups will
always be slower than most other types of systems.  It's a pretty
worst-case scenario for an incremental backup since it involves a huge
number of very small files.  An ftp transfer doesn't really accurately
tell you anything, since that's only testing speed of reading a
single/few very large files, and filling the network pipe.  Disk
performance will likely be the dominating factor in this kind of
scenario, so I'd look at what kind of raid set you have, how many
spindles, on how many controllers, with what block size, what rpm your
drives are, ect.

>>> [EMAIL PROTECTED] 9/12/2006 1:45 PM >>>
We have installed a new TSM server intended to backup about a dozen
Novell Groupwise post offices, totaling around 600GB. These are being
directed to IBM Ultrium-TD3 LTO tapes in a FC-attached Spectralogic
library.  The TSM server is Version 5.3.3.3 running under Solaris 10
(Sunfire V240, 2 1.5G CPUs, 8GB memory).  The clients machines are
dual-processor 3GHz, 3GB memory running the 5.3.4 version of the
Netware
client.  Client/Server connection is over a GigE VLan.  Server
options:

COMMmethod TCPIP
TCPWindowsize 128
BUFPOOLSIZE 128000
EXPINTERVAL 0
SELFTUNEBUFPOOLSIZE YES
TXNGROUPMAX 2048

Client Options:

COMMMETHOD TCPip
TCPSERVERADDRESS   172.18.16.6
TCPBUFFSIZE32
TCPWINDOWSIZE  64
TCPPORT1500
TXNB   2097152
PASSWORDACCESSGENERATE
PROCESSORUTILIZATION 100
MEMORYEFFICIENTBACKUP NO

Initial test backup of a small (9GB) PO showed a throughput of around
20GB/hour.  Subsequent tests have improved to 25-29GB/hour after
upping
the TXNG and PROCESSORUTILIZATION parms, but this still seems awfully
slow for what, to us, seems like a pretty beefy system.

The data resides on a NetApp FAS device and we actually backup a
snapshot of the PO to avoid having to take Groupwise down.

Re: Memory Allocation Backup Failure

[Richard Sims]

Kimberly -

That's a question we've addressed before.  As you realize, your site
has outgrown the antiquated Windows 2000 operating system, and needs
to move on.

You can see past approaches to the ANS1030E situation as collected
in   http://people.bu.edu/rbs/ADSM.QuickFacts

   Richard Sims

dsmserv.opt

[Gill, Geoffrey L.]

I have a 5.2 server and a 5.3 server. When comparing q opt output it does
not show the same options when comparing the outputs from each. This
particular option is listed in the dsmserv.opt exactly as the 5.2 server.
Any ideas as to why?



UseLargeBuffer   Yes



Thanks,



Geoff Gill

TSM Administrator

PeopleSoft Sr. Systems Administrator

SAIC M/S-G1b

(858)826-4062

Email:   [EMAIL PROTECTED]