Re: Windows excludes

2009-06-08 Thread Robben Leaf
Also, it looks like there shouldn't be a space between Software and
distribution in your exclude statement

Robben Leaf




From:
lindsay morris lind...@tsmworks.com
To:
ADSM-L@VM.MARIST.EDU
Date:
06/08/2009 12:48 PM
Subject:
Re: [ADSM-L] Windows excludes
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Do you need quotes around the directory names? I think yes.

--
Mr. Lindsay Morris
Principal
www.tsmworks.com
919-403-8260
lind...@tsmworks.com




On Jun 8, 2009, at Jun 8, 12:20 PM, Fred Johanson wrote:

 I'm trying to bring up to date all our cloptsets .  I've had some
 success, but these have me stumped.


 Directory
 Name
 Occurrences
 \\ad1\c$\Program Files\System Center Operations Manager 2007\Health
 Service State\Health Service Store\4
 \\ad1\c$\WINDOWS\SoftwareDistribution\DataStore
 \   1
 \\ad1\c$\WINDOWS\SoftwareDistribution\DataStore\Logs
 \2
 \\ad1\c$\WINDOWS\SoftwareDistribution\EventCache
 \1

 This is what I've tried

 INCLEXCL86  No exclude.dir c:
 \Program Files\System Center Operations
Manager 2007
 INCLEXCL88  No exclude.dir *:
 \...\Software distribution

 Where's the error?



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: TDP Oracle Authentication failure

2009-05-14 Thread Robben Leaf
Check to see if the user under which the Oracle rman process is running
has read permission to the TDPO.ora_xxx password file.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.l...@usbank.com



From:
TSM User tsm...@gmail.com
To:
ADSM-L@VM.MARIST.EDU
Date:
05/14/2009 07:51 AM
Subject:
[ADSM-L] TDP Oracle Authentication failure
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Hi all



I have a problem witch TDP for Oracle (Version 5, Release 4, Level 2.0) in
HP_UX B.11.11



TDP was property configured.



When exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf password, TDP Works
fine, and generate de password file (TDPO.xxx_ora)



But, when exec /opt/tivoli/tsm/client/oracle/bin64/tdpoconf
SHOWENVironment,
TSM server refuse (ANR0424W Session 52044 for node  (TDP Oracle
HP)  refused
- invalid password submitted.



And TDP show ANS1025E (RC137)  Session rejected: Authentication failure



Any help is appreciated



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Exclude Files From Restore?

2009-01-27 Thread Robben Leaf
Greetings,

In our environment, restores are by and large performed by the Operations
group. These are a simple folk, unschooled in the murky depths of ADvanced
STorage And Retrieval.

It has come to pass that the Threat and Vulnerability group is battling a
virus contamination. The infection takes the form of a file of a specific
name, which can appear anywhere on an infected server. It is too late to
prevent this file name from getting backed up to TSM.

A representative of the Threat and Vulnerability group has appealed to me
to configure TSM to prevent the possibility of this file name from being
restored inadvertently by Operations, for they are many, and work in
shifts, and are unlikely to consistently heed our admonitions.

From what I can tell, Excludes in an option file or client option set only
apply to backups and archives, not to restores or retrievals.

I have considered waylaying each of the Operations group and tattooing the
offending file name on the inside of their eyelids, but that seems
impractical. They are scattered among multiple locations across the
country.

Seriously, though, is there a way in TSM to prevent already-backed-up
files from being restored?

Thanks,

Robben Leaf

U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Archive script for selected directory names

2009-01-22 Thread Robben Leaf
Hello All,

I've got a customer who uses a NAS as a repository for various log files
from many servers. These log files are organized by server, then by year
and month in the directory structure on the file space. For example, any
log file from July of 2008 will be in a directory called
...\servername\y08\m07\. New servers will have their logs added to this
share without notice, in various places on the directory tree, but the log
directory naming convention will be consistent.

This customer requires monthly archives of all log files that are older
than 90 days. Once archived, the log files will be deleted - sort of a
poor man's HSM. The -deletefiles parameter in the TSM ARCHIVE command will
work for this. Note: NDMP does not support archives, or backups of
specific selected data, so this must be done via CIFS or NFS - I've got
that covered.

Due to corporate standards, the archive job will not be scheduled with
TSM, but rather with a third-party solution (Autosys).

I'm trying to write a script (a Windows batch file) that will figure out
what month it is and archive all - and only - the directories for the log
files from 4 months ago.

The problem I'm having is that the ellipses wildcard (\...\) for directory
specification cannot be used in the ARCHIVE command itself - it can only
be used for INCLUDE and EXCLUDE statements in the option file.

I can compensate for this by having the script rewrite the option file
each month with the right includes and excludes, but then the ARCHIVE
command gets effectively run from the command line - overriding the option
file's includes and excludes, even using INCLUDE.ARCHIVE and
EXCLUDE.ARCHIVE.

I can't figure out a way to get the ARCHIVE command to do its archives on
only, and all, the directories from one specific month.

This doesn't necessarily have to be done from a Windows server, though I'm
not real speedy with my unix shell scripting.

Any suggestions?

Thanks in advance!

Robben Leaf

U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Archive script for selected directory names

2009-01-22 Thread Robben Leaf
That might work, if there weren't also other, non-log files and
directories on that share that are older than 90 days, that we do NOT want
archived and deleted.

But it's worth keeping in mind. Thanks for the suggestion!

Robben Leaf




From:
Shawn Drew shawn.d...@americas.bnpparibas.com
To:
ADSM-L@VM.MARIST.EDU
Date:
01/22/2009 11:57 AM
Subject:
Re: [ADSM-L] Archive script for selected directory names
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Instead of trying to deal with the naming convention of the directories, I
would create an archive file list by simply doing a file search for any
file/directory that is older than 90 days.  I'm sure you can find a
windows version of gnu find that can do this.


Regards,
Shawn

Shawn Drew





Internet
robben.l...@usbank.com

Sent by: ADSM-L@VM.MARIST.EDU
01/22/2009 12:34 PM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] Archive script for selected directory names





Hello All,

I've got a customer who uses a NAS as a repository for various log files
from many servers. These log files are organized by server, then by year
and month in the directory structure on the file space. For example, any
log file from July of 2008 will be in a directory called
...\servername\y08\m07\. New servers will have their logs added to this
share without notice, in various places on the directory tree, but the log
directory naming convention will be consistent.

This customer requires monthly archives of all log files that are older
than 90 days. Once archived, the log files will be deleted - sort of a
poor man's HSM. The -deletefiles parameter in the TSM ARCHIVE command will
work for this. Note: NDMP does not support archives, or backups of
specific selected data, so this must be done via CIFS or NFS - I've got
that covered.

Due to corporate standards, the archive job will not be scheduled with
TSM, but rather with a third-party solution (Autosys).

I'm trying to write a script (a Windows batch file) that will figure out
what month it is and archive all - and only - the directories for the log
files from 4 months ago.

The problem I'm having is that the ellipses wildcard (\...\) for directory
specification cannot be used in the ARCHIVE command itself - it can only
be used for INCLUDE and EXCLUDE statements in the option file.

I can compensate for this by having the script rewrite the option file
each month with the right includes and excludes, but then the ARCHIVE
command gets effectively run from the command line - overriding the option
file's includes and excludes, even using INCLUDE.ARCHIVE and
EXCLUDE.ARCHIVE.

I can't figure out a way to get the ARCHIVE command to do its archives on
only, and all, the directories from one specific month.

This doesn't necessarily have to be done from a Windows server, though I'm
not real speedy with my unix shell scripting.

