Re: stgpool migrations between TSM instances

[Stapleton, Mark]

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
TSTLTDTD
> Try exporting and importing

Yes. In fact that's the only way you'll be able to do that. Be prepared
to tie up at least one tape drive for each pool for long periods of
time. I would suggest that you use the "filedata=allactive" flag to
minimize the amount of data sought and moved.

--
Mark Stapleton
CDW Berbee
System engineer

Re: Issue with archive -archmc=...... command line

[Richard Sims]

Diego -

Two factors:
1. You need to use -SUbdir=Yes in order to pursue subdirectories.
2. You are specifying management classes which have "backup" in their
names:
   be certain that they contain appropriate Archive type Copy Group
definitions.

Use 'dsmc Query Archive' to verify what has been successfully archived.

  Richard Sims

Issue with archive -archmc=...... command line

[Diego Ojeda]

Hi

Can any help me with these issue?

That is the configuration in these moment:

One PolicyDomain with name AIX. Inside this, three ManagmentClass with name:
backup_daily(default); backup_weekly; backup_monthly.
I have one host (AIX) with filesystem mounts
(/;/usr;/data;/home;/files;etc...). I need take archive backup with command
line and bind with backup_monthly managment class. Im runing these command:
archive -archmc=backup_monthly "/*", But the only backup files that are
directory "/". Sowhat is the command line to take archive for all
filesystem in AIX host??? Im probe with command archive
-archmc=backup_monthly "/* /usr /data /home, etc..." but give me errors.
With the option '/* /usr /data, etc...'...error... Im create one file that
contain filesystem to archive (fs.txt) and put these command option...
archive -filelist=fs.txt -archmc=backup_montly...and nothing

Thanks to all, greetings!

Re: What to use for TSM monitoring/alerting

[Ben Bullock]

No, it is by a smaller company. Go to www.tsmmanager.com and you can
download a trial version. It is quite inexpensive and works well. 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Juan Perla
Sent: Tuesday, January 29, 2008 3:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting

Is tsm manager from bacada?

thx, JP


On Tue, 29 Jan 2008, Ben Bullock wrote:

> Date: Tue, 29 Jan 2008 15:19:55 -0700
> From: Ben Bullock <[EMAIL PROTECTED]>
> Reply-To: "ADSM: Dist Stor Manager" 
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting
>
> We use TSMMANAGER.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
> Of Gill, Geoffrey L.
> Sent: Tuesday, January 29, 2008 3:18 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting
>
> > My question is: What tools are you folks using to monitor TSM and
> alert
> >you to any problems.
>
> >Nicholas
>
> We use Servergraph
>
>
> Geoff Gill
> TSM Administrator
> PeopleSoft Sr. Systems Administrator
> SAIC M/S-G1b
> (858)826-4062
> Email: [EMAIL PROTECTED]
>
>
> The Blue Cross of Idaho Email Firewall Server made the following
annotations:
> --
> 
> *Confidentiality Notice:
>
> This E-Mail is intended only for the use of the individual or entity 
> to which it is addressed and may contain information that is 
> privileged, confidential and exempt from disclosure under applicable 
> law. If you have received this communication in error, please do not 
> distribute, and delete the original message.
>
> Thank you for your compliance.
>
> You may contact us at:
> Blue Cross of Idaho
> 3000 E. Pine Ave.
> Meridian, Idaho 83642
> 1.208.345.4550
>
> ==
> 
>


The Blue Cross of Idaho Email Firewall Server made the following annotations:
--
*Confidentiality Notice: 

This E-Mail is intended only for the use of the individual
or entity to which it is addressed and may contain
information that is privileged, confidential and exempt
from disclosure under applicable law. If you have received
this communication in error, please do not distribute, and
delete the original message. 

Thank you for your compliance.

You may contact us at:
Blue Cross of Idaho 
3000 E. Pine Ave.
Meridian, Idaho 83642
1.208.345.4550

==

Re: What to use for TSM monitoring/alerting

[Juan Perla]

Is tsm manager from bacada?

thx, JP


On Tue, 29 Jan 2008, Ben Bullock wrote:

