authentication with passwordaccess set to generate

2002-05-27 Thread Herbert L|cke

Hi all,

i'm running an OS390/Unix System Services BA Client (TSM 4.2.0). The
paswordaccess-option in the dsm.sys-file is set to 'generate'.
I've changed the password for the USS BA client using 'update node' and
restarted the client-scheduler.
Since that time, the authentication with the server fails.
I don't know the generated old password because it's encrypted in the
tsm.pwd-file.
Is there a way to retrieve the old password from the tsm.pwd-file or what
else can I do?


Thanks a lot,

Herbert



Re: big data pool volumes

2002-05-27 Thread Michael Benjamin

Perform an errpt -a -j21F54B38 and provide more information regarding the
disk errors, are they TEMP or PERM errors?

It shows up at: http://www-aix.gsi.de/~hocks/aix.errpt.codes.html as a
permanent disk error, which is not good. A bad block
relocation is regarded as a TEMP error.

21F54B38 DISK_ERR1 PERM H DISK OPERATION ERROR

It's possible you have a failing drive and this is affecting the TSM
database? Without more information this is speculative...

I would ensure I had a current dbbackup, and consider relocating the
database to another set of disks; if you
are in fact having drive errors, you risk TSM database corruption.


> -Original Message-
> From: Burak Demircan [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, May 27, 2002 12:53 PM
> To:   [EMAIL PROTECTED]
> Subject:  big data pool volumes
>
> Hi,
> Last friday I created a large file enable journaled file system on AIX
> 4.3.3
> and put a
> 10 gb single file on it. It was my backup disk pool volume. But I recieved
>
> following messages on
> TSM and AIX. Any idea?
>
>
> Actlong from TSM 4.2.2.0
>
> 24-05-2002 21:22:38  ANRD dsrtrv.c(538): ThreadId<62> Error on volume
>   /tsmpoolfs/nomirrordata1.dsm: execRc=-1,
> summaryRc=-1.
> 24-05-2002 22:05:28  ANRD blkdisk.c(1496): ThreadId<41> Error -1
> reading
>   from disk /tsmpoolfs/nomirrordata1.dsm, errno=5
> (There is
>   an input or output error.).
>
>
>
> errpt from AIX 4.3.3.0_09ML
>
21F54B38   0525000902 P H hdisk2 DISK OPERATION ERROR
> 21F54B38   0525000902 P H hdisk2 DISK OPERATION ERROR
> 21F54B38   0525000902 P H hdisk2 DISK OPERATION ERROR

**
Bunnings Legal Disclaimer:

1)  This document is confidential and may contain legally privileged
information. If you are not the intended recipient you must not
read, copy, distribute or act in reliance on it.
If you have received this document in error, please telephone
us immediately on (08) 9365-1555.

2)  All e-mails sent to and sent from Bunnings Building Supplies are
scanned for content. Any material deemed to contain inappropriate
subject matter will be reported to the e-mail administrator of
all parties concerned.

**



Re: NT Script to check for failed backups

2002-05-27 Thread Regelin Michael (CHA)

Hi Jean-Baptiste,

I'm really interested in your script. We are backuping about 50 NT servers
and our only procedures is to catch information manually from the TSM
server.

However, we are soon applying a check within the TSM server that will show
us if the backup failed or succeed.

But i'm very interested in your solution. Could it be possible to look at
the scripts.

Thank's

Mike

-Message d'origine-
De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
Envoyé : samedi, 25. mai 2002 20:17
À : [EMAIL PROTECTED]
Objet : Re: NT Script to check for failed backups


Hello,


use WSH 5.6 and with the RUN method execute the dsmc command
to backup your data. Result of the execution will be 0 if everything
ok and >0 if an error did occur. That way it will be possible to
send you a mail. If you're interested in the scripts write me back.

Regards,
--Jean-Baptiste




>From: Justin Black <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: NT Script to check for failed backups
>Date: Thu, 23 May 2002 17:02:37 -0400
>
>I am looking for an automated method to check for failed TSM and TDP
>backups on an NT machine. We kick off different backups (using the TSM
>scheduler and NT Services) on different machines on a daily basis and are
>unable to manually verify (due to time constraints) that these are all
>successful. We have noticed when failure occurs during a TSM backup of a
>particular file, it is written to the NT EventLog. On our Unix platform, we
>are able to do this and email messages are sent out when a failure occurs.
>Any ideas how this can be accomplished on NT?
>
>Justin Black




_
Send and receive Hotmail on your mobile device: http://mobile.msn.com



Re: authentication with passwordaccess set to generate

2002-05-27 Thread Claudia Mºller

you changed the password on the server but the client still only knows the
password in his encrypted local file.
You have to login 1 time on the client and type in the new password - the one
you typed using update node.

ciao, Claudia

-Original Message-
From: HerbertLuecke [mailto:[EMAIL PROTECTED]]
Sent: Montag, 27. Mai 2002 09:13
To: ADSM-L
Cc: HerbertLuecke
Subject: authentication with passwordaccess set to generate


Hi all,

i'm running an OS390/Unix System Services BA Client (TSM 4.2.0). The
paswordaccess-option in the dsm.sys-file is set to 'generate'.
I've changed the password for the USS BA client using 'update node' and
restarted the client-scheduler.
Since that time, the authentication with the server fails.
I don't know the generated old password because it's encrypted in the
tsm.pwd-file.
Is there a way to retrieve the old password from the tsm.pwd-file or what
else can I do?


Thanks a lot,

Herbert



WinClient 5.1.0.1 GetDfsInfo()

2002-05-27 Thread Gerhard Ginzler

Hello,

After installing TSM client 5.1.0.1 (win2000) the error log fills with:

GetDfsInfo(): EntryPath=\\xyz\volumes\MEDIA_5\LostAndFound, Server=(null),
Share=(null)
NetDfsGetInfo() returns RC=5.
GetDfsInfo(): EntryPath=\\cd2.cc.akh-wien.ac.at\volumes\MEDIA_4\tools\Bugs,
Server=(null), Share=(null)
NetDfsGetInfo() returns RC=5.
...