Any suggestions?

Thanks in advance!

Robben Leaf



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Archive script for selected directory names

2009-01-22 Thread Robben Leaf
I think I got it worked out. It goes a little like this:

set MONTH=%date:~4,2%
if (%MONTH%) == (01) set ARCHFOLDER=m09
if (%MONTH%) == (02) set ARCHFOLDER=m10
... etc. for all 12 months
net use W: \\IP_address\vol0 /user:username password
W:
FOR /F %%d IN ('dir /s /b %%ARCHFOLDER%%') DO (C:\path\dsmc arch %%d\*
-optfile=C:\path\dsmarch.opt -subdir=yes -deletefiles)
C:
net use W: /delete

It's all been tested, except for the -deletefiles parameter - waiting for
the customer's OK on that one. The fact that it has to open a new TSM
session for every directory slows it down a bit (hundreds of these
directories, at an extra 3-4 seconds per new TSM session), but it gets the
job done. Had some trouble initially running the dsmc from the W: drive
(ANS0101E), but fixed it by defining the DSM_DIR system variable.

Robben Leaf




From:
Robben N Leaf/MN/USB
To:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Date:
01/22/2009 01:42 PM
Subject:
Re: [ADSM-L] Archive script for selected directory names


That might work, if there weren't also other, non-log files and
directories on that share that are older than 90 days, that we do NOT want
archived and deleted.

But it's worth keeping in mind. Thanks for the suggestion!

Robben Leaf





From:
Shawn Drew shawn.d...@americas.bnpparibas.com
To:
ADSM-L@VM.MARIST.EDU
Date:
01/22/2009 11:57 AM
Subject:
Re: [ADSM-L] Archive script for selected directory names
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Instead of trying to deal with the naming convention of the directories, I
would create an archive file list by simply doing a file search for any
file/directory that is older than 90 days.  I'm sure you can find a
windows version of gnu find that can do this.


Regards,
Shawn

Shawn Drew





Internet
robben.l...@usbank.com

Sent by: ADSM-L@VM.MARIST.EDU
01/22/2009 12:34 PM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] Archive script for selected directory names





Hello All,

I've got a customer who uses a NAS as a repository for various log files
from many servers. These log files are organized by server, then by year
and month in the directory structure on the file space. For example, any
log file from July of 2008 will be in a directory called
...\servername\y08\m07\. New servers will have their logs added to this
share without notice, in various places on the directory tree, but the log
directory naming convention will be consistent.

This customer requires monthly archives of all log files that are older
than 90 days. Once archived, the log files will be deleted - sort of a
poor man's HSM. The -deletefiles parameter in the TSM ARCHIVE command will
work for this. Note: NDMP does not support archives, or backups of
specific selected data, so this must be done via CIFS or NFS - I've got
that covered.

Due to corporate standards, the archive job will not be scheduled with
TSM, but rather with a third-party solution (Autosys).

I'm trying to write a script (a Windows batch file) that will figure out
what month it is and archive all - and only - the directories for the log
files from 4 months ago.

The problem I'm having is that the ellipses wildcard (\...\) for directory
specification cannot be used in the ARCHIVE command itself - it can only
be used for INCLUDE and EXCLUDE statements in the option file.

I can compensate for this by having the script rewrite the option file
each month with the right includes and excludes, but then the ARCHIVE
command gets effectively run from the command line - overriding the option
file's includes and excludes, even using INCLUDE.ARCHIVE and
EXCLUDE.ARCHIVE.

I can't figure out a way to get the ARCHIVE command to do its archives on
only, and all, the directories from one specific month.

This doesn't necessarily have to be done from a Windows server, though I'm
not real speedy with my unix shell scripting.

Any suggestions?

Thanks in advance!

Robben Leaf




U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: How to delete Volhistory...

2009-01-21 Thread Robben Leaf
There are other non-optional parameters in the DELETE VOLHIST command -
those still need to be there.

DELete VOLHistory TODate=TODAY Type=REMOTE VOLUME=volume name FORCE=YES

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.l...@usbank.com



From:
Maria Ilieva mari...@gmail.com
To:
ADSM-L@VM.MARIST.EDU
Date:
01/16/2009 02:34 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Try audit library X checklabel=barcode  from the library client.
That worked for me.

Maria Ilieva


On Fri, Jan 16, 2009 at 8:14 AM, KIRAN-SYSTEMS
ki...@dqentertainment.com wrote:
 I am using the below command to delete volhis of a library client server
 from library manager server

 Del volhis vol=volume name force=yes


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
 Steven Harris
 Sent: Friday, January 16, 2009 11:24 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] How to delete Volhistory...

 We need detail Kiran, if we are to help.


 Please post the command you are using and the output when it doesn't
 work.  also  the output of a

 select * from volhistory where volume_name='XYZ000L3'  - with your
 volume of interest substituted

 Thanks

 Steve

 Steven Harris
 TSM Administrator, Sydney Australia




 KIRAN-SYSTEMS
 ki...@dqentertai
 NMENT.COM To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor cc
 Manager
 ads...@vm.marist Subject
 .EDU Re: [ADSM-L] How to delete
   Volhistory...

 16/01/2009 04:12
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 ads...@vm.marist
   .EDU






 The below command is not working for me.Iam using TSM Server 5.5.0

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
 Robben Leaf
 Sent: Friday, January 09, 2009 1:02 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] How to delete Volhistory...

 Not entirely true. The product doesn't provide a DOCUMENTED way to do
 this.

 There are some undocumented parameters for the DELETE VOLHIST command.
 Specifically, you can add vol=VOLNAME force=yes to the command to
remove
 the volume forcibly from the volhistory.

 We have found this command necessary when our library manager thinks
 another TSM server instance still owns a tape, when that instance has
 forgotten all about it.

 Robben Leaf




 From:
 Richard Sims r...@bu.edu
 To:
 ADSM-L@VM.MARIST.EDU
 Date:
 01/08/2009 06:14 AM
 Subject:
 Re: [ADSM-L] How to delete Volhistory...
 Sent by:
 ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



 On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

 Please let me know how to delete volume history of a particular
 Volume.

 The product does not provide a way to do this.

Richard Sims



 U.S. BANCORP made the following annotations
 -
 Electronic Privacy Notice. This e-mail, and any attachments, contains
 information that is, or may be, covered by electronic communications
 privacy
 laws, and is also confidential and proprietary in nature. If you are not
 the
 intended recipient, please be advised that you are legally prohibited
from
 retaining, using, copying, distributing, or otherwise disclosing this
 information in any manner. Instead, please reply to the sender that you
 have
 received this communication in error, and then immediately delete it.
Thank
 you in advance for your cooperation.



 -


 Disclaimer:
 This email message (including attachments if any) may contain
privileged,
 proprietary, confidential information, which may be exempt from any kind
of
 disclosure whatsoever and is intended solely for the use of addressee
(s).
 If you are not the intended recipient, kindly inform us by return e-mail
 and also kindly disregard the contents of the e-mail, delete the
original
 message and destroy any copies thereof immediately. You are notified
that
 any dissemination, distribution or copying of this communication is
 strictly prohibited unless approved by the sender.

 DQ Entertainment (DQE) has taken every reasonable precaution to minimize
 the risk of transmission of computer viruses with this e-mail; DQE is
not
 liable for any damage you may sustain as a result of any virus in this
 e-mail. DQE shall not be liable for the views expressed in the e-mail.
DQE
 reserves the right to monitor and review the content of all messages
sent
 to or from this e-mail address


 Disclaimer:
 This email message (including attachments if any) may contain