> Date: Tue, 29 Jan 2008 15:19:55 -0700
> From: Ben Bullock <[EMAIL PROTECTED]>
> Reply-To: "ADSM: Dist Stor Manager" 
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting
>
> We use TSMMANAGER.
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Gill, Geoffrey L.
> Sent: Tuesday, January 29, 2008 3:18 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting
>
> > My question is: What tools are you folks using to monitor TSM and
> alert
> >you to any problems.
>
> >Nicholas
>
> We use Servergraph
>
>
> Geoff Gill
> TSM Administrator
> PeopleSoft Sr. Systems Administrator
> SAIC M/S-G1b
> (858)826-4062
> Email: [EMAIL PROTECTED]
>
>
> The Blue Cross of Idaho Email Firewall Server made the following annotations:
> --
> *Confidentiality Notice:
>
> This E-Mail is intended only for the use of the individual
> or entity to which it is addressed and may contain
> information that is privileged, confidential and exempt
> from disclosure under applicable law. If you have received
> this communication in error, please do not distribute, and
> delete the original message.
>
> Thank you for your compliance.
>
> You may contact us at:
> Blue Cross of Idaho
> 3000 E. Pine Ave.
> Meridian, Idaho 83642
> 1.208.345.4550
>
> ==
>

unsubscribe

[Stephen Meier]

**

This email may contain confidential and privileged material

for the sole use of the intended recipient.  Any review or

distribution by others is strictly prohibited.



If you are not the intended recipient, please contact the

sender and delete all copies of it from your system.



Please note that the sender accepts no responsibility for

viruses and it is your responsibility to scan attachments

(if any). No contracts may be concluded on behalf of the

sender by means of email communications unless expressly

stated to the contrary.



NOTICE: This E-mail (including attachments) is covered by

the Electronic Communications Privacy Act,

18 U.S.C. 2510-2521, is confidential and may be legally

privileged. If you are not the intended recipient, you are

hereby notified that any retention, dissemination, distribution

or copying of this communication is strictly prohibited. Please

reply to the sender that you have received the message in

error, then delete it.

Re: What to use for TSM monitoring/alerting

[Ben Bullock]

We use TSMMANAGER.  

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: Tuesday, January 29, 2008 3:18 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting

> My question is: What tools are you folks using to monitor TSM and
alert
>you to any problems.

>Nicholas

We use Servergraph

 
Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED] 


The Blue Cross of Idaho Email Firewall Server made the following annotations:
--
*Confidentiality Notice: 

This E-Mail is intended only for the use of the individual
or entity to which it is addressed and may contain
information that is privileged, confidential and exempt
from disclosure under applicable law. If you have received
this communication in error, please do not distribute, and
delete the original message. 

Thank you for your compliance.

You may contact us at:
Blue Cross of Idaho 
3000 E. Pine Ave.
Meridian, Idaho 83642
1.208.345.4550

==

Re: What to use for TSM monitoring/alerting

[Gill, Geoffrey L.]

> My question is: What tools are you folks using to monitor TSM and
alert
>you to any problems.

>Nicholas

We use Servergraph

 
Geoff Gill 
TSM Administrator 
PeopleSoft Sr. Systems Administrator 
SAIC M/S-G1b 
(858)826-4062 
Email: [EMAIL PROTECTED] 

unsubscribe

[Kleynerman, Arthur]

-
The information contained in this e-mail message, and any
attachment thereto, is confidential and may not be disclosed
without our express permission. If you are not the intended
recipient or an employee or agent responsible for delivering this
message to the intended recipient, you are hereby notified that you
have received this message in error and that any review,
dissemination, distribution or copying of this message, or any
attachment thereto, in whole or in part, is strictly prohibited. If
you have received this message in error, please immediately notify
us by telephone, fax or e-mail and delete the message and all of
its attachments. Thank you. Every effort is made to keep our
network free from viruses. You should, however, review this e-mail
message, as well as any attachment thereto, for viruses. We take no
responsibility and have no liability for any computer virus which
may be transferred via this e-mail message.

Re: What to use for TSM monitoring/alerting

[Howard Coles]

You should also look into Servergraph, which can send email alerts when
things like this go wrong.  I have benefited from those messages on more
than one occasion.  A problem we had recently with a few drives was that
they would just lock up.  The Library would think they were busy, but no
data would go in or out, and eventually TSM would time out on the drive.



See Ya'
Howard
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Stephen Mackereth
Sent: Tuesday, January 29, 2008 3:11 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] What to use for TSM monitoring/alerting

Hi Nicholas,

The 3584 can send snmp traps, this is configured via the specialist gui.
I wrote a few scripts to query TSM, ie number of drives offline, number
of paths offline

