Question ???

[Robert Ouzen Ouzen]

Hi to all

 

Try to link the search.adsm.org for a search of old post but get “Page cannot 
be found” ? Did the site change or just a temporary problem 

 

Did another site to search 

 

Regards Robert OuZen

Re: measuring shoeshining ?

[Peter Billam]

Greetings.  I wrote:
>Is there a good way of collecting daily shoeshining statistics ?

Roger Deschner wrote:
> Interesting question. I would simply measure tape throughput.
> ... You could scan the activity log for migration and reclamation
> completed stats, and also look for backup sessions that mounted a
> tape and grab their accounting stats.

Is there a good SQL query for throughput ?  Throughput grouped by
node is what's needed for the direct-to-disc case.

> ..., you can open a door on the back and have access to the back
> of the tape drives. I should borrow a doctor's stethescope and see
> if I can hear anything from the back.

In our server-room you wouldn't hear much, now that our fierce new
air contitioners have been installed :-)

> I wonder if the tape drives many of us use (LTO and SDLT) collect any
> of this information. ...
> Is anybody from someplace like Quantum or the LTO consortium listening?

The hardware could collect filemark counts.  (Or, after the fact,it
might be easy to read the tape and count filemarks ?) (Is filemark
the right word ?) But I don't see how it could know whether the
filemark was an emergency motivated by buffer-underrun.
Maybe only the application (dsmserv) knows that ?

And maybe that's the disconnect here; maybe only the driver and drive
know whether a mark-and-backspace was done, and the application knows
if it's expecting more data in the same stream, and maybe they don't
talk to each other ?

If the information _is_ to be had in one place, it's probably the scsi
tape driver, like drivers/scsi/st.c and Documentation/scsi/st.txt,
because that wrestles with the buffers, filemarks, backspacing etc.

I'd want a figure in shoeshines/Gb, or Gb/shoeshine.
One shoeshine is probably something like a mark-and-backspace
caused by slow supply of an ongoing data stream.

I can't help feeling it's an important statistic. I know I'd love to
have it to have it, to properly motivate purchasing decisions...

Regards, Peter

AUS/TAS/DPIW/CIT/Servers hbt/lnd/l8   6233 3061   http://www.pjb.com.au
Pasari, pasarimosdice el aguay canta la verdad contra la piedra
 -- Pablo Neruda

Re: WinTel Bare Metal Restore

[Prather, Wanda]

Cool!
Thanks Stefan.



From: ADSM: Dist Stor Manager on behalf of Stefan Holzwarth
Sent: Tue 4/17/2007 4:23 PM
To: ADSM-L@VM.MARIST.EDU
Subject: AW: WinTel Bare Metal Restore



I can confirm for HP servers, that the ASR recovery process works also with HP 
usb floppy drives.
Regards Stefan Holzwarth

> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im
> Auftrag von Prather, Wanda
> Gesendet: Dienstag, 17. April 2007 21:38
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: WinTel Bare Metal Restore
>
> I believe someone posted to the list a long time ago that an
> external/portable USB-connected floppy will work.
> But I haven't personally done it.
>
> 
>
> From: ADSM: Dist Stor Manager on behalf of Len Boyle
> Sent: Mon 4/16/2007 10:30 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: WinTel Bare Metal Restore
>
>
>
> Wanda
>
> With ASR is there a work around for a client that does not
> have a floopy disk drive?
>
> len
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of Prather, Wanda
> Sent: Monday, April 16, 2007 10:20 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] WinTel Bare Metal Restore
>
> For XP and 2003, see the TSM Client Manual for Windows
> instructions for ASR (Automated System Recovery).
> It's a MIcrosoft thing which TSM supports.
> Works, if you follow the instructions exactly.
>
>
> 
>
> From: ADSM: Dist Stor Manager on behalf of Johnson, Milton
> Sent: Mon 4/16/2007 10:43 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: WinTel Bare Metal Restore
>
>
>
> Due to the lack of recent religious wars on this forum, I'm forced to
> ask:
>
> What is the best method to back-up and perform a reliable and
> successful Bare Metal Restore of a WinTel platform (Windows NT/Server
> 2000/2003/XP/etc.) using a TSM AIX server?  Methods requiring
> a third party solution are acceptable.  Solutions allowing a
> BMR to dis-similar hardware are preferable.
>
> Personally I view the need to do a BMR on a WinTel platform
> as an opportunity to bring up another AIX server, but that is
> yet another religious war.
>
> Thanks,
> Milton
>