privileged, proprietary, confidential information, which may be exempt
from any kind of disclosure whatsoever and is intended

Re: How to delete Volhistory...

2009-01-08 Thread Robben Leaf
Not entirely true. The product doesn't provide a DOCUMENTED way to do
this.

There are some undocumented parameters for the DELETE VOLHIST command.
Specifically, you can add vol=VOLNAME force=yes to the command to remove
the volume forcibly from the volhistory.

We have found this command necessary when our library manager thinks
another TSM server instance still owns a tape, when that instance has
forgotten all about it.

Robben Leaf




From:
Richard Sims r...@bu.edu
To:
ADSM-L@VM.MARIST.EDU
Date:
01/08/2009 06:14 AM
Subject:
Re: [ADSM-L] How to delete Volhistory...
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote:

 Please let me know how to delete volume history of a particular
 Volume.

The product does not provide a way to do this.

Richard Sims



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Library manager oversubscription

2008-12-10 Thread Robben Leaf
The library manager allocates the drives to the server instances that
request mounts. If more mounts are requested than there are available
drives, then the most recent mount requests have to wait until a drive
becomes available. This is a pretty common occurrence in our environment
at certain times of the day. It doesn't hurt anything - it just makes some
processes take a little longer.

There's no need to adjust the number of tape drives available to each
server, unless one server has more critical processing to do and must have
priority to the drives over the other server. If all of the drives are
available to both of the TSM instances, the library manager will honor
mount requests on available drives as the requests come in.

Robben Leaf




From:
Thomas Denier [EMAIL PROTECTED]
To:
ADSM-L@VM.MARIST.EDU
Date:
12/10/2008 03:19 PM
Subject:
[ADSM-L] Library manager oversubscription
Sent by:
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



I support a TSM server running under mainframe Linux. The database
has been growing at varying rates since we installed TSM. We are
starting to think about splitting the workload between two TSM
servers if there is a major growth spurt before we upgrade to 6.1
(we are currently at 5.4.2.0). If we did this we would set up a
third server to act as a library manager for the other two. We
would want to be able to adjust the number of tape drives available
to each server to adjust to variations in the workload. This would
be done by adjusting the mountlimit settings for the tape device
classes. What would happen if we made a mistake in this process
and ended up with the servers collectively requesting more tape
drives than actually exist?



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Configure Shared Library in TSM...

2008-10-23 Thread Robben Leaf
Does the error only come from one of the TSM server instances? If so, can
that instance use any of the drives if the other instance is not using any
drives? Can each instance use all of the drives without error if the other
instance is not using any of the drives? What's the I/O error you're
getting?

Robben Leaf



From:
Kiran [EMAIL PROTECTED]
To:
ADSM-L@VM.MARIST.EDU
Date:
10/23/2008 12:17 AM
Subject:
Re: [ADSM-L] Configure Shared Library in TSM...



But iam getting IO error when iam performing backup operations from two
server.
I have 4 drives in my library using TS3310 Tape library.


Regards,
Kiran M
DQ ENTERTAINMENT LTD
[EMAIL PROTECTED]
Mobile :+919246395809,+919849725836


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hart, Charles A
Sent: Wednesday, October 22, 2008 7:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Configure Shared Library in TSM...

Yes as long as you have more than one tape drive.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kiran
Sent: Wednesday, October 22, 2008 6:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Configure Shared Library in TSM...

Hi,



How to configure Shared library in TSM.I need to share LTO library for
two TSM server instances.



Can I perform Backup/Archive, Restore/Retrieve operations from both
instances simultaneously?







Regards,

Kiran M



Disclaimer:
This email message (including attachments if any) may contain
privileged, proprietary, confidential information, which may be exempt
from any kind of disclosure whatsoever and is intended solely for the
use of addressee (s). If you are not the intended recipient, kindly
inform us by return e-mail and also kindly disregard the contents of the
e-mail, delete the original message and destroy any copies thereof
immediately. You are notified that any dissemination, distribution or
copying of this communication is strictly prohibited unless approved by
the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is
not liable for any damage you may sustain as a result of any virus in
this e-mail. DQE shall not be liable for the views expressed in the
e-mail. DQE reserves the right to monitor and review the content of all
messages sent to or from this e-mail address


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind
of disclosure whatsoever and is intended solely for the use of addressee
(s). If you are not the intended recipient, kindly inform us by return
e-mail and also kindly disregard the contents of the e-mail, delete the
original message and destroy any copies thereof immediately. You are
notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless approved by the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is not
liable for any damage you may sustain as a result of any virus in this
e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE
reserves the right to monitor and review the content of all messages sent
to or from this e-mail address



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


NDMP backup successful but incomplete

2008-06-12 Thread Robben Leaf
I've got an NDMP client (Celerra) with two file systems - /vol0, and /vol1.
When I run the backup (fulls only), /vol1 gets a complete backup, but /vol0
backs up only a few kilobytes, and the process ends as Successful.

To be more specific:

06/12/08 10:17:12 ANR2017I Administrator RNLEAF issued command: BACKUP
NODE
   SVGMN14GLBSM07 /vol0 mode=full  (SESSION: 36846)

06/12/08 10:17:14 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file

   system /vol0, started as process 552 by
administrator
   RNLEAF. (SESSION: 36846, PROCESS: 552)

...
06/12/08 10:17:37 ANR0988I Process 552 for BACKUP NAS (FULL) running in
the
   BACKGROUND processed 43,482 bytes with a completion
state
   of SUCCESS at 10:17:37. (SESSION: 36846, PROCESS:
552)

and...

06/12/08 10:17:14 ANR2017I Administrator RNLEAF issued command: BACKUP
NODE
   SVGMN14GLBSM07 /vol1 mode=full  (SESSION: 36846,
PROCESS:
   552)

06/12/08 10:17:16 ANR1063I Full backup of NAS node SVGMN14GLBSM07, file

   system /vol1, started as process 553 by
administrator
   RNLEAF. (SESSION: 36846, PROCESS: 553)

...
06/12/08 15:26:39 ANR0988I Process 553 for BACKUP NAS (FULL) running in
the
   BACKGROUND processed 620,126,384,679 bytes with a

   completion state of SUCCESS at 15:26:39. (SESSION:
36846,
   PROCESS: 553)

Now, the administrator of the Celerra can demonstrate that /vol0 has plenty
of data in it:

[EMAIL PROTECTED] nasadmin]$ nas_fs -size vol0
total = 1578910 avail = 900497 used = 678412 ( 42% ) (sizes in MB)
( blockcount = 3283714048 )
volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 ))
[EMAIL PROTECTED] nasadmin]$ nas_fs -size vol1
total = 1578910 avail = 985584 used = 593326 ( 37% ) (sizes in MB)
( blockcount = 3283714048 )
volume: total = 1603376 (sizes in MB) ( blockcount = 3283714048 ))

I see something similar when I look at the information TSM has about that
file space:

q filespace SVGMN14GLBSM07 /vol0 f=d

  Node Name: SVGMN14GLBSM07
 Filespace Name: /vol0
 Hexadecimal Filespace Name:
   FSID: 2
   Platform: DartOS
 Filespace Type: uxfs
  Is Filespace Unicode?: No
  Capacity (MB): 1,578,910.2
   Pct Util: 43.0
Last Backup Start Date/Time: 06/12/08 10:17:13
 Days Since Last Backup Started: 1
   Last Backup Completion Date/Time: 06/12/08 10:17:36
   Days Since Last Backup Completed: 1