Regards,

Stephen.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Rodolfich
Sent: Wednesday, 30 January 2008 7:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] What to use for TSM monitoring/alerting

Hello All,

Thanks for your help!!

We are running TSM 5.3.4 with a IBM 3584 library. Our library has not
exactly been the Pinnacle of MTBF. All the drives have been replaced,
some more than once and the medium changer has been replaced twice. All
of this since April 2007.

The medium changer died this past Friday night and no one caught it
until the next day. Our DBA has made a big stink about monitoring TSM
and alerting when something is wrong. The DBA and another admin think
they can write some code to do this "alerting" on the 8493E message in
the activity log.

My question is: What tools are you folks using to monitor TSM and alert
you to any problems.

Nicholas


IMPORTANT NOTICE:  This message and any included attachments are from
East Jefferson General Hospital, and is intended only for the
addressee(s), and may include Protected Health (PHI) or other
confidential information.  If you are the intended recipient, you are
obligated to maintain it in a secure and confidential manner and
re-disclosure without additional consent or as
permitted by law is prohibited.   If you are not the intended recipient,
use
of this information is strictly prohibited and may be unlawful.  Please
promptly reply to the sender by email and delete this message from your
computer. East Jefferson General Hospital greatly appreciates your
cooperation.

Re: What to use for TSM monitoring/alerting

[Stephen Mackereth]

Hi Nicholas,

The 3584 can send snmp traps, this is configured via the specialist gui.
I wrote a few scripts to query TSM, ie number of drives offline, number of
paths offline

Regards,

Stephen.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Rodolfich
Sent: Wednesday, 30 January 2008 7:31 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] What to use for TSM monitoring/alerting

Hello All,

Thanks for your help!!

We are running TSM 5.3.4 with a IBM 3584 library. Our library has not
exactly been the Pinnacle of MTBF. All the drives have been replaced,
some more than once and the medium changer has been replaced twice. All
of this since April 2007.

The medium changer died this past Friday night and no one caught it
until the next day. Our DBA has made a big stink about monitoring TSM
and alerting when something is wrong. The DBA and another admin think
they can write some code to do this "alerting" on the 8493E message in
the activity log.

My question is: What tools are you folks using to monitor TSM and alert
you to any problems.

Nicholas


IMPORTANT NOTICE:  This message and any included attachments are from East
Jefferson General Hospital, and is intended only for the addressee(s), and
may include Protected Health (PHI) or other confidential information.  If
you are the intended recipient, you are obligated to maintain it in a secure
and confidential manner and re-disclosure without additional consent or as
permitted by law is prohibited.   If you are not the intended recipient, use
of this information is strictly prohibited and may be unlawful.  Please
promptly reply to the sender by email and delete this message from your
computer. East Jefferson General Hospital greatly appreciates your
cooperation.

Re: DISASTER: How to do a LOT of restores?

[Richard Sims]

On Jan 29, 2008, at 3:09 PM, Curtis Preston wrote:


BTW, is there a TSM internals redbook that I could read?


SHARE and Oxford TSM Symposium presentations are the primary sources
of developer expositions.

   Richard Sims

What to use for TSM monitoring/alerting

[Nicholas Rodolfich]

Hello All,

Thanks for your help!!

We are running TSM 5.3.4 with a IBM 3584 library. Our library has not
exactly been the Pinnacle of MTBF. All the drives have been replaced,
some more than once and the medium changer has been replaced twice. All
of this since April 2007.

The medium changer died this past Friday night and no one caught it
until the next day. Our DBA has made a big stink about monitoring TSM
and alerting when something is wrong. The DBA and another admin think
they can write some code to do this "alerting" on the 8493E message in
the activity log.

My question is: What tools are you folks using to monitor TSM and alert
you to any problems.

Nicholas


IMPORTANT NOTICE:  This message and any included attachments are from East 
Jefferson General Hospital, and is intended only for the addressee(s), and may 
include Protected Health (PHI) or other confidential information.  If you are 
the intended recipient, you are obligated to maintain it in a secure and 
confidential manner and re-disclosure without additional consent or as 
permitted by law is prohibited.   If you are not the intended recipient, use of 
this information is strictly prohibited and may be unlawful.  Please promptly 
reply to the sender by email and delete this message from your computer. East 
Jefferson General Hospital greatly appreciates your cooperation.