'xyz' is a network storage server for sharing hard disks (AXIS StorPoint NAS
100). Where can I find more information about these messages?

Any ideas, any help?

Regards,
Gerhard Ginzler



Backup retention period

2002-05-27 Thread Ruksana Siddiqui

Hi,

I just started working with TSM but can someone tell me how can I find the
retention period of the backup I have done.

I have done a particular backup and wanted to have it for atleast 3 months -
is there anyway I tell TSM to hold it for 3 months or can I actually check
how long TSM was configured to hold the data.

Any help is highly appreciated.

With regards,
Ruksana Siddiqui



CAUTION - This message may contain privileged and confidential information intended 
only for the use of the addressee named above. If you are not the intended recipient 
of this message you are hereby notified that any use, dissemination, distribution or 
reproduction of this message is prohibited. If you have received this message in error 
please notify AMCOR immediately. Any views expressed in this message are those of the 
individual sender and may not necessarily reflect the views of AMCOR.



Re: Backup retention period

2002-05-27 Thread Zlatko Krastev

The backup would stay there undefinitely if the content does not change.
If it changes and a new backup is performed the copy you've just becomes
obsolete and according to copygroup settings will expire some day. To
ensure it would not be before three months have passed set
VEREXIST=NOLimit and RETExtra=92.
To become familiar with TSM (which is more evolved than competitive
products) I highly recommend you to have a look at nice redbook "Tivoli
Storage Management Concepts" - SG24-4877-02
(http://www.redbooks.ibm.com/). This would save you many headaches.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Backup retention period

Hi,

I just started working with TSM but can someone tell me how can I find the
retention period of the backup I have done.

I have done a particular backup and wanted to have it for atleast 3 months
-
is there anyway I tell TSM to hold it for 3 months or can I actually check
how long TSM was configured to hold the data.

Any help is highly appreciated.

With regards,
Ruksana Siddiqui



CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of AMCOR.



Estimated Capacity

2002-05-27 Thread Wolfgang Herkenrath

Hi *SM'ers,

I have one Question about the estimated capacity for deviceclass definition.

TSM V4 R1 on OS390 2.8  with 3494 tapelibrary and 3590 Magstar Cartridge.

As far as I know the normal capacity of one 3590 Magstar cratridge is 10 GB. With 
compaction the capacity is 30 GB.
The compaction for the dataclas wich manages my magstar tapes is activated.

At my device-class wich belong to this cartridges I have the estimated capacity set to 
9 GB.

So, if I think about these setting I belief that I don't use the full capacity of my 
tapes.

Before I set the estimated capacity to 27 GB: Are there any expiriences about the real 
compaction of data on tape? To wich value I can set the estimated cpacity without 
runnign into trouble?

TIA
Wolfgang 



Moving tape(s) from a library to other one

2002-05-27 Thread Krzysztof Kus

Hi!

 Is it possible to move one tape (or subset of stg) from one library
to other one (with the same kind of drives)? I'm trying to imagine how
to restore particular node data in any case of library outage.

Since now I've found out that I can check out all tapes from the stg,
update devclass to point to the second library and check the tapes into
the second library.

Will it work? What will happen if the first library is not accessible
any more?

--

--== KKus ==--



Re: NT Script to check for failed backups

2002-05-27 Thread Jean-Baptiste Nothomb

Hi Michael,

hereby included you'll find the VBscripts that we're using
for doing TSM backups. Note that if you think to use them
you'll have to install WSH 5.6.

Regards,
--Jean-Baptiste

--- TSMbck_incr_NTPDC.wsf 



  dim FSO, LOGFILE, WSHSHELL
  dim ENVIR, APPDRIVE, APPEXE,APPFIL,APPLOG,APPDAT,APPLIC
  dim THOUR, TDAY
  const ForReading = 1, ForWriting = 2, ForAppending = 8

  APPDRIVE = "C:\"
  ENVIR  = "PROD"
  APPLIC = "tsm"
  APPEXE = APPDRIVE & ENVIR & "\" & APPLIC & "\exe\"
  APPFIL = APPDRIVE & ENVIR & "\" & APPLIC & "\fil\"
  APPLOG = APPDRIVE & ENVIR & "\" & APPLIC & "\log\"
  APPDAT = APPDRIVE & ENVIR & "\" & APPLIC & "\dat\"
  APPTMP = APPDRIVE & ENVIR & "\" & APPLIC & "\tmp\"

  SCP_FNAME = wscript.scriptfullname
  SCP_NAME = BaseName( SCP_FNAME )
  THOUR = replace ( time , ":" , "" )
  TDAY = replace ( date , "/" , "" )
  set FSO = createobject("scripting.filesystemobject")
  set WSHSHELL = wscript.createobject("wscript.shell")
  set LOGFILE = FSO.createtextfile( APPLOG & SCP_NAME & "_" & TDAY & THOUR &
".txt", true)
  LOGFILE.writeline("Script " & SCP_NAME & " started on: " & date & " " &
time)
  LOGFILE.writeline("")

  REM

  REM --- Start of script job. Put your commands below...
  REM


  Do_Backup

  sub Do_Backup()
dim TSMDIR,TSMEXE,TSMOPT,TSMCMD

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMEXE="""c:\program files\tivoli\tsm\baclient\dsmc.exe"""
TSMOPT="-id=x -password=x"
TSMCMD="incr"

RC=WSHSHELL.run(TSMEXE & " " & TSMOPT & " " & TSMCMD,0,true)
if RC<>0 then
  LOGFILE.writeline( SCP_NAME & ": ERROR --- dsmc.exe exited with RC=" &
RC & ". ---")
else
  LOGFILE.writeline( SCP_NAME & ": INFO  --- dsmc.exe exited with RC=" &
RC & ". ---")
end if
  end sub

  REM

  REM --- End of script job.
  REM


  LOGFILE.writeline("")
  LOGFILE.writeline("Script " & SCP_NAME & " ended on: " & date & " " &
time)


--end TSMbck_incr_NTPDC 


 Basename.vbs --
function BASENAME(FNAME)
  dim FSO
  set FSO = createobject("scripting.filesystemobject")
  BASENAME = FSO.getbasename(FNAME)
end function
-- end basename.vbs 

>From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: NT Script to check for failed backups
>Date: Mon, 27 May 2002 08:44:58 +0200
>
>Hi Jean-Baptiste,
>
>I'm really interested in your script. We are backuping about 50 NT servers
>and our only procedures is to catch information manually from the TSM
>server.
>
>However, we are soon applying a check within the TSM server that will show
>us if the backup failed or succeed.
>
>But i'm very interested in your solution. Could it be possible to look at
>the scripts.
>
>Thank's
>
>Mike
>
>-Message d'origine-
>De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
>Envoyi : samedi, 25. mai 2002 20:17
>@ : [EMAIL PROTECTED]
>Objet : Re: NT Script to check for failed backups
>
>
>Hello,
>
>
>use WSH 5.6 and with the RUN method execute the dsmc command
>to backup your data. Result of the execution will be 0 if everything
>ok and >0 if an error did occur. That way it will be possible to
>send you a mail. If you're interested in the scripts write me back.
>
>Regards,
>--Jean-Baptiste
>
>
>
>
> >From: Justin Black <[EMAIL PROTECTED]>
> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: NT Script to check for failed backups
> >Date: Thu, 23 May 2002 17:02:37 -0400
> >
> >I am looking for an automated method to check for failed TSM and TDP
> >backups on an NT machine. We kick off different backups (using the TSM
> >scheduler and NT Services) on different machines on a daily basis and are
> >unable to manually verify (due to time constraints) that these are all
> >successful. We have noticed when failure occurs during a TSM backup of a
> >particular file, it is written to the NT EventLog. On our Unix platform,
>we
> >are able to do this and email messages are sent out when a failure
>occurs.
> >Any ideas how this can be accomplished on NT?
> >
> >Justin Black
>
>
>
>
>_
>Send and receive Hotmail on your mobile device: http://mobile.msn.com


_
Join the world s largest e-mail service with MSN Hotmail.
http://

TSM Server -to backup in round robin fashion----------------HELP REQUIRED!!!!

2002-05-27 Thread Prashant R Gadikar

Hi ,

We have a scenario where in there are 10 servers (TSM Clients) need to do
the backup, we don't want to run schedules as there is no consistency in
the data each server is backing up everyday. To explain e.g. server A on
day one have 50 GB to backup and next day it might not have anything to
backup,in this scenario server B should start the backup immediately if
Server B has nothing to backup then Server C and so on.
Best Regards
Prashant Gadikar
IBM Software -Tivoli Storage Management
IBM India Ltd, Level II, Subhramanya Arcade
12,Bennarghatta Main Road, Bangalore-560029
Tel:Direct: 91-80-2063216, 91-80-6787202 Extn: 3216
Mobile: +91-9845123155, E-mail:[EMAIL PROTECTED]



Re: NT Script to check for failed backups

2002-05-27 Thread Jean-Baptiste Nothomb

Hi Michael,

hereby included you'll find the VBscripts that we're using
for doing TSM backups. Note that if you think to use them
you'll have to install WSH 5.6.

Regards,
--Jean-Baptiste

--- TSMbck_incr_NTPDC.wsf 



  dim FSO, LOGFILE, WSHSHELL
  dim ENVIR, APPDRIVE, APPEXE,APPFIL,APPLOG,APPDAT,APPLIC
  dim THOUR, TDAY
  const ForReading = 1, ForWriting = 2, ForAppending = 8

  APPDRIVE = "C:\"
  ENVIR  = "PROD"
  APPLIC = "tsm"
  APPEXE = APPDRIVE & ENVIR & "\" & APPLIC & "\exe\"
  APPFIL = APPDRIVE & ENVIR & "\" & APPLIC & "\fil\"
  APPLOG = APPDRIVE & ENVIR & "\" & APPLIC & "\log\"
  APPDAT = APPDRIVE & ENVIR & "\" & APPLIC & "\dat\"
  APPTMP = APPDRIVE & ENVIR & "\" & APPLIC & "\tmp\"

  SCP_FNAME = wscript.scriptfullname
  SCP_NAME = BaseName( SCP_FNAME )
  THOUR = replace ( time , ":" , "" )
  TDAY = replace ( date , "/" , "" )
  set FSO = createobject("scripting.filesystemobject")
  set WSHSHELL = wscript.createobject("wscript.shell")
  set LOGFILE = FSO.createtextfile( APPLOG & SCP_NAME & "_" & TDAY & THOUR &
".txt", true)
  LOGFILE.writeline("Script " & SCP_NAME & " started on: " & date & " " &
time)
  LOGFILE.writeline("")

  REM

  REM --- Start of script job. Put your commands below...
  REM


  Do_Backup

  sub Do_Backup()
dim TSMDIR,TSMEXE,TSMOPT,TSMCMD

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMEXE="""c:\program files\tivoli\tsm\baclient\dsmc.exe"""
TSMOPT="-id=x -password=x"
TSMCMD="incr"

RC=WSHSHELL.run(TSMEXE & " " & TSMOPT & " " & TSMCMD,0,true)
if RC<>0 then
  LOGFILE.writeline( SCP_NAME & ": ERROR --- dsmc.exe exited with RC=" &
RC & ". ---")
else
  LOGFILE.writeline( SCP_NAME & ": INFO  --- dsmc.exe exited with RC=" &
RC & ". ---")
end if
  end sub

  REM

  REM --- End of script job.
  REM


  LOGFILE.writeline("")
  LOGFILE.writeline("Script " & SCP_NAME & " ended on: " & date & " " &
time)


--end TSMbck_incr_NTPDC 


 Basename.vbs --
function BASENAME(FNAME)
  dim FSO
  set FSO = createobject("scripting.filesystemobject")
  BASENAME = FSO.getbasename(FNAME)
end function
-- end basename.vbs 



>From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: NT Script to check for failed backups
>Date: Mon, 27 May 2002 08:44:58 +0200
>
>Hi Jean-Baptiste,
>
>I'm really interested in your script. We are backuping about 50 NT servers
>and our only procedures is to catch information manually from the TSM
>server.
>
>However, we are soon applying a check within the TSM server that will show
>us if the backup failed or succeed.
>
>But i'm very interested in your solution. Could it be possible to look at
>the scripts.
>
>Thank's
>
>Mike
>
>-Message d'origine-
>De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
>Envoyi : samedi, 25. mai 2002 20:17
>@ : [EMAIL PROTECTED]
>Objet : Re: NT Script to check for failed backups
>
>
>Hello,
>
>
>use WSH 5.6 and with the RUN method execute the dsmc command
>to backup your data. Result of the execution will be 0 if everything
>ok and >0 if an error did occur. That way it will be possible to
>send you a mail. If you're interested in the scripts write me back.
>
>Regards,
>--Jean-Baptiste
>
>
>
>
> >From: Justin Black <[EMAIL PROTECTED]>
> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: NT Script to check for failed backups
> >Date: Thu, 23 May 2002 17:02:37 -0400
> >
> >I am looking for an automated method to check for failed TSM and TDP
> >backups on an NT machine. We kick off different backups (using the TSM
> >scheduler and NT Services) on different machines on a daily basis and are
> >unable to manually verify (due to time constraints) that these are all
> >successful. We have noticed when failure occurs during a TSM backup of a
> >particular file, it is written to the NT EventLog. On our Unix platform,
>we
> >are able to do this and email messages are sent out when a failure
>occurs.
> >Any ideas how this can be accomplished on NT?
> >
> >Justin Black
>
>
>
>
>_
>Send and receive Hotmail on your mobile device: http://mobile.msn.com


_
Get your FREE download of MSN Explorer at http://explorer.msn.c

IE Explorer for TSM Admin: Event window is horizontally too small

2002-05-27 Thread Ken Sedlacek

I am using IE 5.5 (128-bit) for TSM administration on a Win2K wrkstn.

My event window is not horizontally long enough to see the event messages.

I am using the smallest text type.

How can I get the event window to expand to see the whole event message
length??


ps-on my WinNT 4 wrkstn, the event window would expand to see most of the
event message length!



Ken Sedlacek
AIX/TSM/UNIX Administrator
[EMAIL PROTECTED]

IBM Certified Specialist: RS/6000 AIX v4.3 Support
IBM Certified Specialist: RS/6000 SP & PSSP 3
Tivoli Certified Consultant - Tivoli Storage Manager v4.1



Multiple filespaces for one disk volume

2002-05-27 Thread Tomáš Hrouda

Hi all,

due to some imports of archive and backup data I have now three filespaces
for one volume at one of my nodes, for example:
\\node\e$... this is original filespace
\\node\e1... these two FS comes with imnports of E:\ data
\\node\e2...

Question: is any way to join these three filespaces to one \\node\e$ ? All
three filespaces are seen through BAclient GUI and it looks a little
disruptive.
Any idea?

Thanks, Tom



Linux Backup

2002-05-27 Thread Crawford, Lindy

Good Day,

Please help me...How can I do a backup of say 2 filesystems (but you want to
specify these two filesystems when you do the backup) on Linux from the dsmc
command line

What command can one use


> Lindy Crawford
> Business Solutions: IT
> BoE Corporate
>
> * +27-31-3642185
> +27-31-3642946
 [EMAIL PROTECTED] 




WARNING:
Any unauthorised use or interception of this email is illegal. If this email
is not intended for you, you may not copy, distribute nor disclose the
contents to anyone. Save for bona fide company matters, the BoE Group does
not accept any responsibility for the opinions expressed in this email.
For further details please see: http://www.nbs.co.za/emaildisclaim.htm



Re: NT scripts to check if backup failed

2002-05-27 Thread Jean-Baptiste Nothomb

Hi Michael,

hereby included you'll find the VBscripts that we're using
for doing TSM backups. Note that if you think to use them
you'll have to install WSH 5.6.

Regards,
--Jean-Baptiste

--- TSMbck_incr_NTPDC.wsf 



  dim FSO, LOGFILE, WSHSHELL
  dim ENVIR, APPDRIVE, APPEXE,APPFIL,APPLOG,APPDAT,APPLIC
  dim THOUR, TDAY
  const ForReading = 1, ForWriting = 2, ForAppending = 8

  APPDRIVE = "C:\"
  ENVIR  = "PROD"
  APPLIC = "tsm"
  APPEXE = APPDRIVE & ENVIR & "\" & APPLIC & "\exe\"
  APPFIL = APPDRIVE & ENVIR & "\" & APPLIC & "\fil\"
  APPLOG = APPDRIVE & ENVIR & "\" & APPLIC & "\log\"
  APPDAT = APPDRIVE & ENVIR & "\" & APPLIC & "\dat\"
  APPTMP = APPDRIVE & ENVIR & "\" & APPLIC & "\tmp\"

  SCP_FNAME = wscript.scriptfullname
  SCP_NAME = BaseName( SCP_FNAME )
  THOUR = replace ( time , ":" , "" )
  TDAY = replace ( date , "/" , "" )
  set FSO = createobject("scripting.filesystemobject")
  set WSHSHELL = wscript.createobject("wscript.shell")
  set LOGFILE = FSO.createtextfile( APPLOG & SCP_NAME & "_" & TDAY & THOUR &
".txt", true)
  LOGFILE.writeline("Script " & SCP_NAME & " started on: " & date & " " &
time)
  LOGFILE.writeline("")

  REM

  REM --- Start of script job. Put your commands below...
  REM


  Do_Backup

  sub Do_Backup()
dim TSMDIR,TSMEXE,TSMOPT,TSMCMD

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMEXE="""c:\program files\tivoli\tsm\baclient\dsmc.exe"""
TSMOPT="-id=x -password=x"
TSMCMD="incr"

RC=WSHSHELL.run(TSMEXE & " " & TSMOPT & " " & TSMCMD,0,true)
if RC<>0 then
  LOGFILE.writeline( SCP_NAME & ": ERROR --- dsmc.exe exited with RC=" &
RC & ". ---")
else
  LOGFILE.writeline( SCP_NAME & ": INFO  --- dsmc.exe exited with RC=" &
RC & ". ---")
end if
  end sub

  REM

  REM --- End of script job.
  REM


  LOGFILE.writeline("")
  LOGFILE.writeline("Script " & SCP_NAME & " ended on: " & date & " " &
time)


--end TSMbck_incr_NTPDC 


 Basename.vbs --
function BASENAME(FNAME)
  dim FSO
  set FSO = createobject("scripting.filesystemobject")
  BASENAME = FSO.getbasename(FNAME)
end function
-- end basename.vbs 


_
Join the world s largest e-mail service with MSN Hotmail.
http://www.hotmail.com



Re: NT Script to check for failed backups

2002-05-27 Thread Jean-Baptiste Nothomb

Hi Michael,

hereby included you'll find the VBscripts that we're using
for doing TSM backups. Note that if you think to use them
you'll have to install WSH 5.6.

Regards,
--Jean-Baptiste

--- TSMbck_incr_NTPDC.wsf 



  dim FSO, LOGFILE, WSHSHELL
  dim ENVIR, APPDRIVE, APPEXE,APPFIL,APPLOG,APPDAT,APPLIC
  dim THOUR, TDAY
  const ForReading = 1, ForWriting = 2, ForAppending = 8

  APPDRIVE = "C:\"
  ENVIR  = "PROD"
  APPLIC = "tsm"
  APPEXE = APPDRIVE & ENVIR & "\" & APPLIC & "\exe\"
  APPFIL = APPDRIVE & ENVIR & "\" & APPLIC & "\fil\"
  APPLOG = APPDRIVE & ENVIR & "\" & APPLIC & "\log\"
  APPDAT = APPDRIVE & ENVIR & "\" & APPLIC & "\dat\"
  APPTMP = APPDRIVE & ENVIR & "\" & APPLIC & "\tmp\"

  SCP_FNAME = wscript.scriptfullname
  SCP_NAME = BaseName( SCP_FNAME )
  THOUR = replace ( time , ":" , "" )
  TDAY = replace ( date , "/" , "" )
  set FSO = createobject("scripting.filesystemobject")
  set WSHSHELL = wscript.createobject("wscript.shell")
  set LOGFILE = FSO.createtextfile( APPLOG & SCP_NAME & "_" & TDAY & THOUR &
".txt", true)
  LOGFILE.writeline("Script " & SCP_NAME & " started on: " & date & " " &
time)
  LOGFILE.writeline("")

  REM

  REM --- Start of script job. Put your commands below...
  REM


  Do_Backup

  sub Do_Backup()
dim TSMDIR,TSMEXE,TSMOPT,TSMCMD

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMDIR="c:\program files\tivoli\tsm\baclient"
WSHSHELL.currentdirectory=TSMDIR

TSMEXE="""c:\program files\tivoli\tsm\baclient\dsmc.exe"""
TSMOPT="-id=x -password=x"
TSMCMD="incr"

RC=WSHSHELL.run(TSMEXE & " " & TSMOPT & " " & TSMCMD,0,true)
if RC<>0 then
  LOGFILE.writeline( SCP_NAME & ": ERROR --- dsmc.exe exited with RC=" &
RC & ". ---")
else
  LOGFILE.writeline( SCP_NAME & ": INFO  --- dsmc.exe exited with RC=" &
RC & ". ---")
end if
  end sub

  REM

  REM --- End of script job.
  REM


  LOGFILE.writeline("")
  LOGFILE.writeline("Script " & SCP_NAME & " ended on: " & date & " " &
time)


--end TSMbck_incr_NTPDC 


 Basename.vbs --
function BASENAME(FNAME)
  dim FSO
  set FSO = createobject("scripting.filesystemobject")
  BASENAME = FSO.getbasename(FNAME)
end function
-- end basename.vbs 

>From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: NT Script to check for failed backups
>Date: Mon, 27 May 2002 08:44:58 +0200
>
>Hi Jean-Baptiste,
>
>I'm really interested in your script. We are backuping about 50 NT servers
>and our only procedures is to catch information manually from the TSM
>server.
>
>However, we are soon applying a check within the TSM server that will show
>us if the backup failed or succeed.
>
>But i'm very interested in your solution. Could it be possible to look at
>the scripts.
>
>Thank's
>
>Mike
>
>-Message d'origine-
>De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
>Envoyi : samedi, 25. mai 2002 20:17
>@ : [EMAIL PROTECTED]
>Objet : Re: NT Script to check for failed backups
>
>
>Hello,
>
>
>use WSH 5.6 and with the RUN method execute the dsmc command
>to backup your data. Result of the execution will be 0 if everything
>ok and >0 if an error did occur. That way it will be possible to
>send you a mail. If you're interested in the scripts write me back.
>
>Regards,
>--Jean-Baptiste
>
>
>
>
> >From: Justin Black <[EMAIL PROTECTED]>
> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: NT Script to check for failed backups
> >Date: Thu, 23 May 2002 17:02:37 -0400
> >
> >I am looking for an automated method to check for failed TSM and TDP
> >backups on an NT machine. We kick off different backups (using the TSM
> >scheduler and NT Services) on different machines on a daily basis and are
> >unable to manually verify (due to time constraints) that these are all
> >successful. We have noticed when failure occurs during a TSM backup of a
> >particular file, it is written to the NT EventLog. On our Unix platform,
>we
> >are able to do this and email messages are sent out when a failure
>occurs.
> >Any ideas how this can be accomplished on NT?
> >
> >Justin Black
>
>
>
>
>_
>Send and receive Hotmail on your mobile device: http://mobile.msn.com


_
MSN Photos is the easiest way to share and print your photos:
htt

Parm field length for for

2002-05-27 Thread Sam Sheppard

 Top of message 
>>--> 05-27-02  07:23  S.SHEPPARD (SHS)Parm field length for for

Put the list in two files and use the following:

// PARM='/LOADFORMAT 8 FILE:''ADSM.LOGLIST'' 5 FILE:''ADSM.DBLIST'''

Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
---`


 Top of message 
>>--> 05-25-02  14:49  ..NETMAIL (001) Parm field length for for
Date: Sat, 25 May 2002 23:03:35 +0200
From: "Bo Nielsen" <[EMAIL PROTECTED]>
Subject: Parm field length for format command
To: [EMAIL PROTECTED]
_Top_of_Message_

Hi,

I hope someone can help me.

I have unloaded my DB on a OS/390 server vers. 4.1.5, and now I try to
initialize the  volumes,
but I get the message:

2 IEF642I EXCESSIVE PARAMETER LENGTH IN THE PARM FIELD

My PARM field look like:
PARM=('/LOADFORMAT 2 XSYS.ADSMVSAM.RLOG1 XSYS.ADSMVSAM.RLOG 3',
' XSYS.ADSMVSAM.DB5 XSYS.ADSMVSAM.DB1 XSYS.ADSMVSAM.DB')

And now I can't restore the DB, because I have format one log and db vol.


> Regards
> Bo Nielsen
>   * 43 86 46 71
> COOP data  * (Internt postcenter): 6230
> IT-Driftscenter  * [EMAIL PROTECTED]
>
If you don't have the time to do it right the first time, where will you
find the time to do it again?

---`



Re: Linux Backup

2002-05-27 Thread Alexander Verkooijen

"Crawford, Lindy" wrote:

> Good Day,
>
> Please help me...How can I do a backup of say 2 filesystems (but you want to
> specify these two filesystems when you do the backup) on Linux from the dsmc
> command line
>
> What command can one use

For an incremental backup use:

dsmc incremental /filesystem1 /filesystem2

Regards,

Alexander
--
---
Alexander Verkooijen([EMAIL PROTECTED])
Senior Systems Programmer
SARA High Performance Computing



trace manual backup

2002-05-27 Thread Diciommo Fabio EDS

I would like to know if manuals backup ( only with GUI  ) on NT/2000 servers
can trace a log file.


Thanks to all

fdc



Re: NT Script to check for failed backups

2002-05-27 Thread Jean-Baptiste Nothomb

>From: "Regelin Michael (CHA)" <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: NT Script to check for failed backups
>Date: Mon, 27 May 2002 08:44:58 +0200
>
>Hi Jean-Baptiste,
>
>I'm really interested in your script. We are backuping about 50 NT servers
>and our only procedures is to catch information manually from the TSM
>server.
>
>However, we are soon applying a check within the TSM server that will show
>us if the backup failed or succeed.
>
>But i'm very interested in your solution. Could it be possible to look at
>the scripts.
>
>Thank's
>
>Mike
>
>-Message d'origine-
>De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
>Envoyi : samedi, 25. mai 2002 20:17
>@ : [EMAIL PROTECTED]
>Objet : Re: NT Script to check for failed backups
>
>
>Hello,
>
>
>use WSH 5.6 and with the RUN method execute the dsmc command
>to backup your data. Result of the execution will be 0 if everything
>ok and >0 if an error did occur. That way it will be possible to
>send you a mail. If you're interested in the scripts write me back.
>
>Regards,
>--Jean-Baptiste
>
>
>
>
> >From: Justin Black <[EMAIL PROTECTED]>
> >Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
> >To: [EMAIL PROTECTED]
> >Subject: NT Script to check for failed backups
> >Date: Thu, 23 May 2002 17:02:37 -0400
> >
> >I am looking for an automated method to check for failed TSM and TDP
> >backups on an NT machine. We kick off different backups (using the TSM
> >scheduler and NT Services) on different machines on a daily basis and are
> >unable to manually verify (due to time constraints) that these are all
> >successful. We have noticed when failure occurs during a TSM backup of a
> >particular file, it is written to the NT EventLog. On our Unix platform,
>we
> >are able to do this and email messages are sent out when a failure
>occurs.
> >Any ideas how this can be accomplished on NT?
> >
> >Justin Black
>
>
>
>
>_
>Send and receive Hotmail on your mobile device: http://mobile.msn.com


_
Chat with friends online, try MSN Messenger: http://messenger.msn.com



Re: Backup retention period

2002-05-27 Thread jamshid_akhter

Hi,
Use
QUERY COPYGROUP

and look for Retain Only Version


You need to understand the following things.

  Versions Data Exists Number of versions to keep when the data still
exists on the Client Node
  Versions Data Deleted Nnumber of versions to keep when the data no
longer exists on the client node
  Retain Extra Versions How many days to keep inactive backup versions;
the days are
  counted from the day that the version became inactive.
  Retain Only Version How many days to keep the last backup version of a
file that
  has been deleted


Type

help q copy for further detail and read TSM administrator manual.



Good luck and welcome to TSM.



- Original Message -
From: "Ruksana Siddiqui" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, May 27, 2002 12:01 AM
Subject: Backup retention period


> Hi,
>
> I just started working with TSM but can someone tell me how can I find the
> retention period of the backup I have done.
>
> I have done a particular backup and wanted to have it for atleast 3
months -
> is there anyway I tell TSM to hold it for 3 months or can I actually check
> how long TSM was configured to hold the data.
>
> Any help is highly appreciated.
>
> With regards,
> Ruksana Siddiqui
>
>
>
> CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR immediately.
Any views expressed in this message are those of the individual sender and
may not necessarily reflect the views of AMCOR.
>



Error Message

2002-05-27 Thread Steve Green

Hi,

Could you let me know what this error message means?

"ReadIndex: Message index not found for message 1006"

Also, is TSM compatable with Windows Terminal Server 4?

Thanks



Re: trace manual backup

2002-05-27 Thread Gianluca Mariani1

Fabio,
I don't know if I understand correctly your question, but if you want to
see log files and traces on a TSM Client machine (if those machines are
servers for other applications TSM doesn't care) you would need these
files:

dsmerror.log
dsmsched.log
dsm.opt
dsm.sys (if unix)
TSM server activity log (See QUERY ACTLOG)


Cordiali saluti
Gianluca Mariani
 Tech Support SSD
Via Sciangai 53, Roma
 phones : +39(0)659664598
   +393351270554 (mobile)
[EMAIL PROTECTED]



  Diciommo Fabio EDS
  cc:
  Sent by: "ADSM:Subject:  trace manual backup
  Dist Stor Manager"
  <[EMAIL PROTECTED]
  DU>


  27-05-02 18.24
  Please respond to
  "ADSM: Dist Stor
  Manager"





I would like to know if manuals backup ( only with GUI  ) on NT/2000
servers
can trace a log file.


Thanks to all

fdc



Re: trace a log on NT/2000 manuals backup

2002-05-27 Thread Gianluca Perilli

To trace a W-NT/2000 if you didn't have turn the tracing option on in the
client, you can search for the files: dsmsched.log (client), dsmerr.log
(client),server activity log (server).
If you want more details you have to turn the tracing option on in the
dsm.opt file of the client (adding to the dsm.opt "tracefile" specifying
the full path name of the log file you prefer).

Cordiali saluti / Best regards

Gianluca Perilli



Gianluca Perilli
Tivoli Customer Support
Via Sciangai n° 53 - 00144 Roma (Italy)
Tel. 06/5966 - 4581
Cell. 335/7840985


   
  
  Diciommo Fabio EDS   
  
  cc:   
  
  Sent by: "ADSM:Subject:  trace a log on  NT/2000 
manuals backup
  Dist Stor Manager"   
  
  <[EMAIL PROTECTED]  
  
  DU>  
  
   
  
   
  
  24-05-02 20.41   
  
  Please respond to
  
  "ADSM: Dist Stor 
  
  Manager" 
  
   
  
   
  



Hi all,
Is there one way to trace in a log, backups with a GUI client on windows
NT/2000 like dsmsched.log for scheduler.

many thanks

Fabio





TDP for Exchange

2002-05-27 Thread Elenara Geraldo

Hi all,

I installed and I configured TDP for Exchange in a server Windows 2000 after 
restarting the server, the same it didn't come back and its base of data was rotten.
The fact of me has just installed TDP it could have caused damages to the file of the 
base?
I installed same TDP in another servers Exchange and I never had problems equal to 
this.


---
Kind Regards,
Elenara Geraldo
Analyst Support
MML Systems
Phone: 55 41-342-7864
E-mail: [EMAIL PROTECTED]




Outgrown your current e-mail service?
Get a 25MB Inbox, POP3 Access, No Ads and No Taglines with LYCOS MAIL PLUS.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus



Re: TDP for Exchange and TSM sizing

2002-05-27 Thread Rushforth, Tim

A couple of our servers (Exchange 5.5 environment:

21.5 GB Database, 133 logs created in 1 day - 665 MB
23.3 GB Database, 179 logs created in 1 day - 895 MB

We do fulls mon-fri, incrementals on weekends.

On 5.5 a significant amount of time is spent replaying the Exchange logs
after a restore - you must consider this when deciding how often to do
fulls.

Tim Rushforth
City of Winnipeg

-Original Message-
From: DEAN LUNDGREN [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 24, 2002 2:42 PM
To: [EMAIL PROTECTED]
Subject: TDP for Exchange and TSM sizing


We are planning to convert out mail from Groupwise to Exchange 2000 and are
trying to estimate the load to TSM.   We have 2000 users on Groupwise and a
database of about 70 GB.   We are told to expect the Exchange to be three
time larger or about 200GB.

>From what I've read about TDP for Exchange we can choose to do fulls, then
either perform differentials or incremental on the log until the next full.
How big is the log compared to the database?

Some input we have received is to expect the whole database to be backed up,
which makes no sense to me.  Otherwise the TDP Exchange agent is worthless.
We have a 60 day retention policy for our mail and the implications to our
tape usage would be too much if we have to backup the whole thing.

Can anyone share the size of the Exchange database and how much log space
changes.  Please let me know whether you've chosen to use differential or
incremental and how often you do fulls.

Thanks,





Dean Lundgren
Sr. System Engineer
(740)322-5479



Re: Backup retention period

2002-05-27 Thread Ruksana Siddiqui

Hi Zlatko,

Thanks for your quick response.
According to my TSM the copygroup setting has nolimit for this management
class but the utl file has MAX versions 31.
>From what you said ( my understanding is )  below if I don't do the backup
of this database it should stay forever as it has nolimit -but if I do
perform backup it will stay for next 31 days. Correct me if I'm wrong.

The link you sent me was very useful I will start reading it.

With regards,
Ruksana Siddiqui



-Original Message-
From: Zlatko Krastev [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 7:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Backup retention period


The backup would stay there undefinitely if the content does not change.
If it changes and a new backup is performed the copy you've just becomes
obsolete and according to copygroup settings will expire some day. To
ensure it would not be before three months have passed set
VEREXIST=NOLimit and RETExtra=92.
To become familiar with TSM (which is more evolved than competitive
products) I highly recommend you to have a look at nice redbook "Tivoli
Storage Management Concepts" - SG24-4877-02
(http://www.redbooks.ibm.com/). This would save you many headaches.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Backup retention period

Hi,

I just started working with TSM but can someone tell me how can I find the
retention period of the backup I have done.

I have done a particular backup and wanted to have it for atleast 3 months
-
is there anyway I tell TSM to hold it for 3 months or can I actually check
how long TSM was configured to hold the data.

Any help is highly appreciated.

With regards,
Ruksana Siddiqui



CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of AMCOR.

CAUTION - This message may contain privileged and confidential information intended 
only for the use of the addressee named above. If you are not the intended recipient 
of this message you are hereby notified that any use, dissemination, distribution or 
reproduction of this message is prohibited. If you have received this message in error 
please notify AMCOR immediately. Any views expressed in this message are those of the 
individual sender and may not necessarily reflect the views of AMCOR.



Re: Backup retention period

2002-05-27 Thread Zlatko Krastev

Ruksana,

the method TSM usilizes is "keep several copies, check to limits, if any
limit is reached delete oldest copy"
So if you have set 31 versions and perform backups weekly last version
would be 31 weeks old. But if you set at the same time versions to stay
for 31 days you will have no more than 5 (sixth would be more than 31 days
and would be "expired").
Most recent copy ("active" one) would stay forever until you delete the
file. At that time next pair of limits (VERDELETED and RETONLY) would take
care of the copies.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Re: Backup retention period

Hi Zlatko,

Thanks for your quick response.
According to my TSM the copygroup setting has nolimit for this management
class but the utl file has MAX versions 31.
>From what you said ( my understanding is )  below if I don't do the backup
of this database it should stay forever as it has nolimit -but if I do
perform backup it will stay for next 31 days. Correct me if I'm wrong.

The link you sent me was very useful I will start reading it.

With regards,
Ruksana Siddiqui



-Original Message-
From: Zlatko Krastev [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 27, 2002 7:21 PM
To: [EMAIL PROTECTED]
Subject: Re: Backup retention period


The backup would stay there undefinitely if the content does not change.
If it changes and a new backup is performed the copy you've just becomes
obsolete and according to copygroup settings will expire some day. To
ensure it would not be before three months have passed set
VEREXIST=NOLimit and RETExtra=92.
To become familiar with TSM (which is more evolved than competitive
products) I highly recommend you to have a look at nice redbook "Tivoli
Storage Management Concepts" - SG24-4877-02
(http://www.redbooks.ibm.com/). This would save you many headaches.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:

Subject:Backup retention period

Hi,

I just started working with TSM but can someone tell me how can I find the
retention period of the backup I have done.

I have done a particular backup and wanted to have it for atleast 3 months
-
is there anyway I tell TSM to hold it for 3 months or can I actually check
how long TSM was configured to hold the data.

Any help is highly appreciated.

With regards,
Ruksana Siddiqui



CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of AMCOR.

CAUTION - This message may contain privileged and confidential information
intended only for the use of the addressee named above. If you are not the
intended recipient of this message you are hereby notified that any use,
dissemination, distribution or reproduction of this message is prohibited.
If you have received this message in error please notify AMCOR
immediately. Any views expressed in this message are those of the
individual sender and may not necessarily reflect the views of AMCOR.



Re: NT Script to check for failed backups

2002-05-27 Thread Bill Boyer

How 'bout posting them to the Scripts Depot at
http://www.coderelief.com/depot.htm so the rest of us can enjoy them, too??

Bill Boyer
DSS, Inc.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Regelin Michael (CHA)
Sent: Monday, May 27, 2002 2:45 AM
To: [EMAIL PROTECTED]
Subject: Re: NT Script to check for failed backups


Hi Jean-Baptiste,

I'm really interested in your script. We are backuping about 50 NT servers
and our only procedures is to catch information manually from the TSM
server.

However, we are soon applying a check within the TSM server that will show
us if the backup failed or succeed.

But i'm very interested in your solution. Could it be possible to look at
the scripts.

Thank's

Mike

-Message d'origine-
De : Jean-Baptiste Nothomb [mailto:[EMAIL PROTECTED]]
Envoyi : samedi, 25. mai 2002 20:17
@ : [EMAIL PROTECTED]
Objet : Re: NT Script to check for failed backups


Hello,


use WSH 5.6 and with the RUN method execute the dsmc command
to backup your data. Result of the execution will be 0 if everything
ok and >0 if an error did occur. That way it will be possible to
send you a mail. If you're interested in the scripts write me back.

Regards,
--Jean-Baptiste




>From: Justin Black <[EMAIL PROTECTED]>
>Reply-To: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: NT Script to check for failed backups
>Date: Thu, 23 May 2002 17:02:37 -0400
>
>I am looking for an automated method to check for failed TSM and TDP
>backups on an NT machine. We kick off different backups (using the TSM
>scheduler and NT Services) on different machines on a daily basis and are
>unable to manually verify (due to time constraints) that these are all
>successful. We have noticed when failure occurs during a TSM backup of a
>particular file, it is written to the NT EventLog. On our Unix platform, we
>are able to do this and email messages are sent out when a failure occurs.
>Any ideas how this can be accomplished on NT?
>
>Justin Black




_
Send and receive Hotmail on your mobile device: http://mobile.msn.com



Andreas Buser ist außer Haus

2002-05-27 Thread Andreas Buser

Ich werde ab  27.05.2002 nicht im Büro sein. Ich kehre zurück am
31.05.2002.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
Bei dringenden Fragen wenden Sie sich an T. Sellner (Tel 061 285 8646)
Email: [EMAIL PROTECTED]


FYI: Magstar 3590 reached 1TB on a cartridge

2002-05-27 Thread Zlatko Krastev

Hello all,

what a surprise - IBM is withdrawing Magstar 3575 replacing it with LTO
... but keeps another trump to play.
LTO4 will reach according to plans 800 GB but 3590 can deliver soon 1TB
http://www.storage.ibm.com/press/announce/20020513.html

Zlatko Krastev
IT Consultant