Last Full NAS Image Backup Completion Date/Time: 06/12/08 10:17:36
Days Since Last Full NAS Image Backup Completed: 1



I don't know what kind of settings he might have on his end that might
affect how TSM accesses, or fails to access, a file system on the Celerra.
As you can see, the commands issued to invoke the backups are identical. No
client option sets are applied to the node.

TSM server is ver 5.3.5.2 on AIX 5.3; backing up to a VTL emulating a 3584
with LTO drives. If the version of DART on the Celerra matters, I'll dig it
up.

Does anyone have a theory as to why the /vol0 backup isn't backing up the
data that's there, while the backups of /vol1 are working fine?,

Thanks in advance!

Robben Leaf


U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Deleting tape that belongs to defunct TSM instance from volhist

2008-06-05 Thread Robben Leaf
There are some undocumented parameters to the Delete Volhist command.

Try:

   del volhist todate=today type=remote volume=A00229 force=yes

Robben Leaf




 Bell, Charles
 (Chip)
 [EMAIL PROTECTED]  To
 .COM ADSM-L@VM.MARIST.EDU
 Sent by: ADSM:cc
 Dist Stor
 Manager  Subject
 [EMAIL PROTECTED] [ADSM-L] Deleting tape that belongs
 .EDU to defunct TSM instance from
   volhist

 06/05/2008 03:55
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






Received the following when a tape would not checkin per normal, so I tried
a
label libv with overwrite:

06/05/08   15:44:37  ANR2017I Administrator BC03CB1 issued command: LABEL
libv
  3584_1 search=b labels=b checkin=scr overwrite=y
waitt=0
  (SESSION: 2)
06/05/08   15:44:37  ANR0984I Process 15 for LABEL LIBVOLUME started in the
  BACKGROUND at 15:44:37. (SESSION: 2, PROCESS: 15)
06/05/08   15:44:37  ANR8799I LABEL LIBVOLUME: Operation for library 3584_1
  started as process 15. (SESSION: 2, PROCESS: 15)
06/05/08   15:44:49  ANR8816E LABEL LIBVOLUME: Volume A00229 in library
3584_1
  cannot be labeled because it is currently defined in
a
  storage pool or in the volume history file. (SESSION:
2,
  PROCESS: 15)
06/05/08   15:44:49  ANR9756I No volumes were found. (SESSION: 2, PROCESS:
15)
06/05/08   15:44:49  ANR8801I LABEL LIBVOLUME process 15 for library 3584_1
  completed; 0 volume(s) labeled, 0 volume(s)
checked-in.
  (SESSION: 2, PROCESS: 15)
06/05/08   15:44:49  ANR0985I Process 15 for LABEL LIBVOLUME running in the
  BACKGROUND completed with completion state SUCCESS at
  15:44:49. (SESSION: 2, PROCESS: 15)

How do I delete just this one tape from volhist, without deleting any
others?
I think it is a database backup belonging to a defunct TSM instance (TSM2):

DATE_TIME: 2008-03-24 07:55:45.00
  UNIQUE: 0
TYPE: REMOTE
   BACKUP_SERIES:
BACKUP_OPERATION:
  VOLUME_SEQ:
DEVCLASS: LTO2
 VOLUME_NAME: A00229
LOCATION: TSM2
 COMMAND:

-
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the
individual or entity named in the address. If you are not the
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this information is strictly
prohibited. If you received this information in error, please
notify the sender and delete this information from your computer
and retain no copies of any of this information.



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Antwort: [ADSM-L] Windows 2nd instance - how to restore the DB?

2008-05-02 Thread Robben Leaf
I suspect you can get around this by updating environment variables before
you run the restore command. Maybe something like:

set DSMSERV_DIR=%SYS%\Program Files\tivoli\tsm\server2
set DSMSERV_CONFIG=%SYS%\Program Files\tivoli\tsm\server2\dsmserv.opt
set DSMSERV_LOG=%SYS%\Program Files\tivoli\tsm\server2dsmserv.log

At least, that's more or less how we do it in Unix.

And that way, you shouldn't need to use the -k parameter when doing the
restore.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]


   
 Ullrich Mänz
 [EMAIL PROTECTED]   
 Sent by: ADSM:To
 Dist Stor ADSM-L@VM.MARIST.EDU
 Manager   cc
 [EMAIL PROTECTED] 
 .EDU Subject
   [ADSM-L] Antwort: [ADSM-L] Windows
   2nd instance - how to restore the
 05/02/2008 05:23  DB? 
 AM
   
   
 Please respond to 
 ADSM: Dist Stor  
 Manager  
 [EMAIL PROTECTED] 
   .EDU   
   
   




Well, I've tested an similar environment and found a restore is running
for a specific instance only if volhist, devconfig, dsmserv.opt, and
dsmserv.dsk are copied from directory (i.e.) server2 to %SYS%\program
files\tivoli\tsm\server. You must prepare database and recoverylog
previously like you have already done with option -k instance name in
order to get a valid dsk file.

Good lluck

Mit freundlichen Grüßen / Best regards

Ullrich Mänz
System-Integration

FRITZ  MACZIOL Software und Computervertrieb GmbH
Ludwig Str. 180D, 63067 Offenbach, Germany

Office:
+49 69 38013500 15
Mobil:
+49 170 7678434
Fax:
+49 69 38013500 10
Web:
http://www.fum.de

FRITZ  MACZIOL Software und Computervertrieb GmbH
Amtsgericht Ulm, Handelsregister-Nummer: HRB 1936
Geschäftsführer: Heribert Fritz, Oliver Schallhorn, Frank Haines
Inhaber: Imtech N.V., Gouda, Niederlande
Referenzen finden Sie auf unserer Website, Rubrik 'News'.
For References, please click our website, button 'News'.
Mail powered by Lotus Notes Version 7



Wanda Prather [EMAIL PROTECTED]
Gesendet von: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
02.05.2008 01:13
Bitte antworten an
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


An
ADSM-L@VM.MARIST.EDU
Kopie

Thema
[ADSM-L] Windows 2nd instance - how to restore the DB?






Can someone give me guidance on how you would restore a data base to a 2nd
TSM server instance on Windows?
I'm trying to figure out how to effectively (and safely) work with a test
instance.

I can create the DB for the 2nd instance with: dsmserv -k server2  format
blah.

But when I try to use dsmserv -k server2 restore db, it apparently looks
for
the volhist and devconfig files in the server directory not the server2
directory; so dsmserv restore db doesn't appear to support -k.

Anybody done it?



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Combining two TSM servers into one.

2008-04-22 Thread Robben Leaf
If you don't already have domains on server 2 with the same names as the
ones on server 1, you'll want to EXPORT POLICY to server 2 first, and make
sure that the copy groups have valid storage pools for their destinations.
Then, when you EXPORT NODE, they'll be imported into the same policy
domains they were in on server 1, and the data will be copied into the
storage pools indicated for those copy groups.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Ochs, Duane
 [EMAIL PROTECTED]
 M To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU Re: [ADSM-L] Combining two TSM
   servers into one.

 04/21/2008 04:20
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






One question. I've read the documentation and it's not clear where the
data goes after it is imported.
There is no STG or devclass parameter allowed.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Robben Leaf
Sent: Monday, April 21, 2008 3:36 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Combining two TSM servers into one.

You can export a node's data directly from one TSM server instance to
another one if you use the TOSERVER parameter in the EXPORT NODE
command.