Re: DISASTER: How to do a LOT of restores?

[Curtis Preston]

Putting my TSM knowledge together with my knowledge of how databases
work, I come up with the following understanding:

Each version of each file has an entry in the database.  That entry
stores all the info about the file (size, mtime, any CRC values, etc., a
unique identifier used in other parts of the database).

Each version of each file is stored in one or more aggregates.  Each
aggregate also has a record in the database that contains info about
that aggregate, which would include the size of the aggregate, where it
is stored, and what files are stored in that aggregate.

This is analogous to a Unix filesystem in that a file does not know what
directory it's in.  The directory knows which files are in it. The file
knows its permissions, size, and access times, and the directory knows
its permissions and access times -- and what files are in that
directory. (A lot of people don't realize that in Unix, a directory is
just a different type of file that stores the names of other files.)

How'd I do?

BTW, is there a TSM internals redbook that I could read?  Most of what I
find is administration stuff that doesn't really address this kind of
detail.

---
W. Curtis Preston
Backup Blog @ www.backupcentral.com
VP Data Protection, GlassHouse Technologies 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Paul Zarnowski
Sent: Monday, January 28, 2008 11:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] DISASTER: How to do a LOT of restores?

Curtis, I didn't read this whole thread, but I don't think this is quite
true.  I believe that all files in an aggregate relate to a single
common
database entry which indicates where the aggregate is stored (which tape
or
disk volume, and location on that volume).  When files in an aggregate
are
moved (i.e., migrated from disk to tape), then the one aggregate record
is
updated in the database to reflect that the aggregate was moved, but all
of
the individual file entries (that make up the aggregate) do not need to
be
updated.

So yes, each file it's own database entry, but that database entry
doesn't
necessarily indicate *where* the file is stored.  That information is
kept
in an aggregate record.

It should still be true that if an aggregate transmission is
interrupted,
the entire transaction is rolled back.

The above is my understanding, but I do not know it as fact.

..Paul


At 03:54 PM 1/28/2008, Curtis Preston wrote:
>So I'm back to my original understanding then, that all files are
>tracked individually in TSM.  It's just that TSM doesn't do a commit
>until an aggregate has completed.  This explains why the entire
>aggregate must be redone if it fails halfway through due to a
>busy/locked file.  If it fails, the entire transaction is rolled back,
>so there is no record of any of the previous files in the aggregate.
Am
>I still on the right page?


--
Paul ZarnowskiPh: 607-255-4757
Manager, Storage Services Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801Em: [EMAIL PROTECTED]

stgpool migrations between TSM instances

[TSTLTDTD]

Try exporting and importing

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

Re: What volumes contain node backup data

[Richard Mochnaczewski]

Use the following :

select distinct volume_name from volumeusage where node_name='SERVERNAME' 

SERVERNAME should all be in uppercase .

Rich


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Tim Brown
Sent: Tuesday, January 29, 2008 11:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] What volumes contain node backup data


 How can I tell which TSM tape volumes contain
 backup data for a particular node

 Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: [EMAIL PROTECTED] 
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255

  
Standard Life : 175 ans au coeur de nos vies
Standard Life: Part of our lives for 175 years
 
 

Re: TSM performing full backups where incremental specified

[Kinder, Kevin P]

Yes - first thing I checked. Thanks, though!


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Strand, Neil B.
Sent: Tuesday, January 29, 2008 12:32 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Kevin,
Have you verified that the MODE parameter of the copygoup is not set
to Absolute?



Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kinder, Kevin P
Sent: Tuesday, January 29, 2008 11:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Richard, and others,

Thanks for the on- and off-line responses. I have followed up the
suggestions made, but so far no success.

Richard,

I checked to make sure that nothing was strange with the filespaces. I
actually did an incremental from the command line, then followed it up
immediately with another, and sure enough almost all the files backed up
twice. DSMC Q FI shows just one occurrence of each defined filespace, so
I don't think anything is happening to them between backups. In this
case, it would have had to have happened in about one minute.

Q BACKUP on the client shows multiple instances of each file -- one
active, the rest inactive. I don't see anything on the details of each
file that indicates a change. Last access date, file size, all appear
identical. I chose several operating system files that I know have not
changed since the last server upgrade (more than a year ago) and they
still back up when using INCREMENTAL by itself.

The number of files backed up is just a few dozen short of the number
inspected - a difference which is attributable to those files that were
open (such as log files) and could not be backed up. Obviously, with
full backups running each night, my tape count in increasing
dramatically.