Re: exclude error\ PrivIncrFileSpace: Received rc=104 from fioGetDirEntries

[Richard Sims]

On Apr 17, 2007, at 4:05 PM, Gary Osullivan wrote:


hi
Has anyone seen this error message when running incremental backups
on netware6.5 , TSM client 5.3.0.0

 "PrivIncrFileSpace: Received rc=104 from fioGetDirEntries:  SYS:  /
LTAUDIT"



Supposedly:
This is Novell NKS return value NX_ENONEXTANT - Object doesn't exist,
or POSIX/ANSI return value ENONEXTANT - Object doesn't exist.


I ' ve taken 3 cracks at it + still no luck.
( It is a directory containing security software that we do not
want to take in backup).

example of exclude statements that I have tried.

3rd try) EXCLUDE.DIR  servername\SYS:/LTAUDIT/.../*   mgmclass
2nd try)EXCLUDE  servername\SYS:/LTAUDIT/.../*
1st try) EXCLUDE  servername\SYS:/LTAUDIT/*


Refer to the client documentation when writing Excludes.
Simple Excludes still cause the directory to be entered and traversed,
so the first two tries are not what you would want.
The third try is erroneously coded.  You want to try:
   EXCLUDE.DIR  servername\SYS:/LTAUDIT
If that doesn't work, you may need to contact TSM Support.
But note that you are on a base release, with zero maintenance,
which is a bad idea.  I would get that client updated.

And always do   dsmc Query INCLexcl
after making changes in this area, to fully compile all
contributing sources and validate.

Richard Sims

Re: TSM on Windows Cluster

[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.
==

exclude error\ PrivIncrFileSpace: Received rc=104 from fioGetDirEntries

[Gary Osullivan]

hi 
Has anyone seen this error message when running incremental backups on 
netware6.5 , TSM client 5.3.0.0
 
 "PrivIncrFileSpace: Received rc=104 from fioGetDirEntries:  SYS:  /LTAUDIT"
 
I ' ve taken 3 cracks at it + still no luck.
( It is a directory containing security software that we do not want to take in 
backup).
 
example of exclude statements that I have tried.
 
3rd try) EXCLUDE.DIR  servername\SYS:/LTAUDIT/.../*   mgmclass
2nd try)EXCLUDE  servername\SYS:/LTAUDIT/.../*  
1st try) EXCLUDE  servername\SYS:/LTAUDIT/*
 
I checked on both  www.ibm.com  +  novell.com  ,   
nothing.
 
All the fun is running out of this one.
 
any idea,
Gary
 
 
 

 

 
 
 

AW: WinTel Bare Metal Restore

[Stefan Holzwarth]

I can confirm for HP servers, that the ASR recovery process works also with HP 
usb floppy drives.
Regards Stefan Holzwarth

> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im 
> Auftrag von Prather, Wanda
> Gesendet: Dienstag, 17. April 2007 21:38
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Re: WinTel Bare Metal Restore
> 
> I believe someone posted to the list a long time ago that an 
> external/portable USB-connected floppy will work.
> But I haven't personally done it.
> 
> 
> 
> From: ADSM: Dist Stor Manager on behalf of Len Boyle
> Sent: Mon 4/16/2007 10:30 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: WinTel Bare Metal Restore
> 
> 
> 
> Wanda
> 
> With ASR is there a work around for a client that does not 
> have a floopy disk drive?
> 
> len
> 
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] 
> On Behalf Of Prather, Wanda
> Sent: Monday, April 16, 2007 10:20 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] WinTel Bare Metal Restore
> 
> For XP and 2003, see the TSM Client Manual for Windows 
> instructions for ASR (Automated System Recovery).
> It's a MIcrosoft thing which TSM supports.
> Works, if you follow the instructions exactly.
> 
> 
> 
> 
> From: ADSM: Dist Stor Manager on behalf of Johnson, Milton
> Sent: Mon 4/16/2007 10:43 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: WinTel Bare Metal Restore
> 
> 
> 
> Due to the lack of recent religious wars on this forum, I'm forced to
> ask:
> 
> What is the best method to back-up and perform a reliable and 
> successful Bare Metal Restore of a WinTel platform (Windows NT/Server
> 2000/2003/XP/etc.) using a TSM AIX server?  Methods requiring 
> a third party solution are acceptable.  Solutions allowing a 
> BMR to dis-similar hardware are preferable.
> 
> Personally I view the need to do a BMR on a WinTel platform 
> as an opportunity to bring up another AIX server, but that is 
> yet another religious war.
> 
> Thanks,
> Milton
> 

Re: WinTel Bare Metal Restore

[Prather, Wanda]

I believe someone posted to the list a long time ago that an external/portable 
USB-connected floppy will work.
But I haven't personally done it.



From: ADSM: Dist Stor Manager on behalf of Len Boyle
Sent: Mon 4/16/2007 10:30 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: WinTel Bare Metal Restore



Wanda

With ASR is there a work around for a client that does not have a floopy disk 
drive?

len

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Prather, 
Wanda
Sent: Monday, April 16, 2007 10:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] WinTel Bare Metal Restore

For XP and 2003, see the TSM Client Manual for Windows instructions for ASR 
(Automated System Recovery).
It's a MIcrosoft thing which TSM supports.
Works, if you follow the instructions exactly.




From: ADSM: Dist Stor Manager on behalf of Johnson, Milton
Sent: Mon 4/16/2007 10:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: WinTel Bare Metal Restore



Due to the lack of recent religious wars on this forum, I'm forced to
ask:

What is the best method to back-up and perform a reliable and successful Bare 
Metal Restore of a WinTel platform (Windows NT/Server
2000/2003/XP/etc.) using a TSM AIX server?  Methods requiring a third party 
solution are acceptable.  Solutions allowing a BMR to dis-similar hardware are 
preferable.

Personally I view the need to do a BMR on a WinTel platform as an opportunity 
to bring up another AIX server, but that is yet another religious war.

Thanks,
Milton

FREE! April 19th Tivoli Storage Manager Ask the Experts Session on Recovery logs

[Darrius Plantz]

Ask the Experts Q&A session on Recovery logs.  This will be an Ask the Experts 
session where you can discuss with the L2 Support Engineers Tivoli Storage 
Manager Server Recovery Log topics such as:  Normal mode, Roll forward 
mode,Transactional processing,Managing recovery logs  The product experts will 
be: David Reedy, Mike Sisco, and John Wang
Go to the Support Technical Exchange site for connection details.
http://www.ibm.com/software/sysmgmt/products/support/supp_tech_exch.html
   
-
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.

Re: dsmerror.log & dsmsched.log gets too large

[Avy Wong]

Thank you fellas...(o:

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976






 Charles A Hart
 <[EMAIL PROTECTED]
 .COM>  To
 Sent by: "ADSM:   ADSM-L@VM.MARIST.EDU
 Dist Stor  cc
 Manager"
 <[EMAIL PROTECTED] Subject
 .EDU> Re: [ADSM-L] dsmerror.log &
   dsmsched.log gets too large

 04/17/2007 10:52
 AM


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






There's options you can use to limit number of days to keep for the sched
and error logs...


SCHEDLOGname  /path/dsmsched2.log
SCHEDLOGRetention 5
ERRORLOGname  /path/dsmerror2.log
ERRORLOGRetention 33


Charles Hart
UHT - Data Protection
(763)744-2263
Sharepoint:
http://unitedteams.uhc.com/uht/EnterpriseStorage/DataProtection/default.aspx





Henrik Wahlstedt <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
04/17/2007 09:38 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] dsmerror.log & dsmsched.log gets too large






Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and
delete
this message.
Thank you.



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.


**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**

Re: TSM on Windows Cluster

[William Boyer]

Appendix D of the TSM B/A client manual describes the steps necessary to 
configure TSM to backup cluster resources. I think you're
missing the step for the registry key replication.

Bill Boyer
"Law of Cybernetic Entomology - There is always another bug." - ??


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Fawad Baig
Sent: Tuesday, April 17, 2007 10:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: 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

Re: TSM on Windows Cluster

[Richard Sims]

You can also search at the TSM Support Page for terms:
  password windows cluster
That will yield informationful Technotes such as 1079760.

  Richard Sims

Re: TSM on Windows Cluster

[Greg Yuzik]

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

Re: dsmerror.log & dsmsched.log gets too large

[Charles A Hart]

There's options you can use to limit number of days to keep for the sched
and error logs...


SCHEDLOGname  /path/dsmsched2.log
SCHEDLOGRetention 5
ERRORLOGname  /path/dsmerror2.log
ERRORLOGRetention 33


Charles Hart
UHT - Data Protection
(763)744-2263
Sharepoint:
http://unitedteams.uhc.com/uht/EnterpriseStorage/DataProtection/default.aspx




Henrik Wahlstedt <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" 
04/17/2007 09:38 AM
Please respond to
"ADSM: Dist Stor Manager" 


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: [ADSM-L] dsmerror.log & dsmsched.log gets too large






Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of
the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and
delete
this message.
Thank you.



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.

Re: dsmerror.log & dsmsched.log gets too large

[Henrik Wahlstedt]

Hi,

There are some freeware you can use to split files, look at tucows.com.

However, you have the options to use Error- and Schedlogretention
together with Error- and Schedlogmax to control the log size.

Look in the client manual for more information.


Thanks
Henrik



-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: den 17 april 2007 16:05
To: ADSM-L@VM.MARIST.EDU
Subject: dsmerror.log & dsmsched.log gets too large

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files
when it says, " The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log
file is too large for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976



**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**


---
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

TSM on Windows Cluster

[Fawad Baig]

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

dsmerror.log & dsmsched.log gets too large

[Avy Wong]

Hello
  Is there a way to open the dsmerror.log and dsmsched.log files when
it says,
" The C:\Program Files\Tivoli\TSM\baclient\dsmerror.log file is too large
for Notepad. Use another editor to edit the file."
File is 779,624 KB.

I have tried wordpad, microsoft word, it does not open.  What is the
managable size before it gets too big?

Thanks,


Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
(860) 862-8164
cell (860) 961-6976


**
The information contained in this message may be privileged and confidential and
protected from disclosure. If the reader of this message is not the intended 
recipient, or
an employee or agent responsible for delivering this message to the intended 
recipient,
you are hereby notified that any dissemination, distribution, or copy of this
communication is strictly prohibited. If you have received this communication 
in error,
please notify us immediately by replying to the message and deleting it from 
your
computer.
**

Long running expire inventory

[Park, Rod]

I posted this before, not sure if it made it out there. I have a TSM
server version 5.3.3.1 on AIX with a 70GB database. I recently moved my
db/log vols from 500GB sata drives to internal drives along with
mirrored vols on separate internal drives on the aix box. My backups
went from 2 hours to 30 minutes, my startup went from about 2 hrs to
20-30 minutes, and I've seen other performance gains. Everything seems
better except for my "expire inventory" in went from running in a couple
of hours to several hours, and my current expiration has been running
since yesterday morning at 10:00 a.m.. Does anybody know why my "expire
inventory" run times would have gotten worse. I can't really tell from
the activity log. Any suggestions?


This has been running for almost 24 hours:

tsm: TSMCORP3>q pr

 Process Process Description  Status

  Number
 
-
   2,301 Expiration   Examined 1600 objects, deleting
1568 backup
   objects, 0 archive objects, 0 DB
backup volumes,
   0 recovery plan files; 0 errors
encountered.

This email and any files transmitted with it are confidential and intended 
solely for the use of the addressee. If you are not the intended addressee, 
then you have received this email in error and any use, dissemination, 
forwarding, printing, or copying of this email is strictly prohibited. Please 
notify us immediately of your unintended receipt by reply and then delete this 
email and your reply. Tyson Foods, Inc. and its subsidiaries and affiliates 
will not be held liable to any person resulting from the unintended or 
unauthorized use of any information contained in this email or as a result of 
any additions or deletions of information originally contained in this email.

Fw: Long running expire inventory

[Nicholas Cassimatis]

Your startup time was 2 hours, and is now only 30 minutes?  I've had MUCH
bigger databases that come back from a crash, with a nearly full log,
faster than that.  Combined with the poor performance on expiration, I'd
guess you have some corruption in the database, or something wrong on the
system.  Have you measured CPU utilization, disk IO, memory usage?  Is
something there at 100%?

I did use the words "database corruption," which, to me, means "Call TSM
Support."  While there's great knowledge on the list about the analysis and
recovery tools, you want to get it from TSM Support.

Nick Cassimatis

- Forwarded by Nicholas Cassimatis/Raleigh/IBM on 04/17/2007 08:51 AM
-

"ADSM: Dist Stor Manager"  wrote on 04/17/2007
08:21:02 AM:

> I posted this before, not sure if it made it out there. I have a TSM
> server version 5.3.3.1 on AIX with a 70GB database. I recently moved my
> db/log vols from 500GB sata drives to internal drives along with
> mirrored vols on separate internal drives on the aix box. My backups
> went from 2 hours to 30 minutes, my startup went from about 2 hrs to
> 20-30 minutes, and I've seen other performance gains. Everything seems
> better except for my "expire inventory" in went from running in a couple
> of hours to several hours, and my current expiration has been running
> since yesterday morning at 10:00 a.m.. Does anybody know why my "expire
> inventory" run times would have gotten worse. I can't really tell from
> the activity log. Any suggestions?
>
>
> This has been running for almost 24 hours:
>
> tsm: TSMCORP3>q pr
>
>  Process Process Description  Status
>
>   Number
>  
> -
>2,301 Expiration   Examined 1600 objects, deleting
> 1568 backup
>objects, 0 archive objects, 0 DB
> backup volumes,
>0 recovery plan files; 0 errors
> encountered.
>
> This email and any files transmitted with it are confidential and
> intended solely for the use of the addressee. If you are not the
> intended addressee, then you have received this email in error and
> any use, dissemination, forwarding, printing, or copying of this
> email is strictly prohibited. Please notify us immediately of your
> unintended receipt by reply and then delete this email and your
> reply. Tyson Foods, Inc. and its subsidiaries and affiliates will
> not be held liable to any person resulting from the unintended or
> unauthorized use of any information contained in this email or as a
> result of any additions or deletions of information originally
> contained in this email.

tivguid question

[Dirk Kastens]

Hi,

I found two nodes with the same globally unique ID (GUID), because the
client admin changed the IP addresses of the machines. Reading the
manuals and the ADSM Quick Facts I came across the tivguid command. But
I cannot find the command on any of my client nodes (Linux, Windows,
versions 5.3 and 5.4).
The Unix client manual also states that the GUID is stored in the
directory /etc/tivoli. That's wrong, because it is stored in the file
/etc/TIVGUID.

Where can I find the tivguid command on the client nodes?

--
Viele Gruesse,

Dirk Kastens
Universitaet Osnabrueck, Rechenzentrum (Computer Center)
Albrechtstr. 28, 49069 Osnabrueck, Germany
Tel.: +49-541-969-2347, FAX: -2470