That being said, depending on your retention policies, it might be
simpler
- and faster - to simply take the clients that back up to TSM server 1,
and point them at TSM server 2, and let the old data expire off of
server 1 as time passes. If you need to restore from the old TSM server,
just point the client back to server 1 for the restore. When all the
data on server 1 is older than your retention policy, it can be
decommissioned. Archive data should be copied to server 2, of course.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Ochs, Duane
 [EMAIL PROTECTED]
 M
To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor
cc
 Manager
 [EMAIL PROTECTED]
Subject
 .EDU [ADSM-L] Combining two TSM
servers
   into one.

 04/21/2008 03:21
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I'm sure someone has done this before. I'm just looking for a little
kick in the right direction.
I have two TSM servers.
One (TSM server 1) with a L700 library using SDLT320 drives with a 50gb
db and approximately 90 TB of data and another (TSM server 2) using a SL
T950 with LTO-4. Both are behind the same SVC.
I'm combining the two TSM servers into the same library and into the
same TSM DB.

Option one, get a LTO-4 drive connected to TSM server1 and export nodes
one at a time, then import the data into TSM server 2.

Option two, get a SDLT320 drive connected to TSM server 2, export from
TSM server 1 and import into 2.

??? Option three,  Is it possible to export to disk, and move the file
system from TSM server 1 to TSM server 2 and import ?

Option 1 and 2 will be time consuming, Option 3 would probably be the
most efficient, if possible.
Any advice or any other suggestions ?

Both TSM servers are running TSM 5.4.3 on AIX 5.3.

Thanks,
Duane



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy laws, and is also confidential and proprietary in nature. If you
are not the intended recipient, please be advised that you are legally
prohibited from retaining, using, copying, distributing, or otherwise
disclosing this information in any manner. Instead, please reply to the
sender that you have received this communication in error, and then
immediately delete it. Thank you in advance for your cooperation.



-



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing

Re: LANFree Implementaion

2008-04-21 Thread Robben Leaf
Hi, Abid,

Did you define paths on the library manager between the storage agent and
the drives it will use? For the Device parameter in the path definitions,
you need to use the tape drive device names as they appear on the client
machine.

Good luck and let us know how it's going,

Robben Leaf





 Abid Ilias
 [EMAIL PROTECTED]
 EDU   To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU [ADSM-L] LANFree Implementaion


 04/17/2008 01:03
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I am trying to get LANFree work on one of our Windows 2003 machine, but
running into issues.  I have installed all the required software.



Our scenario is as follows



Library Manager - This is where the paths are defined from the storage
agent(node) to the Tape drives



Library Client - This is where the node is registered and the
dataread/datawrite is set to LANFree.  This node is in a domain where
the copy destination of backup copy group is pointing to a Tape Storage
pool.



Node - Windows 2003 machine (this is where the storage agent is running)
and TSM backup client software installed and configured for the Node.







When ever I kick off the backup, my paths for that storage agent go
offline with the following error code. This is part of the activity log
from the Library Client





04/17/08   12:14:15  ANR8963E (Session: 6166, Origin: LYMAN_STA)
Unable to

  find path to match the serial number defined
for drive

  DR5516 in library CAPEKLIB1 . (SESSION: 6166)

04/17/08   12:14:15  ANR0408I (Session: 6166, Origin: LYMAN_STA)
Session 27

  started for server NECLM (AIX-RS/6000)
(Tcp/Ip) for

  library sharing.  (SESSION: 6166)

04/17/08   12:14:15  ANR0409I (Session: 6166, Origin: LYMAN_STA)
Session 27

  ended for server NECLM (AIX-RS/6000).
(SESSION: 6166)

04/17/08   12:14:15  ANR8873E (Session: 6166, Origin: LYMAN_STA)
The path from

  source LYMAN_STA to destination DR5516
(mt7.0.0.2) is

  taken offline. (SESSION: 6166)



This is the log from the client.





ANS1228E Sending of object
'\\lyman\d$\rm_mounts\healy\edrive\mount\sg1data\Program
file:///\\lyman\d$\rm_mounts\healy\edrive\mount\sg1data\Program
Files\Microsoft\Exchange Server\Storage Group
1\CatalogData-17e0dbd1-58f0-4608-97ef-1e493e832a15-cd14e744-98a7-44b9-87
0f-f77675d52d8d\00010001.ci' failed ANS1312E Server media mount not
possible



ANS0350E The current client configuration does not comply with the value
of the DATAWRITEPATH or DATAREADPATH server option for this node





If would appreciate if someone can shed some light on it.





Thanks

Abid Ilias

TSM Administrator

773-702-0246





U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Combining two TSM servers into one.

2008-04-21 Thread Robben Leaf
You can export a node's data directly from one TSM server instance to
another one if you use the TOSERVER parameter in the EXPORT NODE command.

That being said, depending on your retention policies, it might be simpler
- and faster - to simply take the clients that back up to TSM server 1, and
point them at TSM server 2, and let the old data expire off of server 1 as
time passes. If you need to restore from the old TSM server, just point the
client back to server 1 for the restore. When all the data on server 1 is
older than your retention policy, it can be decommissioned. Archive data
should be copied to server 2, of course.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Ochs, Duane
 [EMAIL PROTECTED]
 M To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU [ADSM-L] Combining two TSM servers
   into one.

 04/21/2008 03:21
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I'm sure someone has done this before. I'm just looking for a little
kick in the right direction.
I have two TSM servers.
One (TSM server 1) with a L700 library using SDLT320 drives with a 50gb
db and approximately 90 TB of data and another (TSM server 2) using a SL
T950 with LTO-4. Both are behind the same SVC.
I'm combining the two TSM servers into the same library and into the
same TSM DB.

Option one, get a LTO-4 drive connected to TSM server1 and export nodes
one at a time, then import the data into TSM server 2.

Option two, get a SDLT320 drive connected to TSM server 2, export from
TSM server 1 and import into 2.

??? Option three,  Is it possible to export to disk, and move the file
system from TSM server 1 to TSM server 2 and import ?

Option 1 and 2 will be time consuming, Option 3 would probably be the
most efficient, if possible.
Any advice or any other suggestions ?

Both TSM servers are running TSM 5.4.3 on AIX 5.3.

Thanks,
Duane



U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Celerra tape device names for NDMP

2008-03-28 Thread Robben Leaf
I'm setting up NDMP backups for a Celerra; the TSM server to which it will
be backed up is the library controller, and the library is an EMC VTL,
emulating an IBM 3584.

I've presented four tape drives to the Celerra from the VTL - one HBA on
the Celerra is zoned to two HBA's on the VTL, and two drives are presented
down each path. In order to correctly set up the paths on the TSM server, I
need to know which device name on the Celerra corresponds to which drive in
the VTL. The device names on the Celerra look like this:

c128t0l0
c128t0l1
c144t0l0
c144t0l1

Now, I know that the last two characters refer to the LUN numbers, and
since I know which drives are presented with which LUN numbers, this gives
me a 50-50 chance of getting it right if I just guess. The c### part seems
to be a chain or scsi controller number. Interestingly, all of the chain
numbers I've seen from the Celerra were divisible by 16.

Does anyone know how to find a connection between the chain numbers in the
Celerra and the port ID's or WWN's on the VTL? Or am I reduced to making a
guess, and if it doesn't work, trying it the other way around?

If it helps, here are the WWN's and port ID's (in hex and decimal) and
adapter numbers over which the drives are presented from the VTL:

21-03-00-0d-77-fe-61-08   61.18.13  97.24.19  Adapter 1
21-03-00-0d-77-be-61-08   61.14.13  97.20.19  Adapter 3

Any help is appreciated!

Robben Leaf