I have run traces, and have a call open with IBM. It has been open for
20 days. They are stumped as well, and have no idea what to do. So, I
was trying this avenue again in the hope that someone else may have seen
this.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Monday, January 28, 2008 5:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Kevin -

Heck of a problem you have there.  I don't do z/OS or Netware, so
unlikely that I'll have an answer, but some thoughts...

This is too obvious, but: The filespaces involved are not in some way
being renamed or deleted in between the mass incrementals?  That would
cause a full backup.  Seems very unlikely to me, but one thing I would
consider.  Does a 'dsmc q fi' show a singular instance of the suspect
file system?  Here I'm thinking of some oddity causing the server to
believe that the file system is different each time.  But, tape
consumption would cause this to stand out.

In the backup log, does the number of objects backed up equal the number
inspected?  If a substantive difference, I would look into the
exceptions to see what's the basis of their immunity.  Also, perform a
'dsmc q ba -detail -ina ___' on one of the files and see if all
versions look the same, or there is some different which might incite
the backup.  And, if you don't see a bunch of versions, it may be
possible that some mutation to the policies is causing obliteration of
what was backed up the last time.

As a last resort, I would run a client trace of your partial versus
unqualified incrementals and see if any functional differences stand out
in causing the mass backups.  If nothing apparent, give TSM Support a
call.

wacky stuff I can think of,  Richard Sims

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security
numbers, account numbers, or personal identification numbers. Delivery,
and or timely delivery of Internet mail is not guaranteed. Legg Mason
therefore recommends that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain
privileged or confidential information. Unless you are the intended
recipient, you may not use, copy or disclose to anyone any information
contained in this message. If you have received this message in error,
please notify the author by replying to this message and then kindly
delete the message. Thank you.

stgpool migrations between TSM instances

[coopermarsh]

Background:

Have 2 instances,

1. LTO3 stgpools (current)
2. LTO1 stgpools (older)


Issue
I need to migrate the data from the LTO1 stgpools to the LTO3 stgpools for a 
complete DR instance.

Both instances are running, but each instance does not know of the stgpools in 
the other instance, if you get me.

Is this possible?

If not I may have to set up the drives/devc/stgpools on the LTO3 instance and 
then set the NEXTPOOL= on the LTO1 stgpools.

Any help much appreciated.

+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--

Re: TSM performing full backups where incremental specified

[Strand, Neil B.]

Kevin,
Have you verified that the MODE parameter of the copygoup is not set
to Absolute?



Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kinder, Kevin P
Sent: Tuesday, January 29, 2008 11:44 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Richard, and others,

Thanks for the on- and off-line responses. I have followed up the
suggestions made, but so far no success.

Richard,

I checked to make sure that nothing was strange with the filespaces. I
actually did an incremental from the command line, then followed it up
immediately with another, and sure enough almost all the files backed up
twice. DSMC Q FI shows just one occurrence of each defined filespace, so
I don't think anything is happening to them between backups. In this
case, it would have had to have happened in about one minute.

Q BACKUP on the client shows multiple instances of each file -- one
active, the rest inactive. I don't see anything on the details of each
file that indicates a change. Last access date, file size, all appear
identical. I chose several operating system files that I know have not
changed since the last server upgrade (more than a year ago) and they
still back up when using INCREMENTAL by itself.

The number of files backed up is just a few dozen short of the number
inspected - a difference which is attributable to those files that were
open (such as log files) and could not be backed up. Obviously, with
full backups running each night, my tape count in increasing
dramatically.

I have run traces, and have a call open with IBM. It has been open for
20 days. They are stumped as well, and have no idea what to do. So, I
was trying this avenue again in the hope that someone else may have seen
this.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Monday, January 28, 2008 5:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Kevin -

Heck of a problem you have there.  I don't do z/OS or Netware, so
unlikely that I'll have an answer, but some thoughts...

This is too obvious, but: The filespaces involved are not in some way
being renamed or deleted in between the mass incrementals?  That would
cause a full backup.  Seems very unlikely to me, but one thing I would
consider.  Does a 'dsmc q fi' show a singular instance of the suspect
file system?  Here I'm thinking of some oddity causing the server to
believe that the file system is different each time.  But, tape
consumption would cause this to stand out.

In the backup log, does the number of objects backed up equal the number
inspected?  If a substantive difference, I would look into the
exceptions to see what's the basis of their immunity.  Also, perform a
'dsmc q ba -detail -ina ___' on one of the files and see if all
versions look the same, or there is some different which might incite
the backup.  And, if you don't see a bunch of versions, it may be
possible that some mutation to the policies is causing obliteration of
what was backed up the last time.

As a last resort, I would run a client trace of your partial versus
unqualified incrementals and see if any functional differences stand out
in causing the mass backups.  If nothing apparent, give TSM Support a
call.

wacky stuff I can think of,  Richard Sims

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason 
therefore recommends that you do not send any confidential or sensitive 
information to us via electronic mail, including social security numbers, 
account numbers, or personal identification numbers. Delivery, and or timely 
delivery of Internet mail is not guaranteed. Legg Mason therefore recommends 
that you do not send time sensitive 
or action-oriented messages to us via electronic mail.

This message is intended for the addressee only and may contain privileged or 
confidential information. Unless you are the intended recipient, you may not 
use, copy or disclose to anyone any information contained in this message. If 
you have received this message in error, please notify the author by replying 
to this message and then kindly delete the message. Thank you.

Re: What volumes contain node backup data

[Skylar Thompson]

Tim Brown wrote:

 How can I tell which TSM tape volumes contain
 backup data for a particular node


"QUERY NODEDATA node-name" will do the trick.

--
-- Skylar Thompson ([EMAIL PROTECTED])
-- Genome Sciences Department, System Administrator
-- Foege Building S048, (206)-685-7354
-- University of Washington School of Medicine

What volumes contain node backup data

[Tim Brown]

 How can I tell which TSM tape volumes contain
 backup data for a particular node

 Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: [EMAIL PROTECTED] 
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255

Re: TSM performing full backups where incremental specified

[Kinder, Kevin P]

Richard, and others,

Thanks for the on- and off-line responses. I have followed up the
suggestions made, but so far no success.

Richard,

I checked to make sure that nothing was strange with the filespaces. I
actually did an incremental from the command line, then followed it up
immediately with another, and sure enough almost all the files backed up
twice. DSMC Q FI shows just one occurrence of each defined filespace, so
I don't think anything is happening to them between backups. In this
case, it would have had to have happened in about one minute.

Q BACKUP on the client shows multiple instances of each file -- one
active, the rest inactive. I don't see anything on the details of each
file that indicates a change. Last access date, file size, all appear
identical. I chose several operating system files that I know have not
changed since the last server upgrade (more than a year ago) and they
still back up when using INCREMENTAL by itself.

The number of files backed up is just a few dozen short of the number
inspected - a difference which is attributable to those files that were
open (such as log files) and could not be backed up. Obviously, with
full backups running each night, my tape count in increasing
dramatically.

I have run traces, and have a call open with IBM. It has been open for
20 days. They are stumped as well, and have no idea what to do. So, I
was trying this avenue again in the hope that someone else may have seen
this. 



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: Monday, January 28, 2008 5:43 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM performing full backups where incremental
specified

Kevin -

Heck of a problem you have there.  I don't do z/OS or Netware, so
unlikely that I'll have an answer, but some thoughts...

This is too obvious, but: The filespaces involved are not in some way
being renamed or deleted in between the mass incrementals?  That would
cause a full backup.  Seems very unlikely to me, but one thing I would
consider.  Does a 'dsmc q fi' show a singular instance of the suspect
file system?  Here I'm thinking of some oddity causing the server to
believe that the file system is different each time.  But, tape
consumption would cause this to stand out.

In the backup log, does the number of objects backed up equal the
number inspected?  If a substantive difference, I would look into the
exceptions to see what's the basis of their immunity.  Also, perform a
'dsmc q ba -detail -ina ___' on one of the files and see if all
versions look the same, or there is some different which might incite
the backup.  And, if you don't see a bunch of versions, it may be
possible that some mutation to the policies is causing obliteration of
what was backed up the last time.

As a last resort, I would run a client trace of your partial versus
unqualified incrementals and see if any functional differences stand
out in causing the mass backups.  If nothing apparent, give TSM
Support a call.

wacky stuff I can think of,  Richard Sims

restoring multiple filespaces via lanfree

[goc]

hi, i'm having problems with restoring multiple filespaces via lan free
, data was backed up via 2 streams and i guess the only way to restore it
in the same manner is to start restore with mentioning all filespaces
i need for
restore, right ?