U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: PLEASE I NEED YOUR HELP TO DEFINE AN EXCEPTION IN A SCHEDULER

2007-12-03 Thread Robben Leaf
Unfortunately, in the Define Schedule command, the DAYOFMONTH parameter
doesn't play nicely with the DAYOFWEEK parameter, according to the manuals.

One way to get around this is to define a couple of Administrative
schedules that run once a month, one that will Delete Association for the
nodes associated with the schedule, and another to Define Association for
those nodes. The clients will need to be in Polling mode to catch the
updates without having their schedulers restarted, and someone will have to
remember to update these Administrative schedules every time a node is
added to or removed from the Client schedule.

Robben Leaf



   
 Wladimir 
 Benavides
 [EMAIL PROTECTED]  To
 IA.COM.ECADSM-L@VM.MARIST.EDU
 Sent by: ADSM:cc
 Dist Stor 
 Manager  Subject
 [EMAIL PROTECTED] [ADSM-L] PLEASE I NEED YOUR HELP TO
 .EDU DEFINE AN EXCEPTION IN A SCHEDULER
   
   
 12/03/2007 09:03  
 AM
   
   
 Please respond to 
 ADSM: Dist Stor  
 Manager  
 [EMAIL PROTECTED] 
   .EDU   
   
   




Hi:

Please I need you name to define an exception in a scheduler.

I want to define a scheduler that has to run dialy, on Monday, Tuesday,
Wenesday, Thursday and Friday, but this scheduler don´t have to run the
first day of every month. I can define this scheduler, but I don´t know how
to define this exception.

Thanks and regards.




El servicio de Symantec Hosted Mail Security ha verificado que el mensaje
se
encuentra libre de Virus.




U.S. BANCORP made the following annotations
-
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



-


Re: Tapes with a status of filling.

2007-09-27 Thread Robben Leaf
We have found that if you have a storage pool's collocation parameter set
to Group, but you have nodes that aren't in a collocation group, TSM treats
each such node as if it were in its own group - thus, each such node's data
gets written to its own set of tapes. If you have a lot of
un-collocation-grouped nodes writing to that storage pool, it will put a
lot of tapes into the filling state.

Robben Leaf




 Richard Sims
 [EMAIL PROTECTED]
 Sent by: ADSM:To
 Dist Stor ADSM-L@VM.MARIST.EDU
 Manager   cc
 [EMAIL PROTECTED]
 .EDU Subject
   Re: [ADSM-L] Tapes with a status of
   filling.
 09/27/2007 11:04
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






On Sep 27, 2007, at 11:57 AM, Ochs, Duane wrote:

 Any quick ideas on why I'm seeing an increase on volumes with low
 usage,
 no errors and a status of filling ?

 I think it has to do with my migrations getting completed and the
 thresholds being set to 0 for longer than necessary.

Duane -

See   Tape leak
and   Shrinking (dwindling) number of available scratch tapes (tape
leak)
inhttp://people.bu.edu/rbs/ADSM.QuickFacts
for the standard reason for this.  If other causes found, let me know.

   Richard Sims




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: TSM and Windows Cluster Environment

2007-07-12 Thread Robben Leaf
?
echo.
echo OtherDrives:   Any other drives in the vnode, e.g. M: N:
echo.
echo HTTPport:  Httpport CAD service will listen on, e.g. 1591,
1592,..
echo.
echo Servername:The TSM server that this node will back up to
echo.

:end

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Bos, Karel
 [EMAIL PROTECTED]
 IGIN.COM  To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU Re: [ADSM-L] TSM and Windows
   Cluster Environment

 07/12/2007 10:26
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






Hi,

Yep, we and others have.

What are the problems you are running into? Installing ITSM clients in a
cluster is described in the ITSM client documentation.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Mochnaczewski
Sent: donderdag 12 juli 2007 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: TSM and Windows Cluster Environment

Hi *,

Has anyone successfully implemented TSM in a Windows Cluster environment
? We are running into various problems when trying to configure the TSM
client on certain servers in the cluster and IBM is not being very
helpful.

TSM Server : 5.3.3.0 running on AIX 5.2 ML9


Rich



--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: Maximum Capacity for a File Device Class

2007-07-11 Thread Robben Leaf
We are now at version 5.3.5.0, and we still have the 63 GB limit on file
devclass maximum capacity. Figured it out the hard way.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Joni Moyer
 [EMAIL PROTECTED]
 ARK.COM   To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU [ADSM-L] Maximum Capacity for a
   File Device Class

 07/11/2007 09:31
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






Hey Everyone,

I recently upgraded to TSM 5.3.4.2 on an AIX server.  Prior to this I had
set the maximum capacity to be 63 GB, but would anyone happen to know
where I can find the maximum setting for a file device class at this TSM
version?  I have found everything but the info. that I actually wanted in
the manuals, so I think I must be looking in the wrong location.  Any help
is appreciated.  Thanks!

Device Class Name: DBBFILE
Device Access Strategy: Sequential
Storage Pool Count: 0
   Device Type: FILE
Format: DRIVE
 Est/Max Capacity (MB): 64,512.0
   Mount Limit: 1
  Mount Wait (min):
 Mount Retention (min):
  Label Prefix:
   Library:
 Directory: /tsmprod/db1backup
   Server Name:
  Retry Period:
Retry Interval:
Shared:
High-level Address:
  Minimum Capacity:
  WORM: No
  Drive Encryption:
   Scaled Capacity:


Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III
Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]





--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: unloaddb/loaddb

2007-06-29 Thread Robben Leaf
135 GB database, 43% used before the reorg (35% after), very fragmented,
took 14 hours to unload, and maybe 7 or 8 hours for the load.
92 GB database, 63% used before the reorg (40% after), very fragmented,
took 13 hours for the unload, about 6 hours for the load.

As always, YMMV.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 William Boyer
 [EMAIL PROTECTED]
 .NET  To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU Re: [ADSM-L] unloaddb/loaddb


 06/28/2007 05:11
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






What kind of throughput did you see on the unload/load processes?

Bill Boyer
Growing old is mandatory, growing up is optional - ??


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Robben Leaf
Sent: Thursday, June 28, 2007 5:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: unloaddb/loaddb

We recently did unloaddb / loaddb's to a couple of our TSM servers, to a
FILE-type devclass, with great success. Much easier than
messing with manual libraries, in my opinion.

If you can scrounge up 25 GB or so of disk space, that should be more than
enough for your purposes; we temporarily hijacked a disk
pool volume for this operation. Make a FILE-type devclass (make sure the
max capacity is as big as the amount of space you have - we
found a limit at 63 GB), and when you're ready to perform the operation, do

dsmserv unloaddb devclass=DEVCLASSNAME
(when this is done, be sure to record the name of the volume it created for
the unload) dsmserv loadformat # logvol1name ...
logvol#name ## dbvol1name ...
dbvol##name
dsmserv loaddb devclass=DEVCLASSNAME volume=/path/volumename

Assuming the unloaddb came up with a consistent image, you shouldn't need
to do an audit of the database after the loaddb -
probably.

Note that we are on ver 5.3; I don't know what differences there might be
with 5.2 (is the loadformat command new to 5.3, for
example; if so, the format command should work in its place) - best to look
it up and verify.