so this are my filespaces >

[EMAIL PROTECTED]:/tmp # dsmc -se=bscs_ca
IBM Tivoli Storage Manager
Command Line Backup/Archive Client Interface
  Client Version 5, Release 4, Level 0.0
  Client date/time: 01/29/08   14:08:56
(c) Copyright by IBM Corporation and other(s) 1990, 2007. All Rights Reserved.

Node Name: BSCS_CA
q Session established with server TSM01: AIX-RS/6000
  Server Version 5, Release 4, Level 1.0
  Server date/time: 01/29/08   14:08:56  Last access: 01/29/08   14:06:54

ftsm> q filespace
  # Last Incr Date  TypeFile Space Name
--- --  ---
  1   00/00/00   00:00:00   VxFS/
  2   00/00/00   00:00:00   VxFS/db/MBSCS4
  3   00/00/00   00:00:00   VxFS/db/bscs8/arch
  4   00/00/00   00:00:00   VxFS/db/bscs8/backup
  5   12/18/06   09:47:13   VxFS/db/bscs8/dbase/billimage
  6   12/18/06   09:47:13   VxFS/db/bscs8/dbase/data01
  7   12/18/06   09:47:13   VxFS/db/bscs8/dbase/data02
  8   00/00/00   00:00:00   VxFS/db/bscs8/dbase/data03
  9   12/18/06   09:47:13   VxFS/db/bscs8/dbase/index01
 10   12/14/06   14:58:24   VxFS/db/bscs8/dbase/index02
 11   00/00/00   00:00:00   VxFS/db/bscs8/dbase/index03
 12   12/18/06   09:47:13   VxFS/db/bscs8/dbase/redoctl01
 13   12/18/06   09:47:13   VxFS/db/bscs8/dbase/redoctl02
 14   12/18/06   09:47:13   VxFS/db/bscs8/dbase/redoctl03
 15   12/14/06   15:02:02   VxFS/db/bscs8/dbase/redoctl04
 16   00/00/00   00:00:00   VxFS/db/bscs8/dbase/temp01
 17   12/18/06   09:47:13   VxFS/db/bscs8/dbase/undo01

and i'm trying to restore all under .../dbase/ directory

i tried

dsmc res '/db/bscs8/dbase/data01/ /db/bscs8/dbase/data02/
/db/bscs8/dbase/data03/ /db/bscs8/dbase/index01/
/db/bscs8/dbase/index02/ /db/bscs8/dbase/index03/
/db/bscs8/dbase/redoctl01/ /db/bscs8/dbase/redoctl02/
/db/bscs8/dbase/redoctl03/ /db/bscs8/dbase/redoctl04/
/db/bscs8/dbase/temp01/ /db/bscs8/dbase/undo01/ ' -su=yes -se=bscs_ca

with *, with double quotes with su=yes without su=yes with quotes
around every filespace ... almost everything ... but nothing happens
... all i get is following


Restore function invoked.

ANS1247I Waiting for files from the server...
ANS1302E No objects on server match query

or

ANS1102E An excessive number of command line arguments are passed to
the program.
ANS1133W An expression might contain a wildcard not enclosed in quotes.

any clues would be greatly appreciated

thanks,
goran

TSM 5.4 on AIX
client 5.4 on HPUX

Re: GPFS file system backup problem

[Richard Sims]

On Jan 29, 2008, at 5:57 AM, Michael Green wrote:


01/29/08   02:29:28 ANS1999E Incremental processing of '/srv' stopped.


Michael -

Search on that message at the TSM Support page
http://www-306.ibm.com/software/sysmgmt/products/support/
IBMTivoliStorageManager.html
It may be the described case of too many directories.  Assure that
your Unix Resource Limits are not artificially low for the session.
See if any error indications in dsmerror.log.

   Richard Sims

GPFS file system backup problem

[Michael Green]

Bright minds,

Some time ago a problem has arisen with one of the GPFS file systems
that I happen to backup.
The system I'm talking about is:
Server: IBM x345 with SLES 9 SP3
FC switch: Cisco MDS9124
Storage: DS4400 (formerly FAStT700 ), latest firmware
GPFS ver: 2.3
Multipathing: IBM supplied RDAC (Linux MPP Driver Version: 09.01.B5.76)
TSM client: 5.4.1.2; server: 5.3.6
The filesystem:

bioinfo4:~ # df -h /srv
FilesystemSize  Used Avail Use% Mounted on
/dev/gpfs1452G  377G   76G  84% /srv
bioinfo4:~ # mmlsfs /dev/gpfs1
flag value  description
 -- -
 -s  roundRobin Stripe method
 -f  2048   Minimum fragment size in bytes
 -i  512Inode size in bytes
 -I  8192   Indirect block size in bytes
 -m  1  Default number of metadata replicas
 -M  1  Maximum number of metadata replicas
 -r  1  Default number of data replicas
 -R  1  Maximum number of data replicas
 -j  clusterBlock allocation type
 -D  posix  File locking semantics in effect
 -k  posix  ACL semantics in effect
 -a  1048576Estimated average file size
 -n  32 Estimated number of nodes that will mount file system
 -B  65536  Block size
 -Q  user;group Quotas enforced
 user;group Default quotas enabled
 -F  636Maximum number of inodes
 -V  8.01   File system version. Highest supported version: 8.02
 -u  yesSupport for large LUNs?
 -z  no Is DMAPI enabled?
 -E  yesExact mtime mount option
 -S  no Suppress atime mount option
 -d  gpfs4nsd  Disks in file system
 -A  yesAutomatic mount option
 -o  none   Additional mount options
 -T  /srv   Default mount point


Basically what happens is that the backup of that particular file
system never completes,  cuts short with return code 12.
I have two GPFS file systems on that linux box, both reside on the
same storage and are identically connected in terms of storage, FC
topology and multipathing.
One backs up without a hitch while the other doesn't. Log excerpt
below illustrates what's going on.
Online GPFS fsck returns no errors (mmfsck /dev/gpfs1 -o). I haven't
tried offline fsck.

Any ideas on how to proceed about this problem will be appreciated!

bioinfo4:~ # mmlsfs /dev/gpfs1
flag value  description
 -- -
 -s  roundRobin Stripe method
 -f  2048   Minimum fragment size in bytes
 -i  512Inode size in bytes
 -I  8192   Indirect block size in bytes
 -m  1  Default number of metadata replicas
 -M  1  Maximum number of metadata replicas
 -r  1  Default number of data replicas
 -R  1  Maximum number of data replicas
 -j  clusterBlock allocation type
 -D  posix  File locking semantics in effect
 -k  posix  ACL semantics in effect
 -a  1048576Estimated average file size
 -n  32 Estimated number of nodes that will mount file system
 -B  65536  Block size
 -Q  user;group Quotas enforced
 user;group Default quotas enabled
 -F  636Maximum number of inodes
 -V  8.01   File system version. Highest supported version: 8.02
 -u  yesSupport for large LUNs?
 -z  no Is DMAPI enabled?
 -E  yesExact mtime mount option
 -S  no Suppress atime mount option
 -d  gpfs4nsd  Disks in file system
 -A  yesAutomatic mount option
 -o  none   Additional mount options
 -T  /srv   Default mount point
bioinfo4:~ # df -h /srv
FilesystemSize  Used Avail Use% Mounted on
/dev/gpfs1452G  377G   76G  84% /srv


01/28/08   21:00:12 Scheduler has been started by Dsmcad.
01/28/08   21:00:12 Querying server for next scheduled event.
01/28/08   21:00:12 Node Name: BIOINFO4
01/28/08   21:00:12 Session established with server GALAHAD: Linux/i386
01/28/08   21:00:12   Server Version 5, Release 3, Level 6.0
01/28/08   21:00:12   Server date/time: 01/28/08   21:00:12  Last
access: 01/28/08   20:26:46

01/28/08   21:00:12 --- SCHEDULEREC QUERY BEGIN
01/28/08   21:00:12 --- SCHEDULEREC QUERY END
01/28/08   21:00:12 Next operation scheduled:
01/28/08   21:00:12 
01/28/08   21:00:12 Schedule Name: 21_SCHED_18
01/28/08   21:00:12 Action:Incremental
01/28/08   21:00:12 Objects:
01/28/08   21:00:12 Options:
01/28/08   21:00:12 Server Window Start:   21:00:00 on 01/28/08
01/28/08   21:00:12 
01/28/08   21:00:12
Executing scheduled command now.
01/28/08   21:00:12 --- SCHEDULEREC OBJECT BEGIN 21_SCHED_18 01/28/08   21:00:00
01/28/08   21:00:12 Incremental backu