We have also done unloaddb / loaddb's successfully on some 5.3 servers
using a non-manual library; the library is a shared one, and
the library manager instance worked just fine handling the scratch volume
allocation and drive mounts; that being said, we have also
had failures using this method, which is what led us to the FILE devclass
solution.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Gill, Geoffrey
 L.
 GEOFFREY.L.GILL@  To
 SAIC.COM ADSM-L@VM.MARIST.EDU
 Sent by: ADSM:cc
 Dist Stor
 Manager  Subject
 [EMAIL PROTECTED] [ADSM-L] unloaddb/loaddb
 .EDU


 06/27/2007 08:10
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I'm trying to reduce the assigned capacity of the DB since it is only 18%
utilized but it looks like I've hit a roadblock. I'm
thinking I need to run the uloaddb and loaddb to fix this but not totally
sure. If so, as I read it, it sounds like the library
needs to be changed to manual in order for this command to work when going
to tape. It also sounds like other commands should be run
after it and before the loaddb is run.



Anyone out there with a 3494 out there that has done this and can send what
commands and order you've run? I have an old server I'd
like to test this on to see how long it would take to run on a db sized at
about 73GB that is only 18% utilized. I'd call support
but at 5.2 would be told to upgrade the system.



Thanks,



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






--

Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic
communications privacy laws, and is also confidential and proprietary in
nature. If you are not the intended recipient, please be
advised that you are legally prohibited from retaining, using, copying,
distributing, or otherwise disclosing this information in
any manner. Instead, please reply to the sender that you have received this
communication in error

Re: unloaddb/loaddb

2007-06-28 Thread Robben Leaf
We recently did unloaddb / loaddb's to a couple of our TSM servers, to a
FILE-type devclass, with great success. Much easier than messing with
manual libraries, in my opinion.

If you can scrounge up 25 GB or so of disk space, that should be more than
enough for your purposes; we temporarily hijacked a disk pool volume for
this operation. Make a FILE-type devclass (make sure the max capacity is as
big as the amount of space you have - we found a limit at 63 GB), and when
you're ready to perform the operation, do

dsmserv unloaddb devclass=DEVCLASSNAME
(when this is done, be sure to record the name of the volume it created for
the unload)
dsmserv loadformat # logvol1name ... logvol#name ## dbvol1name ...
dbvol##name
dsmserv loaddb devclass=DEVCLASSNAME volume=/path/volumename

Assuming the unloaddb came up with a consistent image, you shouldn't need
to do an audit of the database after the loaddb - probably.

Note that we are on ver 5.3; I don't know what differences there might be
with 5.2 (is the loadformat command new to 5.3, for example; if so, the
format command should work in its place) - best to look it up and verify.

We have also done unloaddb / loaddb's successfully on some 5.3 servers
using a non-manual library; the library is a shared one, and the library
manager instance worked just fine handling the scratch volume allocation
and drive mounts; that being said, we have also had failures using this
method, which is what led us to the FILE devclass solution.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Gill, Geoffrey
 L.
 GEOFFREY.L.GILL@  To
 SAIC.COM ADSM-L@VM.MARIST.EDU
 Sent by: ADSM:cc
 Dist Stor
 Manager  Subject
 [EMAIL PROTECTED] [ADSM-L] unloaddb/loaddb
 .EDU


 06/27/2007 08:10
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I'm trying to reduce the assigned capacity of the DB since it is only
18% utilized but it looks like I've hit a roadblock. I'm thinking I need
to run the uloaddb and loaddb to fix this but not totally sure. If so,
as I read it, it sounds like the library needs to be changed to manual
in order for this command to work when going to tape. It also sounds
like other commands should be run after it and before the loaddb is run.



Anyone out there with a 3494 out there that has done this and can send
what commands and order you've run? I have an old server I'd like to
test this on to see how long it would take to run on a db sized at about
73GB that is only 18% utilized. I'd call support but at 5.2 would be
told to upgrade the system.



Thanks,



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






--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: ALL Tapes known to TSM

2007-06-13 Thread Robben Leaf
Welcome to the community, Daad!

1- TSM classifies tapes in three partially-overlapping ways: LIBVOL's are
the tapes that TSM knows about in an attached tape library; a Q LIBVOL
will show these volumes, including scratch tapes, and other tapes in the
library that aren't in storage pools. VOL's are all volumes (including disk
volumes) that are in any storage pools; Q VOL will show all of these
volumes. Scratch tapes aren't in storage pools. DRMEDIA are tapes that are
in any copy storage pools, plus any database backups (which aren't in
storage pools), whether these tapes are in the librarey or off site; Q
DRMEDIA will show all of these tapes. Between these three commands, you
should get all of the tapes that TSM knows about, many of them more than
once.

2- If a tape shows up as type=STGNEW in the volhistory, it's been checked
in as a new, empty volume; TSM doesn't know about any data that might be on
it.

If the TSM database doesn't know about the data on a volume, it won't be
able to get any data off of that volume. There are two exceptions: One, if
node data was exported to a tape with the EXPORT NODE command; then, the
IMPORT NODE command can be used to extract the information even if the
TSM database doesn't know about it. Two, if a backupset was made using
GENERATE BACKUPSET, the client can restore the data directly from the
tapes the data was written to.

Hope this helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Daad Ali
 [EMAIL PROTECTED]
 Sent by: ADSM:To
 Dist Stor ADSM-L@VM.MARIST.EDU
 Manager   cc
 [EMAIL PROTECTED]
 .EDU Subject
   [ADSM-L] ALL Tapes known to TSM

 06/13/2007 02:28
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






a couple of  newbie questions,

  1- How can I list ALL the tapes that are known to TSM (onsite, offsite,
drm, scratch ..etc)?



  2- If a tape shows as STGNEW, will the data in it be recoverable?

  To give a little bit of history...
  I have a bunch of tapes, I am told used to belong to this TSM server as
exchange and SQL server backups and I can olny find them in the volume
history file as STGNEW. I don't see them as with q vol.

  Once again, thanks a bunch.

  Best regards,
  Daad



-
Ask a question on any topic and get answers from real people. Go to Yahoo!
Answers.




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: TSM on Windows Cluster

2007-04-17 Thread Robben Leaf
You can also use the dsmcutil update cad... and dsmcutil update
remoteagent... commands to set the password on the passive node if you
don't want to fail it over every 90 days.

In fact, I would recommend setting up a batch file for each of your cluster
nodes that uses dsmcutil to update the password.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Greg Yuzik
 [EMAIL PROTECTED]
 CES.COM   To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU Re: [ADSM-L] TSM on Windows Cluster


 04/17/2007 10:36
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






I resolve the same issue I had by taking the Shared TSM Scheduler
offline in the cluster admin, failover the cluster, then opened up the
TSM GUI which prompted me for a password...

Then I was about to start the Shared TSM Scheduler on both nodes and the
failover now works great.

: : Greg Yuzik : :


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Fawad Baig
Sent: Tuesday, April 17, 2007 8:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM on Windows Cluster

Hi,

After setting up TSM on a windows cluster it seems that everytime a
failover
occurs the TSM service on the cluster does not automatically start up. I
have to manually log in start the cluster services through the cluster
admin
and then there is a password mismatch so i have to reset the password in
TSM
and then restart the TSM cluster service via cmd line with

dsmc -optfile=g:\tsmconfig1

Everytime i resync the password on the tsm server for the active node ,
it
ofcourse becomes out of sync with the passive node for the next login.
Seems
the registry is not holding the password and every 90 days this happens
as
the password expires. I cannot set password expiration to zero as its
against regulations. How can I have the registry hold these TSM
passowrds?
Am i doing something wrong? The redbook does not speak on this so im
kinda
lost. Any ideas appreciated.Thanks.

--
Regards,
Fawad Baig




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Windows LAN-free client HBA replacement

2006-11-10 Thread Robben Leaf
The Windows 2003 LAN-free client has been configured and working properly
for some time now. It uses Gresham/ACSLS to share an STK library and drives
with our TSM servers. TSM client, storage agent and server versions are all
5.3.2.0.

So the client's HBA that connects to the tape drives went kablooey
yesterday and had to be replaced. After the storage folks rezoned the new
HBA's WWN to the drives in the SAN, Windows discovered them as it should.
So far, so good.

Naturally, the drives all came back with different names than they used to
have. No big deal, I have spreadsheets telling me which ACSLS drives have
which WWN's, so looking in the Management Console gives me the information
I need to update the elm.cnf file so Gresham can tell TSM which drive ACSLS
is mounting its tape in.

But the Device Names are all different from the TSM Names in the Management
Console. The TSM names look like mt.3.0.0.3, and the Device Names look
like \\.\Tape0. Oh yeah, that means that the drives are all using the
default STK drivers - I need to go into Device Manager and update the
drivers that the tape drives use to the TSMSCSI driver.

And here's where I run into problems. When I try to apply that driver
(which appears to be loaded on the system, and used to work fine before the
HBA replacement) to a drive, the icon for that drive gets the error marker
on it, and the Device Status window in the Properties for the drive shows
This device is not working properly because Windows cannot load the
drivers required for this device. (Code 31).

When I run tsmdlst, it tells me that my TSMSCSI driver is running:

C:\TSM\storageagenttsmdlst

Tivoli Storage Manager -- Device List Utility

Licensed Materials - Property of IBM

5697-TSM (C) Copyright IBM Corporation 2000, 2005. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corporation.

Computer Name:  WIN2003LANFREECLIENT
OS Version: 5.2
OS Build #: 3790
TSM Device Driver:  TSMScsi - Running
.. (boring HBA and drive information, which all looks kosher)

Have I neglected to do something critical that will allow the TSM tape
driver to work on these drives? Do I need to get the TSMSCSI driver
reloaded on that system? Is this something that (this being Windows) a
simple reboot will fix? I would prefer not to hear maybe or even
probably, because a reboot for this server is a non-trivial event,
business-wise, so if that's what I ask for, it had better work.

Thanks in advance for any responses!

Robben Leaf
[EMAIL PROTECTED]


--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Oracle rman LAN-free to virtual tape timeout issue

2006-11-08 Thread Robben Leaf
The setup: TSM servers are ver 5.3.2.0, running on AIX. The situation in
question involves one TSM server instance that the client backs up to, and
a TSM server instance acting as a library manager for a virtual tape
library.

The client (ver 5.3.2.0) is LAN-free, and doing an rman backup of an Oracle
database. The session starts and is proxied normally to the library
manager, the tape gets mounted, and the catalog compilation starts.

15 minutes and a few seconds later (that's just over 900 seconds) - and
it's always this long, but it's also always the same time each day, 4:15 AM
- the proxied session that's holding the tape drive open gets severed
(ANR0480W) from the TSM backup server. A few minutes later, the catalog
compilation finishes and the client tries to start backing up files, but
can't because there isn't a tape available; the backup fails.

The commtimeout parameter on both of the TSM servers is 16,400 seconds; on
the storage agent it's 14,400. The idletimeout parameter on the servers and
the storage agent is 720 minutes. The throughputtimethreshold on the
storage agent is 270 minutes. There aren't any timeout-type parameters set
in the stanza for this node in the dsm.sys file.

Am I missing some timeout parameter that has a default of 15 minutes? Could
rman be timing something out?

Any ideas?

Robben Leaf


--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: Newbie Question cluster backups

2006-09-25 Thread Robben Leaf
The Windows B/A Client manual has a good description on how to do this in
one of its appendices.

In general terms, you need to define a separate node name for the data to
be backed up from the new drive; get an option file on the new drive; set
up services (TSM Schedules, Client Acceptor, and Remote Agent) on EACH of
the physical hosts that the vnode can fail over to, and set up cluster
services in Windows' Cluster Administrator to control those services.

Some gotchas: For clustered services, make sure you choose an HTTP port and
TCP client port that are different from those used by all other nodes
within the cluster. Make sure the option file has only the drives for that
vnode in its Domain statement. The set of services on the different
physical hosts for that vnode must have IDENTICAL names (i.e. the service
called TSM Scheduler: VNODENAME must be named exactly the same way on
every host that that vnode can fail over to). The local services on each
physical host for the vnode must be set to Manual, not Automatic - they
will be controlled by the cluster services. The most straightforward way to
get the password validated for the services on each physical host is to
fail the vnode over to that physical host before you create the services.

Hope this helps - good luck!

Robben



 Matthews, Gary
 [EMAIL PROTECTED]
 GICACMG.COM   To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU [ADSM-L] Newbie Question cluster
   backups

 09/25/2006 07:50
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






Hi,

Have a question about setting a backup. I've inherited a Tivoli backup
solution and am very slowly getting to grips with it ( have a NetBackup
background) and now need help in setting up a new backup. We've a sql
cluster wdccdb01 which has been set up backup the local drives via each
side of the cluster separately (wdccsq01/02) - The clustered disk
resource hold the SQL database and that backs up the SQL agent, so
there's a dsm.opt file  in TSM/baclient locally  for each node  and a
dsm.opt file in TSM/TDPsql locally on each client. Now we've just put on
another drive to the cluster( non SQL) - First time for me to set up a
new backup -  What's the best way to set this backup up

Cheers

Gary


This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: Reuse node name

2006-08-24 Thread Robben Leaf
We have had very good luck with the RENAME NODE method. It's quick and
simple, and allows you to keep the last version of the old server's backup
until you're positive you want to discard it.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Keith Arbogast
 [EMAIL PROTECTED]
 .EDU  To
 Sent by: ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager
 [EMAIL PROTECTED] Subject
 .EDU [ADSM-L] Reuse node name


 08/24/2006 02:18
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






A Windows sys-admin wishes to replace an existing Windows 2000 server
with a newly built Windows 2003 server, but using the old name for
the new server.  We have been backing up the old server for some
time.  He is adamant that he won't need to roll back to the old
server, or restore any files from its backups.

I'm wondering what problems might occur when we start backing up
files from the new client, for instance since the file systems on the
old and new servers will be somewhat different.

Would the best way to avoid problems be to do a RENAME NODE of the
old client?  Then, register the new server with the old name and TSM
won't have any records associated with that name to 'confuse' it.

If there is a simpler way, or if no intervention is required, I would
be glad to know that.

Our TSM servers are at version 5.3.0.2.

Thank you,
Keith Arbogast




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==


Re: include/exclude errors

2006-08-08 Thread Robben Leaf
It looks like it thinks there's a space between /back_txprod:backups-3.0/
and .../* ; If there is a space there, remove it, or try putting the file
specification in quotes.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
[EMAIL PROTECTED]



 Laura Lantz
 [EMAIL PROTECTED]
 Sent by: ADSM:To
 Dist Stor ADSM-L@VM.MARIST.EDU
 Manager   cc
 [EMAIL PROTECTED]
 .EDU Subject
   [ADSM-L] include/exclude errors

 08/08/2006 11:42
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






TSM 5.2.2
AIX 5.2

Hello Everyone!

I am getting the following errors in my dsierror.log file:

08/08/06   10:54:27 Management class '.../*' named on include/exclude line
0
does not exist.

Here is the actual include statement:

include /back_txprod:backups-3.0/.../* database

I know this a syntax problembecause of the spaces and using a
differerent management class other than the default. Please help with the
correct syntax.

Many thanks,




Laura




--
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.
==