Re: restoring exchange in seperate environment

2003-01-14 Thread Tuyl Adrie, A.C. van
Exchange 5.5.

> -Oorspronkelijk bericht-
> Van:  Ochs, Duane [SMTP:[EMAIL PROTECTED]]
> Verzonden:dinsdag 14 januari 2003 17:54
> Aan:  [EMAIL PROTECTED]
> Onderwerp:Re: restoring exchange in seperate environment
>
> Which version of Exchange is being used ? E2K ?
>
> -Original Message-
> From: Tuyl Adrie, A.C. van [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 14, 2003 9:18 AM
> To: [EMAIL PROTECTED]
> Subject: restoring exchange in seperate environment
>
>
> Hi Storage experts,
>
> What is the safest way to restore an exchange server in a seperate
> environment (to extract one mailbox for instance).
> My Exchange Administrator doesn't have full confidence that the method
> described in the manual, i.e. restoring in the same domain, but without
> joining an existing site is safe. He's afraid of double connectors, double
> mail etc, double servers in the site etc.
>
> Do you have any experience with this?
>
> Is there a method of restoring only the edb's and tracking log file's?
>
>
> TSM Server 4.2.2.6 Windows NT
> TDP for Exchange 2.2.0.0
> BA Client 4.2.2.0
>
> Regards, Adrie van Tuyl
>
> **
> **
> This e-mail and any files transmitted with it are confidential and
> intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this e-mail in error, please notify
> [EMAIL PROTECTED]
> This footnote also confirms that this e-mail message has been checked by
> McAfee Groupshield for the presence of computer viruses.
> **
> **

This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error, please notify
[EMAIL PROTECTED]
This footnote also confirms that this e-mail message has been checked by
McAfee Groupshield for the presence of computer viruses.




Re: Non-empty volume with no content

2003-01-14 Thread Paul Ripke
Thanks, guys. As it happened, I had two tapes in this state. "AUDIT VOL"
wanted to mount, so a recalled the tapes onsite. Ran an "AUDIT VOL" on the
first one, no apparent change. Ran "MOVE DATA" on a whim. Said it moved
stuff, but still no apparent change. Ran "AUDIT VOL" again, which returned:
ANR2334W Missing or incorrect information detected by AUDIT
  VOLUME for volume SP0209 - information will be created or corrected.
and left the volume in an empty status. "DELE VOL" and all was happy for
that tape. Went to do something similar on the second tape and discovered
a reclamation had kicked off and cleaned it up automagically. I'm not going
to even try to understand what happened...

Cheers,
Paul Ripke
UNIX/OpenVMS Sysadmin
CSC, Port Kembla 2502, NSW, Australia
Phone +61 2 4275 4101
Fax +61 2 4275 7801
Mobile +61 419 432 517
101 reasons why you can't find your Sysadmin:
68. It's 9 AM. He/she is not working that late.
-- Koos van den Hout


This email, including any attachments, is intended only for use by the
addressee(s) and may contain confidential and/or personal information and
may also be the subject of legal privilege. Any personal information
contained in this email is not to be used or disclosed for any purpose
other than the purpose for which you have received it. If you are not the
intended recipient, you must not disclose or use the information contained
in it. In this case, please let me know by return email, delete the message
permanently from your system and destroy any copies.




Re: Database question

2003-01-14 Thread Ramnarayan, Sean A [EDS]
Hi

IF you are running AIX ver 4.3 and above and also using SSA disks, have
you ever tried the option of export and importvg within AIX. This will
solve all your problems as it will take half the time to rebuild your
server.

Thks
Sean 
AIX and TSM Admin
EDS (South Africa) 

-Original Message-
From: Justin Bleistein [mailto:[EMAIL PROTECTED]] 
Sent: Tuesday, January 14, 2003 11:49 PM
To: [EMAIL PROTECTED]
Subject: Re: Database question

  The "dsmserv upgrade" method is an interesting way. I would like
to
hear other people's input into that. But how we did it when we had to
move
from one H80 to another is we backed the database up to tape. Turned off
H80 1 and then powered up H80 2 and went through a dr procedure on that
system basically. We created the logical volume, the file system, then
ran
a dsmserv format command for the log and database then we simply defined
our devconfig and dsmserv.opt file after we installed the TSM server
software of course and restored and we were up in no time. Of course
this
was to and from the same version with the exception of a maintenance
level
or two. Just an idea on how we did it and I didn't find it very
difficult
or any gotchas (to the same version) of course. You may need to use the
upgrade command going from one version to another. I'm not really sure I
would think so. Thanks!.

--Justin Richard Bleistein
Unix Systems Administrator (Sungard eSourcing)
Desk: (856) 866 - 4017
Cell:(856) 912 - 0861
Email: [EMAIL PROTECTED]



  Jeff G Kloek
 cc:
  Sent by: "ADSM:  Subject:  Database
question
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  01/14/2003 04:47
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Part of our upcoming move includes moving from TSM 4.2.1.9 on AIX 4.3.3
on
RS6000 S7A to TSM 5.1.5.4 on P670 on AIX 5.2.
I've set up an instance of TSM at that level on the P670. Now I'm trying
to
fathom the best way to actually move the database
over. I'm going to be dropping all the disk and tape connections from
the
S7A and connecting them to the P670. I'll have time
to get all the devices defined and paths defined, so that with the
exception of the path statements, the storage pools, libraries
tape drives, log directories, db directories and files will all be
configured the same as before. My question is this: If I did all the
above, could I simply do a "dsmserv upgradedb" and let it fly?
I'm sure this isn't supported, so I'm just wondering aloud.

Thanks!!



Re: keepalive between server and storage agent

2003-01-14 Thread Ron Pavan
Had a similar problem and one solution would be to write a script on your
(BTSM Server that pings the ip address of the Storage Agent Machine once every
(B55 min.  In our case this kept the route alive so the Client (or Agent in
(Byour case) knows how to get back to the TSM Server.
(B
(B-Original Message-
(BFrom: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
(BKunio Miyazawa
(BSent: Tuesday, January 14, 2003 4:32 PM
(BTo: [EMAIL PROTECTED]
(BSubject: keepalive between server and storage agent
(B
(B
(BHello,
(B
(BWe have a firewall between TSM server and StorageAgent.
(BThis firewall disconnects an idle connection after one hour.
(BThis becomes a cause of problem when StorageAgent gets MediaW.
(BIf MediaW is over 1H, StorageAgent does not mount a volume any more.
(BWaiting a volume forever even drives are free.
(BDoes anyone know how to prevent this?
(B
(BServer version 4.2.2.8, StorageAgent is same.
(BAIX4.3.3 ML08
(B
(BThanks in advance.
(B
(B
(BK. Miyazawa
(BSRA Europe B.V.



keepalive between server and storage agent

2003-01-14 Thread Kunio Miyazawa
Hello,
(B
(BWe have a firewall between TSM server and StorageAgent.
(BThis firewall disconnects an idle connection after one hour.
(BThis becomes a cause of problem when StorageAgent gets MediaW.
(BIf MediaW is over 1H, StorageAgent does not mount a volume any more.
(BWaiting a volume forever even drives are free.
(BDoes anyone know how to prevent this?
(B
(BServer version 4.2.2.8, StorageAgent is same.
(BAIX4.3.3 ML08
(B
(BThanks in advance.
(B
(B
(BK. Miyazawa
(BSRA Europe B.V.



Re: Error during "delete volhistory"

2003-01-14 Thread Paul Ripke
John,

That's pretty much the command I used, displayed in the actlog below...

Cheers,
--
Paul

John Naylor <[EMAIL PROTECTED]> on 14/01/2003 22:29:

Paul,
You could try
del volh tod=today vol=xx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)

Paul Ripke <[EMAIL PROTECTED]> on 01/13/2003 06:58:04 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"


Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke



Re: Database question

2003-01-14 Thread Justin Bleistein
  The "dsmserv upgrade" method is an interesting way. I would like to
hear other people's input into that. But how we did it when we had to move
from one H80 to another is we backed the database up to tape. Turned off
H80 1 and then powered up H80 2 and went through a dr procedure on that
system basically. We created the logical volume, the file system, then ran
a dsmserv format command for the log and database then we simply defined
our devconfig and dsmserv.opt file after we installed the TSM server
software of course and restored and we were up in no time. Of course this
was to and from the same version with the exception of a maintenance level
or two. Just an idea on how we did it and I didn't find it very difficult
or any gotchas (to the same version) of course. You may need to use the
upgrade command going from one version to another. I'm not really sure I
would think so. Thanks!.

--Justin Richard Bleistein
Unix Systems Administrator (Sungard eSourcing)
Desk: (856) 866 - 4017
Cell:(856) 912 - 0861
Email: [EMAIL PROTECTED]



  Jeff G Kloek
 cc:
  Sent by: "ADSM:  Subject:  Database question
  Dist Stor
  Manager"
  <[EMAIL PROTECTED]
  .EDU>


  01/14/2003 04:47
  PM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Part of our upcoming move includes moving from TSM 4.2.1.9 on AIX 4.3.3 on
RS6000 S7A to TSM 5.1.5.4 on P670 on AIX 5.2.
I've set up an instance of TSM at that level on the P670. Now I'm trying to
fathom the best way to actually move the database
over. I'm going to be dropping all the disk and tape connections from the
S7A and connecting them to the P670. I'll have time
to get all the devices defined and paths defined, so that with the
exception of the path statements, the storage pools, libraries
tape drives, log directories, db directories and files will all be
configured the same as before. My question is this: If I did all the
above, could I simply do a "dsmserv upgradedb" and let it fly?
I'm sure this isn't supported, so I'm just wondering aloud.

Thanks!!



Réf. : Database question

2003-01-14 Thread Guillaume Gilbert
If all your config files (dsmserv.opt dsmserv.dsk, devconfig and volhistory) are the 
same and all database, log and stgpool files are the same, there should be no
problem. You could even move those around and have the dsmserv.dsk reflect the changes 
and it would be OK.   My SUN server just crashed big time over the weekend and we
had to reinstall the OS. All I did was reinstall TSM and recreate the config files. It 
started up without a hitch.

Guillaume Gilbert
CGI Canada




Jeff G Kloek <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 2003-01-14 16:47:28

Veuillez répondre à "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Envoyé par :  "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>


Pour : [EMAIL PROTECTED]
cc :
Objet : Database question

Part of our upcoming move includes moving from TSM 4.2.1.9 on AIX 4.3.3 on
RS6000 S7A to TSM 5.1.5.4 on P670 on AIX 5.2.
I've set up an instance of TSM at that level on the P670. Now I'm trying to
fathom the best way to actually move the database
over. I'm going to be dropping all the disk and tape connections from the
S7A and connecting them to the P670. I'll have time
to get all the devices defined and paths defined, so that with the
exception of the path statements, the storage pools, libraries
tape drives, log directories, db directories and files will all be
configured the same as before. My question is this: If I did all the
above, could I simply do a "dsmserv upgradedb" and let it fly?
I'm sure this isn't supported, so I'm just wondering aloud.

Thanks!!







Database question

2003-01-14 Thread Jeff G Kloek
Part of our upcoming move includes moving from TSM 4.2.1.9 on AIX 4.3.3 on
RS6000 S7A to TSM 5.1.5.4 on P670 on AIX 5.2.
I've set up an instance of TSM at that level on the P670. Now I'm trying to
fathom the best way to actually move the database
over. I'm going to be dropping all the disk and tape connections from the
S7A and connecting them to the P670. I'll have time
to get all the devices defined and paths defined, so that with the
exception of the path statements, the storage pools, libraries
tape drives, log directories, db directories and files will all be
configured the same as before. My question is this: If I did all the
above, could I simply do a "dsmserv upgradedb" and let it fly?
I'm sure this isn't supported, so I'm just wondering aloud.

Thanks!!



Re: Netware NDS question for TSM

2003-01-14 Thread Jim Kirkman
On one of the older clients there was a problem where a leading zero was
getting in the password and causing problems, but I don't remember which rev
that was on. Try changing the pwd and see what happens.

Ron Lochhead wrote:

> OS= Netware 4.11
> TSM = 3.1.0.6
> NDS = 6.13
>
> We are backing up multiple Netware servers using a older ver of the TSM
> client because the Netware client back in June 2002 would not work on those
> servers.  We recently setup NDS to be backed up via the scheduler and now
> when the scheduler attempts to kick off the backup it prompts for a Netware
> user id and pw?  So does anyone know how we can insert the Netware user id
> and pw to prevent this from taking place?
>
> Thanks in advance.  Ron Lochhead

--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884



Re: How is the *.PST freed?

2003-01-14 Thread Prather, Wanda
We also backup a lot of LARGE .pst files on personal PC's.

Many of our users have multiple .pst files, and they get released
periodically, so most users get a couple of backups a week, especially if we
can get them to leave the PC on overnight so that the backup occurs a while
after they leave.

I have had NO luck getting the files to release early by creating the
mspst.ini file - if you have success with that, please let me know!

The .pab file doesn't seem to EVER get released.

So we aren't getting as many backups as we would like, but it's better than
nothing...


-Original Message-
From: MC Matt Cooper (2838) [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 1:58 PM
To: [EMAIL PROTECTED]
Subject: How is the *.PST freed?


Hello all,
I am using TSM 5.1.5.4 server and 5.1.0 and 5.1.5.2 clients on
WindowsXP clients.
I have been tasked with backing up a couple hundred desktops, during
the day.   Of course the number 1 file of importance is everyone's E-MAIL.
We are using WindowsXP and OUTLOOK 2000.   I notice that many of the PC's
have there e-mail file OPEN and it is skipped.   However many are being
backed up and these people also have there e-mail open.   My Guess is that
after a period of inactivity that the outlook email file user.PST is
released.
DOES ANYONE KNOW THIS TO BE A FACT?
HOW CAN THIS 'period of inactivity' variable be shorted so most people get
there .PST file backed up?
Thanks in advance
Matt



Re: restoring exchange in seperate environment

2003-01-14 Thread Rajesh Oak
It's a very safe and simple process. We do it all the time and we manage 18 Exchange 
Servers at different locations.
We have an Exchange restore server at all the Exchange sites to which we restore the 
Information Store. Then we extract the users mailbox.

Rajesh Oak
--

On Tue, 14 Jan 2003 11:27:50
 Bruce Kamp wrote:
>I have done it a couple of times without causing any problems.  I
>followed the manual.
>
>--
>Bruce Kamp
>Midrange Systems Analyst II
>Memorial Healthcare System
>E: [EMAIL PROTECTED]
>P: (954) 987-2020 x4597
>F: (954) 985-1404
>---
>
>
>-Original Message-
>From: Mark Stapleton [mailto:[EMAIL PROTECTED]]
>Sent: Tuesday, January 14, 2003 11:19 AM
>To: [EMAIL PROTECTED]
>Subject: Re: restoring exchange in seperate environment
>
>
>On Tue, 2003-01-14 at 09:18, Tuyl Adrie, A.C. van wrote:
>> What is the safest way to restore an exchange server in a seperate
>> environment (to extract one mailbox for instance). My Exchange
>> Administrator doesn't have full confidence that the method described
>> in the manual, i.e. restoring in the same domain, but without joining
>> an existing site is safe. He's afraid of double connectors, double
>> mail etc, double servers in the site etc.
>
>It is absolutely safe, as long as you follow the instructions in the TDP for
>Exchange manual. I've done it (or seen it done) a dozen times. Your Exchange
>administrator needs to read the MS docs on this process; it's well
>documented.
>
>--
>Mark Stapleton ([EMAIL PROTECTED])
>


_
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus



Re: How is the *.PST freed?

2003-01-14 Thread Rajesh Oak
You have to close Outlook to backup the pst file. Outlook puts an exclusive lock on 
the pst when it is open and therefore cannot be backed up. I have the same problem.
Solution to this problem.
"If you need your personal folder to be backed up, make sure you close outlook when 
you go home." is the message that needs to go out to the clients.

Rajesh Oak
--

On Tue, 14 Jan 2003 11:05:53
 Joshua Bassi wrote:
>I have never been able to backup a PST file while Outlook was open.  You
>might want to double-check on that because I believe Microsoft puts a
>lock on the file ANYTIME it's open.
>
>
>--
>Joshua S. Bassi
>IBM Certified - AIX 4/5L, SAN, Shark
>Tivoli Certified Consultant -ADSM/TSM
>eServer Systems Expert -pSeries HACMP
>
>AIX, HACMP, Storage, TSM Consultant
>Cell (831) 595-3962
>[EMAIL PROTECTED]
>
>-Original Message-
>From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
>MC Matt Cooper (2838)
>Sent: Tuesday, January 14, 2003 10:58 AM
>To: [EMAIL PROTECTED]
>Subject: How is the *.PST freed?
>
>
>Hello all,
>I am using TSM 5.1.5.4 server and 5.1.0 and 5.1.5.2 clients on
>WindowsXP clients.
>I have been tasked with backing up a couple hundred desktops,
>during
>the day.   Of course the number 1 file of importance is everyone's
>E-MAIL.
>We are using WindowsXP and OUTLOOK 2000.   I notice that many of the
>PC's
>have there e-mail file OPEN and it is skipped.   However many are being
>backed up and these people also have there e-mail open.   My Guess is
>that
>after a period of inactivity that the outlook email file user.PST is
>released. DOES ANYONE KNOW THIS TO BE A FACT? HOW CAN THIS 'period of
>inactivity' variable be shorted so most people get there .PST file
>backed up? Thanks in advance Matt
>


_
Get 25MB, POP3, Spam Filtering with LYCOS MAIL PLUS for $19.95/year.
http://login.mail.lycos.com/brandPage.shtml?pageId=plus&ref=lmtplus



Re: How is the *.PST freed?

2003-01-14 Thread Richard Sims
>...DOES ANYONE KNOW THIS TO BE A FACT? HOW CAN THIS 'period of
>inactivity' variable be shorted so most people get there .PST file
>backed up? ...

See the ".PST filename suffix and access" entry
in  http://people.bu.edu/rbs/ADSM.QuickFacts



Re: How is the *.PST freed?

2003-01-14 Thread Joshua Bassi
I have never been able to backup a PST file while Outlook was open.  You
might want to double-check on that because I believe Microsoft puts a
lock on the file ANYTIME it's open.


--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant -ADSM/TSM
eServer Systems Expert -pSeries HACMP

AIX, HACMP, Storage, TSM Consultant
Cell (831) 595-3962
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
MC Matt Cooper (2838)
Sent: Tuesday, January 14, 2003 10:58 AM
To: [EMAIL PROTECTED]
Subject: How is the *.PST freed?


Hello all,
I am using TSM 5.1.5.4 server and 5.1.0 and 5.1.5.2 clients on
WindowsXP clients.
I have been tasked with backing up a couple hundred desktops,
during
the day.   Of course the number 1 file of importance is everyone's
E-MAIL.
We are using WindowsXP and OUTLOOK 2000.   I notice that many of the
PC's
have there e-mail file OPEN and it is skipped.   However many are being
backed up and these people also have there e-mail open.   My Guess is
that
after a period of inactivity that the outlook email file user.PST is
released. DOES ANYONE KNOW THIS TO BE A FACT? HOW CAN THIS 'period of
inactivity' variable be shorted so most people get there .PST file
backed up? Thanks in advance Matt



Re: Problems with Windows Cluster.

2003-01-14 Thread Lasse Tastesen
Hi Jorge.

 

You are not mentioning the client and server level.

If your client is new enough try using the journal engine, it might be useful if there 
is about 100 files on your client. 

 

BR Lasse


Hello folks !!!

I have a problem with a Windows 2000 cluster. The TSM is taking a long time to do the 
backup. it4s a long time processing the files locally (I look for problems in CPU 
utilization, Processor utilization, and so on...). there is lots of files locally 
(aproximately 1.000.000 files, it4s a file server).

the network traffic rate is ok (between 6 and 15 MB)...the Machine is a Intel with 2 
GB RAM, 180 GB HD, 4 GB virtual memory.

I have tried a script (or several scripts), describing the list of files...I tried 
several schedules (with several scripts)...and the time so, so..long - 
aproximately 40 hours...I put in dsm.opt the resourceutilization for 6 (trying open 
several sessions to backup go on...).

I don4t know anymore...

Please, anyone can help me ??


hugs

Jorge Martins
Service IT Solutions
www.service.com.br - RS/Brazil



Icon - Internet gratis, MP3, Vmdeo, radio, e-mail e informagco.
Pega ja o seu em www.ibest.com.br/icon/mail1.html. I gratis!



How is the *.PST freed?

2003-01-14 Thread MC Matt Cooper (2838)
Hello all,
I am using TSM 5.1.5.4 server and 5.1.0 and 5.1.5.2 clients on
WindowsXP clients.
I have been tasked with backing up a couple hundred desktops, during
the day.   Of course the number 1 file of importance is everyone's E-MAIL.
We are using WindowsXP and OUTLOOK 2000.   I notice that many of the PC's
have there e-mail file OPEN and it is skipped.   However many are being
backed up and these people also have there e-mail open.   My Guess is that
after a period of inactivity that the outlook email file user.PST is
released.
DOES ANYONE KNOW THIS TO BE A FACT?
HOW CAN THIS 'period of inactivity' variable be shorted so most people get
there .PST file backed up?
Thanks in advance
Matt



Re: Netware NDS question for TSM

2003-01-14 Thread David Longo
After you manually enter it the first time, it shouldn't prompt
again.

David Longo

>>> [EMAIL PROTECTED] 01/14/03 01:28PM >>>
OS= Netware 4.11
TSM = 3.1.0.6
NDS = 6.13

We are backing up multiple Netware servers using a older ver of the
TSM
client because the Netware client back in June 2002 would not work on
those
servers.  We recently setup NDS to be backed up via the scheduler and
now
when the scheduler attempts to kick off the backup it prompts for a
Netware
user id and pw?  So does anyone know how we can insert the Netware user
id
and pw to prevent this from taking place?

Thanks in advance.  Ron Lochhead


"MMS " made the following
 annotations on 01/14/2003 01:50:27 PM
--
This message is for the named person's use only.  It may contain confidential, 
proprietary, or legally privileged information.  No confidentiality or privilege is 
waived or lost by any mistransmission.  If you receive this message in error, please 
immediately delete it and all copies of it from your system, destroy any hard copies 
of it, and notify the sender.  You must not, directly or indirectly, use, disclose, 
distribute, print, or copy any part of this message if you are not the intended 
recipient.  Health First reserves the right to monitor all e-mail communications 
through its networks.  Any views or opinions expressed in this message are solely 
those of the individual sender, except (1) where the message states such views or 
opinions are on behalf of a particular entity;  and (2) the sender is authorized by 
the entity to give such views or opinions.

==



Re: AIX 5.2

2003-01-14 Thread PINNI, BALANAND (SBCSI)
I have migrated OS 433 TO 5L .After migration 3.7.3, 4.X worked ok for me.
But if I install new OS 5L I can not install TSM 3.7 Client on it.

This is what I experienced.

Balanand Pinni

-Original Message-
From: Kathleen Hallahan [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 12:32 PM
To: [EMAIL PROTECTED]
Subject: AIX 5.2


I've just received a request from a client admin for a TSM client version to
run on an AIX 5.2 client.  However, there is no version currently supported
for this level of OS.  Has anyone out there tried it yet, and if so, how is
it working for you?  My server is also AIX, currently 4.3.3 although we were
also anticipating moving to new hardware and AIX 5.2 not too far down the
road.

Meanwhile, I'm suggesting to our admin that he goes ahead and tries out the
5.1 version that we've already tested; I figure that an unsupported backup
is better (hopefully!) than no backup at all.

Ideas would be greatly appreciated!

Kathleen



Netware NDS question for TSM

2003-01-14 Thread Ron Lochhead
OS= Netware 4.11
TSM = 3.1.0.6
NDS = 6.13

We are backing up multiple Netware servers using a older ver of the TSM
client because the Netware client back in June 2002 would not work on those
servers.  We recently setup NDS to be backed up via the scheduler and now
when the scheduler attempts to kick off the backup it prompts for a Netware
user id and pw?  So does anyone know how we can insert the Netware user id
and pw to prevent this from taking place?

Thanks in advance.  Ron Lochhead



AIX 5.2

2003-01-14 Thread Kathleen Hallahan
I've just received a request from a client admin for a TSM client version
to run on an AIX 5.2 client.  However, there is no version currently
supported for this level of OS.  Has anyone out there tried it yet, and if
so, how is it working for you?  My server is also AIX, currently 4.3.3
although we were also anticipating moving to new hardware and AIX 5.2 not
too far down the road.

Meanwhile, I'm suggesting to our admin that he goes ahead and tries out the
5.1 version that we've already tested; I figure that an unsupported backup
is better (hopefully!) than no backup at all.

Ideas would be greatly appreciated!

Kathleen



Re: Exclude Question

2003-01-14 Thread Gill, Geoffrey L.
Mehdi,

This works for me:
Exclude.Dir D:\SMS

Don't forget, once you've made a change you have to restart the service for
it to pick up. You can also use the GUI to see if your exclude is working
properly. In this case click on backup and you will not see the directory
excluded when you traverse the tree.

Geoff Gill
TSM Administrator
NT Systems Support Engineer
SAIC
E-Mail:   [EMAIL PROTECTED]
Phone:  (858) 826-4062
Pager:   (877) 905-7154



> -Original Message-
> From: Sung Y Lee [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 14, 2003 9:17 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Exclude Question
>
>
> Hello,
>
> Just a suggestion..I didn't have the manual for Windows
> client, but looked up Unix client manual.  It had / after the
> directory.
>
> Give this a try.
>
>
> Exclude.Dir "D:\SMS\"
>
>
> Sung Y. Lee
> Enterprise Storage Services
> IBM Global Services, Service Delivery Center - South
> Office (512) 823-1012 T/L 793-1012
> Fax (512) 823-1037
> Pager  ( 800) 759- PIN: 1087116
> E-mail  [EMAIL PROTECTED]



Re: /VAR skipped during incremental

2003-01-14 Thread Mark Stapleton
On Mon, 2003-01-13 at 08:36, Loon, E.J. van - SPLXM wrote:
> I have got one TSM client (4.2.1.0) which skips /VAR during an incremental.
> dsmc i /var works fine, there are no errors in the dsmerror.log.
> Does anybody know what could be the cause of this?

Who are you logged in as when you run the backup? What do you see when
you run
dsmc i /var/* -subdir=yes -pick

(I ask this because I had the same problem with a Linux client, until I
realized that I wasn't logged on as root, which is the ID you have to
use to get all of /var backed up.)

--
Mark Stapleton ([EMAIL PROTECTED])



Re: Non-empty volume with no content

2003-01-14 Thread Roger Deschner
I encountered this once before. It wouldn't delete it. DELETE VOL
DISCARDDATA=YES said no data to discard, but then it didn't delete it.
AUDIT VOL said everything is fine, what are you bothering me for? A
simple server restart cleared it up for me.

IBM: Please don't go rush out and fix this in a panic unless you happen
to be in this area. If I were to actually report it, it would definitely
be "Sev 4". Low impact and easily circumvented. There are more important
things to pay attention to.

Roger Deschner  University of Illinois at Chicago [EMAIL PROTECTED]


On Mon, 13 Jan 2003, Boireau, Eric (MED) wrote:

>Perform an audit vol SP0335 fix=yes.
>PS : You can try this without the tape, it works for me.
>
>Regards,
>Eric Boireau
>
>-Original Message-
>From: Paul Ripke [mailto:[EMAIL PROTECTED]]
>Sent: Monday, January 13, 2003 07:57
>To: [EMAIL PROTECTED]
>Subject: Non-empty volume with no content
>
>
>I guess this is a sign of a corrupted database?
>Is there anything that can be done apart from "audit db"?
>dele vol sp0335 discard=yes?
>audi vol sp0335 fix=yes?
>
>tsm: BHPS>q vol sp0335
>
>Volume Name  Storage Device Estimated
>Pct  Volume
> Pool Name   Class Name  Capacity
>Util  Status
> (MB)
> --- -- -
>- 
>SP0335   OFFSITE 359057,689.3
>0.7   Full
>
>tsm: BHPS>q cont sp0335
>ANR2034E QUERY CONTENT: No match found using this criteria.
>ANS8001I Return code 11.
>
>"move data" and reclamations both return:
>  ANR1163W Offsite volume SP0335 still contains files which could not
>be moved.
>
>Cheers,
>--
>Paul Ripke
>UNIX/OpenVMS Sysadmin
>CSC, Port Kembla 2502, NSW, Australia
>Phone +61 2 4275 4101
>Fax +61 2 4275 7801
>Mobile +61 419 432 517
>101 reasons why you can't find your Sysadmin:
>68. It's 9 AM. He/she is not working that late.
>-- Koos van den Hout
>
>
>
>This email, including any attachments, is intended only for use by the
>addressee(s) and may contain confidential and/or personal information and
>may also be the subject of legal privilege. Any personal information
>contained in this email is not to be used or disclosed for any purpose
>other than the purpose for which you have received it. If you are not the
>intended recipient, you must not disclose or use the information contained
>in it. In this case, please let me know by return email, delete the message
>permanently from your system and destroy any copies.
>
>
>



Re: Exclude Question

2003-01-14 Thread Sung Y Lee
Hello,

Just a suggestion..I didn't have the manual for Windows client, but looked
up Unix client manual.  It had / after the directory.

Give this a try.


Exclude.Dir "D:\SMS\"


Sung Y. Lee
Enterprise Storage Services
IBM Global Services, Service Delivery Center - South
Office (512) 823-1012 T/L 793-1012
Fax (512) 823-1037
Pager  ( 800) 759- PIN: 1087116
E-mail  [EMAIL PROTECTED]



  "Amini, Mehdi"
  cc:
  Sent by: "ADSM:Subject:  Exclude Question
  Dist Stor Manager"
  <[EMAIL PROTECTED]
  DU>


  01/14/2003 08:55 AM
  Please respond to
  "ADSM: Dist Stor
  Manager"






Below is the copy of DSM.OPT file for our SMS Server...As you can see I
have
excluded D:\SMS folder from backing up and yet in the morning when I look
at
the Log...it shows me this folder being backed up.What is wrong here:


* IBM Adstar Distributed Storage Manager
*
* Sample dsm.opt for 32-Bit Windows backup and archive Client - V3 level
*
* See options.wri for complete options file documentation


*
* TCP/IP
*

commmethod  tcpip
tcpport  
TCPServeraddress XXX.XXX.XXX.XXX

*
* ipx/spx
*

*
* netbios
*

*commmethod   netbios
*netbiosname   client1
*netbiosservername ntserver1

*
* named pipes
*

*commmethod namedpipe
namedpipename \\.\pipe\adsmpipe



* COMPression
*
* +--+--+
* | COMPression  | ON|OFf   |
* +--+--+
* System default: OFf
*
* Option file example:
*
 COMPression ON
* COMPression OFf




* DOMain
*
* +--+--+
* | DOMain   | ALL-LOCAL|domain |
* +--+--+
* System default: ALL-LOCAL
*
* Options file examples:
*
* DOMain ALL-LOCAL Q:




* EXclude and INclude
*
* +--+--+
* | EXclude  | pattern  |
* +--+--+
* | INclude  | pattern  |
* +--+--+
*
* EXclude and INclude patterns are written using an extended pattern
* match language.  This language uses the native operating system's
* metacharacters (wildcards) whenever possible.  A list of the
* supported metacharacters for the match language follows:
*
*   Function   AIX   DOS  OS/2
*   -     -
*   Match one character? ??
*   Match n characters * **
*   Match n directories/... (1)  \... (1) \...  (1)
*   Directory Separator/ \\
*   Open Character Class   [[(1) [(1)
*   Character Class Range  - -(1) - (1)
*   Close Character Class  ]](1) ](1)
*   Literal Escape \ \(1) \ (1)
*   Drive Separatornone  ::
*
*


*Exclude *:\IBMBIO.COM
*Exclude *:\IBMDOS.COM
*Exclude *:\MSDOS.SYS
*Exclude *:\IO.SYS
*Exclude *:\...\SYSTEM32\CONFIG\*.*
*Exclude *:\...\SYSTEM32\CONFIG\...\*




* NodeName
*
* +--+--+
* | MACHinename  | client_name  |
* +--+---

Re: Is upgrade DB required?

2003-01-14 Thread Joshua Bassi
No, an upgrade DB should not be required.


--
Joshua S. Bassi
IBM Certified - AIX 4/5L, SAN, Shark
Tivoli Certified Consultant -ADSM/TSM
eServer Systems Expert -pSeries HACMP

AIX, HACMP, Storage, TSM Consultant
Cell (831) 595-3962
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]] On Behalf Of
David Browne
Sent: Tuesday, January 14, 2003 8:50 AM
To: [EMAIL PROTECTED]
Subject: Is upgrade DB required?


Is an upgrade DB required to go from TSM 4.2.1.9 on OS390/2.10 to TSM
4.2.3.0?



Re: restoring exchange in seperate environment

2003-01-14 Thread Ochs, Duane
Which version of Exchange is being used ? E2K ?

-Original Message-
From: Tuyl Adrie, A.C. van [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 9:18 AM
To: [EMAIL PROTECTED]
Subject: restoring exchange in seperate environment


Hi Storage experts,

What is the safest way to restore an exchange server in a seperate
environment (to extract one mailbox for instance).
My Exchange Administrator doesn't have full confidence that the method
described in the manual, i.e. restoring in the same domain, but without
joining an existing site is safe. He's afraid of double connectors, double
mail etc, double servers in the site etc.

Do you have any experience with this?

Is there a method of restoring only the edb's and tracking log file's?


TSM Server 4.2.2.6 Windows NT
TDP for Exchange 2.2.0.0
BA Client 4.2.2.0

Regards, Adrie van Tuyl


This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error, please notify
[EMAIL PROTECTED]
This footnote also confirms that this e-mail message has been checked by
McAfee Groupshield for the presence of computer viruses.




Is upgrade DB required?

2003-01-14 Thread David Browne
Is an upgrade DB required to go from TSM 4.2.1.9 on OS390/2.10 to TSM
4.2.3.0?



Re: Exclude Question

2003-01-14 Thread Sunil Nair
Amini ,


Try this exclude.dir *:\

Thanx
Sunil.
 "Amini, Mehdi" <[EMAIL PROTECTED]> wrote:Below is the copy of DSM.OPT file 
for our SMS Server...As you can see I have
excluded D:\SMS folder from backing up and yet in the morning when I look at
the Log...it shows me this folder being backed up.What is wrong here:


* IBM Adstar Distributed Storage Manager
*
* Sample dsm.opt for 32-Bit Windows backup and archive Client - V3 level
*
* See options.wri for complete options file documentation


*
* TCP/IP
*

commmethod tcpip
tcpport 
TCPServeraddress XXX.XXX.XXX.XXX

*
* ipx/spx
*

*
* netbios
*

*commmethod netbios
*netbiosname client1
*netbiosservername ntserver1

*
* named pipes
*

*commmethod namedpipe
namedpipename \\.\pipe\adsmpipe



* COMPression
*
* +--+--+
* | COMPression | ON|OFf |
* +--+--+
* System default: OFf
*
* Option file example:
*
COMPression ON
* COMPression OFf




* DOMain
*
* +--+--+
* | DOMain | ALL-LOCAL|domain |
* +--+--+
* System default: ALL-LOCAL
*
* Options file examples:
*
* DOMain ALL-LOCAL Q:




* EXclude and INclude
*
* +--+--+
* | EXclude | pattern |
* +--+--+
* | INclude | pattern |
* +--+--+
*
* EXclude and INclude patterns are written using an extended pattern
* match language. This language uses the native operating system's
* metacharacters (wildcards) whenever possible. A list of the
* supported metacharacters for the match language follows:
*
* Function AIX DOS OS/2
* -   -
* Match one character ? ? ?
* Match n characters * * *
* Match n directories /... (1) \... (1) \... (1)
* Directory Separator / \ \
* Open Character Class [ [(1) [(1)
* Character Class Range - - (1) - (1)
* Close Character Class ] ](1) ](1)
* Literal Escape \ \ (1) \ (1)
* Drive Separator none : :
*
*


*Exclude *:\IBMBIO.COM
*Exclude *:\IBMDOS.COM
*Exclude *:\MSDOS.SYS
*Exclude *:\IO.SYS
*Exclude *:\...\SYSTEM32\CONFIG\*.*
*Exclude *:\...\SYSTEM32\CONFIG\...\*




* NodeName
*
* +--+--+
* | MACHinename | client_name |
* +--+--+
* Default: Netbios Name (NT/Win95 Computer name)
*
* Option file example:
*
* MACHinename


NODENAME XXX
password XX


* REPlace
*
* +--+--+
* | REPlace | Yes|No|Prompt |
* +--+--+
* System default: Prompt
*
* Option file example:
*
* REPlace N
* REPlace Y




* SUbdir
*
* +--+--+
* | SUbdir | Yes|No |
* +--+--+
* System default: No
*
* Option file example:
*
SUbdir Yes
* SUbdir No




* TCPPort
*
* +--+--+
* | TCPPort 

Re: restoring exchange in seperate environment

2003-01-14 Thread Bruce Kamp
I have done it a couple of times without causing any problems.  I
followed the manual.

--
Bruce Kamp
Midrange Systems Analyst II
Memorial Healthcare System
E: [EMAIL PROTECTED]
P: (954) 987-2020 x4597
F: (954) 985-1404
---


-Original Message-
From: Mark Stapleton [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 11:19 AM
To: [EMAIL PROTECTED]
Subject: Re: restoring exchange in seperate environment


On Tue, 2003-01-14 at 09:18, Tuyl Adrie, A.C. van wrote:
> What is the safest way to restore an exchange server in a seperate
> environment (to extract one mailbox for instance). My Exchange
> Administrator doesn't have full confidence that the method described
> in the manual, i.e. restoring in the same domain, but without joining
> an existing site is safe. He's afraid of double connectors, double
> mail etc, double servers in the site etc.

It is absolutely safe, as long as you follow the instructions in the TDP for
Exchange manual. I've done it (or seen it done) a dozen times. Your Exchange
administrator needs to read the MS docs on this process; it's well
documented.

--
Mark Stapleton ([EMAIL PROTECTED])



Re: TSM migration problem & recovery log question???

2003-01-14 Thread Jane Bamberger
Hi, Joni,

When was the last DBBackup? Did that finish successfully? If not, The log will not 
empty.

Jane
%%
Jane Bamberger
IS Department
Bassett Healthcare
607-547-4750
- Original Message - 
From: Joni Moyer 
To: [EMAIL PROTECTED] 
Sent: Tuesday, January 14, 2003 11:05 AM
Subject: Re: TSM migration problem & recovery log question???


I really don't know what is wrong with the recovery log.  There are no
clients that have been connected to the server for more than 4 minutes.  I
have a backup of a primary tape pool to a copy tape pool running 1 process.
Other than that everything is silent.  I can't seem to get the log to clear
to 0% and soon I'll have to add more space which will take it to 6 GB for
the recovery log.  I am still baffled about this.

We have TSM on the mainframe and it is attached to STK silos with 3590
magstar tapes.  As far as I know communication wasn't lost because other
migrations/backups etc. were running.  I was just having problems with 1
out of 3 of my disk storage pools migrating to tape.  I looked through the
logs trying to find out what tape it might have been trying to migrate to,
but it never asked for a certain tape and I never received a mount request
either. I know this all seems very bizarre.  I really don't know how to
justify what happened.  Thanks!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



"Cook, Dwight
E"   To: [EMAIL PROTECTED]
   Subject: Re: TSM migration problem & 
recovery log question???
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


01/14/2003
09:20 AM
Please respond
to "ADSM: Dist
Stor Manager"






Because of internal locks that aren't being readily resolved.
Look for a client (or clients) that have been connected for a long time
(say
4-6+ hours)
Also look for other things like expiration, reclamation, migration, etc...
processes that might be running also.
Might only been client sessions though...
Anyway, generally (I've discovered) the log won't clear until those long
running clients either finish normally OR I cancel them.
We have had to increase some of our log sizes to 6 GB (6144 MB) in order to
allow things to run to completion and not have our log fill up and cause
sessions to die off due to log space being exhausted.

Now, media inaccessible, how is your library attached ?
I've noticed (in the past) that if the library manager can't talk to TSM
(or
tsm can't talk to the library manager) AND tsm requires a tape mount (which
fails because of lack of communication) even though I restored
communications to the library, I would still have to bounce TSM to get it
to
start talking to the library again...
Is there something that is causing a loss of communications with your
library prior to this "media not available" situation ?
When things fail due to media not available does it report a specific
volser
?
When things are bounced and start working again, does the problem volser
(if
identified) become accessible ?

Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 7:23 AM
To: [EMAIL PROTECTED]
Subject: TSM migration problem & recovery log question???


The recovery log on TSM is 95% full.  I do a full DB backup everyday, which
I thought would reset the log to 0%.  It is in normal mode, not
rollforward.  Why would it be so high when I just did a full backup last
night that ended at 9 PM.  The log right now is 4.6 GB with 4.2 GB
utilized.  Any suggestions?

We have TSM 4.1.3 on OS/390.  My other problem is that our disk storage
pool filled to 100%, getting message anr1021w: media inaccessible.  When
trying to force migration (which should've occurred automatically) the
processes still failed with the media inaccessible messages.  We were not
in tape drive allocation and plenty of scratch volumes were available.  No
messages in the logs even pointed to a specific tape that was being called
in.  Bouncing the tsm server triggered one of four possible migration
processes.  Around 8 hours after bouncing the server 4 migration processes
finally did kick off after hitting the set threshold.  Any ideas or insight
as to what the problem could be???

Thanks for any help,

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



Re: restoring exchange in seperate environment

2003-01-14 Thread Mark Stapleton
On Tue, 2003-01-14 at 09:18, Tuyl Adrie, A.C. van wrote:
> What is the safest way to restore an exchange server in a seperate
> environment (to extract one mailbox for instance).
> My Exchange Administrator doesn't have full confidence that the method
> described in the manual, i.e. restoring in the same domain, but without
> joining an existing site is safe. He's afraid of double connectors, double
> mail etc, double servers in the site etc.

It is absolutely safe, as long as you follow the instructions in the TDP
for Exchange manual. I've done it (or seen it done) a dozen times. Your
Exchange administrator needs to read the MS docs on this process; it's
well documented.

--
Mark Stapleton ([EMAIL PROTECTED])



Re: TSM migration problem & recovery log question???

2003-01-14 Thread Joni Moyer
I really don't know what is wrong with the recovery log.  There are no
clients that have been connected to the server for more than 4 minutes.  I
have a backup of a primary tape pool to a copy tape pool running 1 process.
Other than that everything is silent.  I can't seem to get the log to clear
to 0% and soon I'll have to add more space which will take it to 6 GB for
the recovery log.  I am still baffled about this.

We have TSM on the mainframe and it is attached to STK silos with 3590
magstar tapes.  As far as I know communication wasn't lost because other
migrations/backups etc. were running.  I was just having problems with 1
out of 3 of my disk storage pools migrating to tape.  I looked through the
logs trying to find out what tape it might have been trying to migrate to,
but it never asked for a certain tape and I never received a mount request
either. I know this all seems very bizarre.  I really don't know how to
justify what happened.  Thanks!!!

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



"Cook, Dwight
E"   To: [EMAIL PROTECTED]
   Subject: Re: TSM migration problem & 
recovery log question???
Sent by:
"ADSM: Dist
Stor Manager"
<[EMAIL PROTECTED]
IST.EDU>


01/14/2003
09:20 AM
Please respond
to "ADSM: Dist
Stor Manager"






Because of internal locks that aren't being readily resolved.
Look for a client (or clients) that have been connected for a long time
(say
4-6+ hours)
Also look for other things like expiration, reclamation, migration, etc...
processes that might be running also.
Might only been client sessions though...
Anyway, generally (I've discovered) the log won't clear until those long
running clients either finish normally OR I cancel them.
We have had to increase some of our log sizes to 6 GB (6144 MB) in order to
allow things to run to completion and not have our log fill up and cause
sessions to die off due to log space being exhausted.

Now, media inaccessible, how is your library attached ?
I've noticed (in the past) that if the library manager can't talk to TSM
(or
tsm can't talk to the library manager) AND tsm requires a tape mount (which
fails because of lack of communication) even though I restored
communications to the library, I would still have to bounce TSM to get it
to
start talking to the library again...
Is there something that is causing a loss of communications with your
library prior to this "media not available" situation ?
When things fail due to media not available does it report a specific
volser
?
When things are bounced and start working again, does the problem volser
(if
identified) become accessible ?

Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 7:23 AM
To: [EMAIL PROTECTED]
Subject: TSM migration problem & recovery log question???


The recovery log on TSM is 95% full.  I do a full DB backup everyday, which
I thought would reset the log to 0%.  It is in normal mode, not
rollforward.  Why would it be so high when I just did a full backup last
night that ended at 9 PM.  The log right now is 4.6 GB with 4.2 GB
utilized.  Any suggestions?

We have TSM 4.1.3 on OS/390.  My other problem is that our disk storage
pool filled to 100%, getting message anr1021w: media inaccessible.  When
trying to force migration (which should've occurred automatically) the
processes still failed with the media inaccessible messages.  We were not
in tape drive allocation and plenty of scratch volumes were available.  No
messages in the logs even pointed to a specific tape that was being called
in.  Bouncing the tsm server triggered one of four possible migration
processes.  Around 8 hours after bouncing the server 4 migration processes
finally did kick off after hitting the set threshold.  Any ideas or insight
as to what the problem could be???

Thanks for any help,

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



restoring exchange in seperate environment

2003-01-14 Thread Tuyl Adrie, A.C. van
Hi Storage experts,

What is the safest way to restore an exchange server in a seperate
environment (to extract one mailbox for instance).
My Exchange Administrator doesn't have full confidence that the method
described in the manual, i.e. restoring in the same domain, but without
joining an existing site is safe. He's afraid of double connectors, double
mail etc, double servers in the site etc.

Do you have any experience with this?

Is there a method of restoring only the edb's and tracking log file's?


TSM Server 4.2.2.6 Windows NT
TDP for Exchange 2.2.0.0
BA Client 4.2.2.0

Regards, Adrie van Tuyl


This e-mail and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this e-mail in error, please notify
[EMAIL PROTECTED]
This footnote also confirms that this e-mail message has been checked by
McAfee Groupshield for the presence of computer viruses.




Exclude Question

2003-01-14 Thread Amini, Mehdi
Below is the copy of DSM.OPT file for our SMS Server...As you can see I have
excluded D:\SMS folder from backing up and yet in the morning when I look at
the Log...it shows me this folder being backed up.What is wrong here:


* IBM Adstar Distributed Storage Manager
*
* Sample dsm.opt for 32-Bit Windows backup and archive Client - V3 level
*
* See options.wri for complete options file documentation


*
* TCP/IP
*

commmethod  tcpip
tcpport  
TCPServeraddress XXX.XXX.XXX.XXX

*
* ipx/spx
*

*
* netbios
*

*commmethod   netbios
*netbiosname   client1
*netbiosservername ntserver1

*
* named pipes
*

*commmethod namedpipe
namedpipename \\.\pipe\adsmpipe



* COMPression
*
* +--+--+
* | COMPression  | ON|OFf   |
* +--+--+
* System default: OFf
*
* Option file example:
*
 COMPression ON
* COMPression OFf




* DOMain
*
* +--+--+
* | DOMain   | ALL-LOCAL|domain |
* +--+--+
* System default: ALL-LOCAL
*
* Options file examples:
*
* DOMain ALL-LOCAL Q:




* EXclude and INclude
*
* +--+--+
* | EXclude  | pattern  |
* +--+--+
* | INclude  | pattern  |
* +--+--+
*
* EXclude and INclude patterns are written using an extended pattern
* match language.  This language uses the native operating system's
* metacharacters (wildcards) whenever possible.  A list of the
* supported metacharacters for the match language follows:
*
*   Function   AIX   DOS  OS/2
*   -     -
*   Match one character? ??
*   Match n characters * **
*   Match n directories/... (1)  \... (1) \...  (1)
*   Directory Separator/ \\
*   Open Character Class   [[(1) [(1)
*   Character Class Range  - -(1) - (1)
*   Close Character Class  ]](1) ](1)
*   Literal Escape \ \(1) \ (1)
*   Drive Separatornone  ::
*
*


*Exclude *:\IBMBIO.COM
*Exclude *:\IBMDOS.COM
*Exclude *:\MSDOS.SYS
*Exclude *:\IO.SYS
*Exclude *:\...\SYSTEM32\CONFIG\*.*
*Exclude *:\...\SYSTEM32\CONFIG\...\*




* NodeName
*
* +--+--+
* | MACHinename  | client_name  |
* +--+--+
* Default:  Netbios Name (NT/Win95 Computer name)
*
* Option file example:
*
* MACHinename


NODENAME XXX
password  XX


* REPlace
*
* +--+--+
* | REPlace  | Yes|No|Prompt|
* +--+--+
* System default: Prompt
*
* Option file example:
*
* REPlace N
* REPlace Y




* SUbdir
*
* +--+---

Re: TSM migration problem & recovery log question???

2003-01-14 Thread Cook, Dwight E
Because of internal locks that aren't being readily resolved.
Look for a client (or clients) that have been connected for a long time (say
4-6+ hours)
Also look for other things like expiration, reclamation, migration, etc...
processes that might be running also.
Might only been client sessions though...
Anyway, generally (I've discovered) the log won't clear until those long
running clients either finish normally OR I cancel them.
We have had to increase some of our log sizes to 6 GB (6144 MB) in order to
allow things to run to completion and not have our log fill up and cause
sessions to die off due to log space being exhausted.

Now, media inaccessible, how is your library attached ?
I've noticed (in the past) that if the library manager can't talk to TSM (or
tsm can't talk to the library manager) AND tsm requires a tape mount (which
fails because of lack of communication) even though I restored
communications to the library, I would still have to bounce TSM to get it to
start talking to the library again...
Is there something that is causing a loss of communications with your
library prior to this "media not available" situation ?
When things fail due to media not available does it report a specific volser
?
When things are bounced and start working again, does the problem volser (if
identified) become accessible ?

Dwight E. Cook
Software Application Engineer III
Science Applications International Corporation
509 S. Boston Ave.  Suite 220
Tulsa, Oklahoma 74103-4606
Office (918) 732-7109



-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 7:23 AM
To: [EMAIL PROTECTED]
Subject: TSM migration problem & recovery log question???


The recovery log on TSM is 95% full.  I do a full DB backup everyday, which
I thought would reset the log to 0%.  It is in normal mode, not
rollforward.  Why would it be so high when I just did a full backup last
night that ended at 9 PM.  The log right now is 4.6 GB with 4.2 GB
utilized.  Any suggestions?

We have TSM 4.1.3 on OS/390.  My other problem is that our disk storage
pool filled to 100%, getting message anr1021w: media inaccessible.  When
trying to force migration (which should've occurred automatically) the
processes still failed with the media inaccessible messages.  We were not
in tape drive allocation and plenty of scratch volumes were available.  No
messages in the logs even pointed to a specific tape that was being called
in.  Bouncing the tsm server triggered one of four possible migration
processes.  Around 8 hours after bouncing the server 4 migration processes
finally did kick off after hitting the set threshold.  Any ideas or insight
as to what the problem could be???

Thanks for any help,

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



Re: Why my library doesn't compress data?

2003-01-14 Thread Cook, Dwight E
So to me that indicates that your clients are probably compressing the data.
Here are examples from some of my environments...
Volume Name   Storage  Device  EstimatedPct   Volume
  Pool NameClass Name   Capacity   Util   Status
(MB)
  ---  --  -  -

AAA025PR3590   3590DEVC  9,262.5  100.0Full
AAA0313590P1   3590DEVC  9,150.4  100.0Full
AAA042PR3590   3590DEVC  9,170.1  100.0Full
AAA0493590P1   3590DEVC  9,194.0  100.0Full
AAA0553590P1   3590DEVC  9,080.6  100.0Full
AAA0633590P1   3590DEVC  9,142.9  100.0Full
AAA0663590P1   3590DEVC  9,210.3  100.0Full
...
AAA1433590P1   3590DEVC 15,914.5   95.7Full
AAA45510YRARCH 3590DEVC 40,000.02.8  Filling
AAB04710YRARCH 3590DEVC 20,000.06.3  Filling
AAB0783590P1   3590DEVC 10,240.0   43.5  Filling
AAB12810YRARCH 3590DEVC 40,000.04.7  Filling
AAB1523590P1   3590DEVC 10,240.0   11.9  Filling
AAB918ARCHLOGTPEC  3590DEVC 10,240.0   72.3  Filling
AAC836PR3590   3590DEVC 10,240.0   74.4  Filling
AAF2753590P1   3590DEVC 22,485.5  100.0  Filling
AAF35910YRARCHCP   3590DEVC 10,000.0   74.1  Filling

OK, now this might look odd but I'll explain where things come from
Used to I never assigned a "Est/Max Capacity (MB)" in my environments.
Back with older 3590 tape drivers, the driver estimated the capacity at
10,000MB as is seen with volume AAF359.
When new technology came out (and an associated driver, and remember newer
drivers support the older devices)
anyway, the default estimated capacity changed to 20,000MB as seen in volume
AAB047.
Once again, new stuff came out and new drivers were installed and the
default capacity changed to 40,000MB as seen in volume AAA455.
Now, since this environment was still the old 3590-B1A tape drives with old
"J" series tapes, the base capacity was still only 10 GB (aka 10,000MB).
Once I became tired of seeing all these 20,000MB's & 40,000MB's in an
enviroment that was actually 10,000MB I assigned a value of 10,240 MB to the
"Est/Max Capacity (MB)" for device class 3590DEVC (see volumes like AAB078).
Now, that estimated capacity value is assigned when a scratch volume becomes
private AND doesn't change until the volume either becomes full (see AAA143)
OR the amount of data written to it exceeds the estimated capacity (see
AAF275).
So with all this said, what I can say about the above tapes is...
Tapes like AAF359 were first written to back long ago (about 2 tape driver
levels ago).
Tapes like AAB047 were first written to back sort of long ago (about 1 tape
driver level ago).
Tapes like AAB128 were first written recently (on the current tape driver
level) but prior to me setting the "Est/Max Capacity (MB)" for the device
class 3590devc.
Tapes like AAC836 were first written very recently (on the current tape
driver level) after I got tired of seeing false information being reported
and set the "Est/Max Capacity (MB)" to 10,240 MB.
Tapes like AAA066 probably contain ONLY client data that was compressed at
the client... because when the tape drive attempts to compress the already
compressed data, it actually grows, thus these tapes don't hold their
reported 10 GB (because the 10 GB read from disk grows when written to tape
but the value reported by TSM is the amount that was pulled from disk to put
on the tape).
Tapes like AAA143 lets me know that 1 or more clients aren't doing as they
have been requested and are NOT using TSM client compression... because the
compression at the tape drive actually reduced its size. (and we know
already compressed data grows with attempted further compression)


Dwight



-Original Message-
From: Elio Vannelli [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 14, 2003 2:27 AM
To: [EMAIL PROTECTED]
Subject: Re: Why my library doesn't compress data?


Thanks for your answer.
The problem is that TSM marks the tape as 1MB while the tape is
FILLING. When the volume is FULL TSM says 6500MB. I don't have only
*.zip in my 250GB file server, but a lot of *.pdf, *.doc, images, CAD
files, ...
None of the 40 volumes marked as FULL reaches 7GB.

Thanks in advance

Elio Vannelli



TSM migration problem & recovery log question???

2003-01-14 Thread Joni Moyer
The recovery log on TSM is 95% full.  I do a full DB backup everyday, which
I thought would reset the log to 0%.  It is in normal mode, not
rollforward.  Why would it be so high when I just did a full backup last
night that ended at 9 PM.  The log right now is 4.6 GB with 4.2 GB
utilized.  Any suggestions?

We have TSM 4.1.3 on OS/390.  My other problem is that our disk storage
pool filled to 100%, getting message anr1021w: media inaccessible.  When
trying to force migration (which should've occurred automatically) the
processes still failed with the media inaccessible messages.  We were not
in tape drive allocation and plenty of scratch volumes were available.  No
messages in the logs even pointed to a specific tape that was being called
in.  Bouncing the tsm server triggered one of four possible migration
processes.  Around 8 hours after bouncing the server 4 migration processes
finally did kick off after hitting the set threshold.  Any ideas or insight
as to what the problem could be???

Thanks for any help,

Joni Moyer
Systems Programmer
[EMAIL PROTECTED]
(717)975-8338



write errors with tsm 5.1.5.4 and TDP for oracle

2003-01-14 Thread Marcel J.E. Mol
Hello,

We have got this LANfree backup setup using the TSM Storage Agent.
We experience some strange write error on a tape in combination with the
Oracle TDP as can be seen in the actlog below.

Nugvas03 is the storageagent. It mounts a tape (volume 100031 at 07:19:05)
and a while later we see it unmounts it (at 07:22:35).
After that a write error occurs (07:23:58) for volume 100031  accompanied
with an error from nugvas03 (07:24:01).
Does anybody understands what is happening here?

TSM server and StorageAgent 5.1.5.4
Client and API 5.1.5.5
TDP for Oracle 2.2.1.0

Thanks

-Marcel

01/14/03   07:19:05  ANR8337I (Session: 5542, Origin: NUGVAS03_SRV)  LTO volume 
100031 mounted in drive DRIVE0 (/dev/rmt2).
01/14/03   07:21:39  ANR8325I (Session: 5542, Origin: NUGVAS03_SRV) Dismounting 
volume 100031 - 1 minute mount retention expired.
01/14/03   07:21:44  ANR8336I (Session: 5542, Origin: NUGVAS03_SRV)  Verifying 
label of LTO volume 100031 in drive DRIVE0 (/dev/rmt2).
01/14/03   07:22:33  ANR0406I Session 5708 started for node NUGVAS03_ORA (TDP 
Oracle AIX) (Tcp/Ip 172.21.32.18(64660)).
01/14/03   07:22:33  ANR0408I Session 5709 started for server NUGVAS03_SRV 
(AIX-RS/6000) (Tcp/Ip) for library sharing.
01/14/03   07:22:33  ANR8336I Verifying label of LTO volume 100031 in drive DRIVE0 
(/dev/rmt0).
01/14/03   07:22:33  ANR0403I Session 5708 ended for node NUGVAS03_ORA (TDP Oracle 
AIX).
01/14/03   07:22:35  ANR8468I (Session: 5542, Origin: NUGVAS03_SRV)  LTO volume 
100031 dismounted from drive DRIVE0 (/dev/rmt2) in library 3584LIB.

01/14/03   07:23:21  ANR0406I Session 5726 started for node NUGVAS03_ORA (TDP 
Oracle AIX) (Tcp/Ip 172.21.32.18(64717)).
01/14/03   07:23:22  ANR3605E Unable to communicate with storage agent.
01/14/03   07:23:22  ANR0479W Session 3981 for server NUGVAS03_SRV (AIX-RS/6000) 
terminated - connection with server severed.
01/14/03   07:23:22  ANR0403I Session 5726 ended for node NUGVAS03_ORA (TDP Oracle 
AIX).
01/14/03   07:23:55  ANR0406I Session 5727 started for node NUGVAS03_ORA (TDP 
Oracle AIX) (Tcp/Ip 172.21.32.18(64736)).
01/14/03   07:23:55  ANR0406I Session 5728 started for node NUGVAS03_ORA (TDP 
Oracle AIX) (Tcp/Ip 172.21.32.18(64737)).
01/14/03   07:23:55  ANR1639I Attributes changed for node NUGVAS03_ORA: TCP 
Address from  to 172.21.32.18.
01/14/03   07:23:58  ANRD pvrntp.c(1595): ThreadId<39> Position value 12 not 
expected size (48).
01/14/03   07:23:58  (39) Context report
01/14/03   07:23:58  (39) AgentThread : ANRD calling thread
01/14/03   07:23:58  (39) Generating TM Context Report: (struct=tmTxnDesc) 
(slots=256)
01/14/03   07:23:58  (39)  *** no transactions found ***
01/14/03   07:23:58  (39) Generating Database Transaction Table Context:
01/14/03   07:23:58  (39)  *** no transactions found ***
01/14/03   07:23:58  (39) Generating SM Context Report:
01/14/03   07:23:58  (39)  *** no sessions found ***
01/14/03   07:23:58  (39) Generating AS Vol Context Report:
01/14/03   07:23:58  (39)  No mounted (or mount in progress) volumes.
01/14/03   07:23:58  (39) Generating ssSession Context Report:
01/14/03   07:23:58  (39)  No storage service sessions active.
01/14/03   07:23:58  (39) Generating ssOpenSeg Context Report:
01/14/03   07:23:58  (39)  No storage service segments found.
01/14/03   07:23:58  (39) Generating BF Copy Control Context Report:
01/14/03   07:23:58  (39)  No global copy control blocks.
01/14/03   07:23:58
01/14/03   07:23:58  (39) End Context report
01/14/03   07:23:58  ANR1411W Access mode for volume 100031 now set to "read-only" 
due to write error.
01/14/03   07:23:58  ANR0523W Transaction failed for session 5727 for node 
NUGVAS03_ORA (TDP Oracle AIX) - error on output storage device.
01/14/03   07:24:01  ANE4994S (Session: 5727, Node: NUGVAS03_ORA)  TDP Oracle AIX 
ANU0599 TDP for Oracle: (94632): => (nugvas03_ora) ANS1315E (RC15)   Unexpected Retry 
request
01/14/03   07:24:11  ANR0403I Session 5727 ended for node NUGVAS03_ORA (TDP Oracle 
AIX).
01/14/03   07:28:02  ANR8336I Verifying label of LTO volume 100031 in drive DRIVE0 
(/dev/rmt0).
01/14/03   07:28:35  ANR8468I LTO volume 100031 dismounted from drive DRIVE0 
(/dev/rmt0) in library 3584LIB.

--
 == Marcel J.E. MolMESA Consulting B.V.
===-ph. +31-(0)6-54724868  P.O. Box 112
===-[EMAIL PROTECTED] 2630 AC  Nootdorp
__ www.mesa.nl ---U_n_i_x__I_n_t_e_r_n_e_t The Netherlands 
 They couldn't think of a number,   Linux user 1148  --  counter.li.org
so they gave me a name!  -- Rupert Hine  --  www.ruperthine.com



Antwort: Re: TSM Server Version 4.2.3.0

2003-01-14 Thread Markus Veit
Hi Leif,
thanks, I'll remember it for next time.

Best Regards

Markus Veit







An: [EMAIL PROTECTED]
Kopie:
Thema:   Re: TSM Server Version 4.2.3.0

  [EMAIL PROTECTED]
  Received :  14.01.2003
  12:35
  Bitte antworten an "ADSM:
  Dist Stor Manager"






Instead of /patches/, look at /maintenance/.

/Leif

- Original Message -
From: "Markus Veit" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 12:29 PM
Subject: TSM Server Version 4.2.3.0


> Hi all,
> where would I find the download for TSM 4.2.3.0 server so I can Update to
> 4.2.3.2. from 4.2.1.9. The fileset requires base level 4.2.3.0.
> OS AIX 4.3.3 ML10
> It's not here
>
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/
AIX/
> Best Regards and thanks
> Markus
>



TSM Server Version 4.2.3.0

2003-01-14 Thread Markus Veit
Hi all,
where would I find the download for TSM 4.2.3.0 server so I can Update to
4.2.3.2. from 4.2.1.9. The fileset requires base level 4.2.3.0.
OS AIX 4.3.3 ML10
It's not here
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/AIX/
Best Regards and thanks
Markus



Re: TSM Server Version 4.2.3.0

2003-01-14 Thread Leif Gustafsson Giga Consulting AB
Instead of /patches/, look at /maintenance/.

/Leif

- Original Message -
From: "Markus Veit" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, January 14, 2003 12:29 PM
Subject: TSM Server Version 4.2.3.0


> Hi all,
> where would I find the download for TSM 4.2.3.0 server so I can Update to
> 4.2.3.2. from 4.2.1.9. The fileset requires base level 4.2.3.0.
> OS AIX 4.3.3 ML10
> It's not here
>
ftp://ftp.software.ibm.com/storage/tivoli-storage-management/patches/server/
AIX/
> Best Regards and thanks
> Markus
>



Re: Error during "delete volhistory"

2003-01-14 Thread John Naylor
Paul,
You could try
del volh tod=today vol=xx type=backupset force=yes
(only the first volume in sequence is required the others will delete
automatically)




Paul Ripke <[EMAIL PROTECTED]> on 01/13/2003 06:58:04 AM

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

To:   [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject:  Error during "delete volhistory"



Anyone know how to delete multi-volume backupsets from volhistory?
BTW, server is 4.1.3.0 (waiting on my spare time for an upgrade...)

tsm: BHPS>q volhist ty=backupset

   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 1
Device Class: 3590
 Volume Name: SP0064
 Volume Location:
 Command: generate backupset ISDWOL-ES2 es2-fdrive \\isdwol-es2\f$
devcla=3590 scrat=y retent=90

   Date/Time: 09/19/02   12:34:34
...
   Date/Time: 09/19/02   12:34:34
 Volume Type: BACKUPSET
   Backup Series:
Backup Operation:
  Volume Seq: 9
Device Class: 3590
 Volume Name: SP0469
 Volume Location:
 Command:

Actlog output looks ominous:
ANR2017I Administrator WERIPP issued command: DELETE VOLHISTORY
typ=backupset volu=SP0064 force=yes todate=today
ANRD tb.c(2029): Invalid Encoded Key Length
ANR0106E imarqry.c(3069): Unexpected error 100 fetching row in table
"Archive.Descriptions".
ANRD icvolhst.c(3473): Volume SP0064 initially found no longer exists
during volume deletion.
ANR2468E DELETE VOLHISTORY: An internal server error was encountered while
deleting server sequential volume history information.
ANR2017I Administrator WERIPP issued command: ROLLBACK

Tried first and last tape of the series, with same results.
A comma-separated list generated a "no such volume" type error.

Cheers,
--
Paul Ripke
UNIX/OpenVMS Sysadmin
CSC, Port Kembla 2502, NSW, Australia
Phone +61 2 4275 4101
Fax +61 2 4275 7801
Mobile +61 419 432 517
101 reasons why you can't find your Sysadmin:
68. It's 9 AM. He/she is not working that late.
-- Koos van den Hout



This email, including any attachments, is intended only for use by the
addressee(s) and may contain confidential and/or personal information and
may also be the subject of legal privilege. Any personal information
contained in this email is not to be used or disclosed for any purpose
other than the purpose for which you have received it. If you are not the
intended recipient, you must not disclose or use the information contained
in it. In this case, please let me know by return email, delete the message
permanently from your system and destroy any copies.









**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely for the addressees. Access to this E-Mail by
anyone else is unauthorised. If you are not the intended recipient,
any disclosure, copying, distribution or any action taken or omitted
to be taken in reliance on it, is prohibited and may be unlawful.
Any unauthorised recipient should advise the sender immediately of
the error in transmission.

Scottish Hydro-Electric, Southern Electric, SWALEC and S+S
are trading names of the Scottish and Southern Energy Group.
**



Re: Remove from list

2003-01-14 Thread Farren Minns
Hi Daniel

You need to send the following message

UNSUBSCRIBE ADSM-L

To the following email address

[EMAIL PROTECTED]

Cheers

Farren - John Wiley & Sons Ltd



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

Sent by:        "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:        [EMAIL PROTECTED]
cc:
Subject:        Remove from list


Regards,
Daniel B.






Remove from list

2003-01-14 Thread Bouenos, Daniel
Regards,
Daniel B.



Remove

2003-01-14 Thread Bouenos, Daniel
Regards,
Daniel B.


-Original Message-
From: Jim Sporer [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 13, 2003 11:29 PM
To: [EMAIL PROTECTED]
Subject: Re: label/checkin libvolume

Can't you just do a checkout with remove=no and then label the tapes?
Jim Sporer

At 01:16 PM 1/13/2003 -0800, you wrote:
> > -Original Message-
> > From: Cook, Dwight E [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, January 13, 2003 11:58 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: label/checkin libvolume
> >
> > Well, TSM doesn't want to label them while they are PRIVATE
> > and TSM doesn't
> > really know what is going on...
> > You might be able to do a del vol against them to get them
> > back to scratch,
> > then do your label libvol
>
>Dwight-
>
>Thank you for the reply.  I did try deleting them, but they are not part
>of a storage pool, so they cannot be "deleted" (and there is no "delete
>libvolume" command).  I updated a couple of the volumes to scratch, just
>as a test.  After updating them, I tried:  "label libvol 
>search=yes checkl=barcode checkin=scr overwrite=yes
>volrange=,".  However, TSM reports 0 volumes labelled and
>exits with "Success".
>
>The only other thing I can think to do is to go to the library and
>physically remove them.  Once removed, audit the library to show TSM that
>they are no longer in the library. Then, load them back in and check them
>in correctly.
>
>Any other ideas?  Thanks.
>Peter



Re: Objects compressed by

2003-01-14 Thread Zlatko Krastev/ACIT
Why not - same Oracle server data (about 200 GB) compressed by IBM 3583
got approx 2:1 while using node-compression got 3.4-3.5:1.
Another customer case - 600 GB DB (cold backup, no TDP involved) had to go
to DLT and achieved again 2.2:1 compression. Switching to diskpool with
node-compression relieved DLT drives contention and as side effect
improved compression ratio. Compressed data was 130 GB initially and grew
up to 160 GB over months. Thus the ratio was 4.6:1 going down to 3.75:1
but is still much higher than 2:1.
Another usage of node-compression is when you have to backup a lot (Nx
10^5 - 10^6) of small files. Drives cannot stream very well but compressed
data sent over LAN and aggregated by TSM server streams better. Again
performance benefit.
Completely agree with the argument - this highly depends on backup case
and data contents. And I am using node-compression only on mighty servers
- 6, 8 or more processors. The results are very pleasant. You can look
also Dwight's results on E10k - 20 processors can feed even Gb Ether with
compressed data.

Zlatko Krastev
IT Consultant






Mark Stapleton <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
13.01.2003 22:32
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: Objects compressed by


On Thu, 2003-01-09 at 07:11, Zlatko Krastev/ACIT wrote:
> Yes, usually TSM node-compression gets better compression ratio that
tape
> drive compression.

I'd like to see figures on this. My experience has been that
hardware-based compression is both faster and more efficient than
software-based compression.

--
Mark Stapleton ([EMAIL PROTECTED])



Re: TSM message formatting

2003-01-14 Thread Sheelagh Treweek
I reported this as a PMR a little while ago.  The APAR is IC34754
and I understand it may be fixed in approximately 6 months time.

It seems to corrupt all Q PROC output in the same way.

Best wishes, Sheelagh
--

Sheelagh Treweek
Oxford University Computing Services
Email: [EMAIL PROTECTED]
Phone: +44 (0)1865 273205 Fax:-273275



X-Sender: [EMAIL PROTECTED]
Mime-Version: 1.0
X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang)
Date: Thu, 9 Jan 2003 15:51:10 -0500
From: Chet Osborn <[EMAIL PROTECTED]>
Subject: TSM message formatting
To: [EMAIL PROTECTED]

Hi,

We just upgraded from TSM server version 4.2.3.0 to version 5.1.5.4 on and
RS/6000 running AIX 4.3.3. Everything seems OK, except for  the output from
"query proc". E.g.,

tsm: RPIADSM_1>quer proc

  Process Process Description  Status
   Number
  -
1 Space ReclamationVolume A00717 (storage pool RCS3494), Moved
Files: 15054, Moved Bytes: 812,243,048,
Unreadable Files: 0, Unreadable Bytes: 0.
Current Physical File (bytes):
1,201,741~Current
input volume: A00717.~Current output volume:
A00055.\

Presumably, the "~" and "\" are not meant to be part of the text. Looking
through the output of "query system",  I don't see anything else that looks
strange. Anyone have any idea what's going on here?
Thanks.

Chet Osborn
Systems Programmer
NT/Central Servers
Rensselaer Polytechnic Institute



Re: Why my library doesn't compress data?

2003-01-14 Thread Christian Svensson

   
   
   


Hi Elio
I have´nt read the convesation but I have this problem before on a customer
site.
And we saw that the OS has enable filesystem compressen.

And what I know is that compressen + compressen is decompresstion.

If it not the OS has compressen the files watch out for compressed files
like
Zip, Arj, Rar, Pdf, MP3, Mdb (And another databas files).
This kind of files is can take alot of space on the tapes.

Another idea is that. Is you runing hardware compressen? on your tape
drives?
If you do that. Don´t run any software compressen then. Becuse the tape can
compress the file much better then software.
And I say it agien. Compressen + Compressen = decompressed.

Try this three ideas first. If it still don´t work. Send me a email and i
figurout some more idea what is can be.

Med Vänliga Hälsningar/Best Regards
Christian Svensson

---

Cristie Nordic AB
Box 2
SE-131 06 Nacka
Sweden

Phone : +46-(0)8-641 96 30
Mobil : +46-(0)70-325 15 77
eMail : [EMAIL PROTECTED]
MSN : [EMAIL PROTECTED]


   
   
  Elio Vannelli  cc:
   
  Sent by: "ADSM: Dist Stor Subject:  Re: Why my library 
doesn't compress data?   
  Manager"   
   
   
   
   
   
  2003-01-14 09:27 
   
  Please respond to "ADSM: 
   
  Dist Stor Manager"   
   
   
   
   
   




Thanks for your answer.
The problem is that TSM marks the tape as 1MB while the tape is
FILLING. When the volume is FULL TSM says 6500MB. I don't have only
*.zip in my 250GB file server, but a lot of *.pdf, *.doc, images, CAD
files, ...
None of the 40 volumes marked as FULL reaches 7GB.

Thanks in advance

Elio Vannelli


 - Original Message: -
Date:Mon, 13 Jan 2003 08:26:04 -0800
From:"Cook, Dwight E" <[EMAIL PROTECTED]>
Subject: Re: Why my library doesn't compress data?

OK... TSM will estimate the capacity of a device/media pair based on
what you set with the device class definition and if nothing is
specified there, it will be based on what the ~driver~ reports, THIS IS
WHILE A VOLUME IS FILLING. Now what is actually shown as the capacity
once the volume is FULL is what has been written to the tape. What does
all of this mean ? I'd say the 6500MB is close to your stated 7 GB
native capacity... if you do a "q dev f=d" and see "Est/Max Capacity
(MB)" as blank, the 6500 is being provided by the device driver and that
is where it is coming from... Now the 21 GB is an ~estimated at 3/1
compression" and if your full volumes show only about 12-13 GB that
means that either you have uncompressed cliient that doesn't compress
very well OR you have a mixture of compressed & uncompressed (at the
client) client data. Basically when a tape's EndOfTape marker is
reached, TSM assigns a capacity equal to what it has written to that
specific tape. If you front end things with a diskpool, the amount
reported on a tape is what was read from the disk and put on the tape.
Client compressed data doesn't reduce at the tape drive with tape drive
compression SO if all your client data came into your tsm server as
~client compressed~, I'd expect the capacity of FULL tapes to  be about
7 GB. If all your data came in from your clients uncompressed AND it
were all Oracle DB file type data I'd expect your FULL volumes to be
about 21-22 GB. If any of the data is something like a .zip file or
other type of already compressed data outside tsm client compression, it
won't compress

Re: Why my library doesn't compress data?

2003-01-14 Thread Elio Vannelli
Thanks for your answer.
The problem is that TSM marks the tape as 1MB while the tape is
FILLING. When the volume is FULL TSM says 6500MB. I don't have only
*.zip in my 250GB file server, but a lot of *.pdf, *.doc, images, CAD
files, ...
None of the 40 volumes marked as FULL reaches 7GB.

Thanks in advance

Elio Vannelli


 - Original Message: -
Date:Mon, 13 Jan 2003 08:26:04 -0800
From:"Cook, Dwight E" <[EMAIL PROTECTED]>
Subject: Re: Why my library doesn't compress data?

OK... TSM will estimate the capacity of a device/media pair based on
what you set with the device class definition and if nothing is
specified there, it will be based on what the ~driver~ reports, THIS IS
WHILE A VOLUME IS FILLING. Now what is actually shown as the capacity
once the volume is FULL is what has been written to the tape. What does
all of this mean ? I'd say the 6500MB is close to your stated 7 GB
native capacity... if you do a "q dev f=d" and see "Est/Max Capacity
(MB)" as blank, the 6500 is being provided by the device driver and that
is where it is coming from... Now the 21 GB is an ~estimated at 3/1
compression" and if your full volumes show only about 12-13 GB that
means that either you have uncompressed cliient that doesn't compress
very well OR you have a mixture of compressed & uncompressed (at the
client) client data. Basically when a tape's EndOfTape marker is
reached, TSM assigns a capacity equal to what it has written to that
specific tape. If you front end things with a diskpool, the amount
reported on a tape is what was read from the disk and put on the tape.
Client compressed data doesn't reduce at the tape drive with tape drive
compression SO if all your client data came into your tsm server as
~client compressed~, I'd expect the capacity of FULL tapes to  be about
7 GB. If all your data came in from your clients uncompressed AND it
were all Oracle DB file type data I'd expect your FULL volumes to be
about 21-22 GB. If any of the data is something like a .zip file or
other type of already compressed data outside tsm client compression, it
won't compress at the drive either and that can cause variations in what
the capacity is reported on FULL volumes.

whew, my explanation isn't very pretty but does it clear things up a bit
???

Dwight



Re: OSX Mac Client Question

2003-01-14 Thread Farren Minns
So, the Scheduler Daemon provided does not actually work?

This machine is actually a server in our secure comms room, so it's not a
big issue and I assume the manual scheduler does not add significant
overhead to the machine resources. It will do until they iron out all
problems I guess.

Thanks

Farren Minns - John Wiley & Sons Ltd



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

Sent by:        "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To:        [EMAIL PROTECTED]
cc:
Subject:        Re: OSX Mac Client Question


Yes, IBM does have a ways to go with the Tivoli Storage Manager client
for Mac OS X. It does work, and the last couple updates have taken care
of very critical problems. The major problem that remains is that the
Scheduler (which is the agent that communicates with the server and
facilitates scheduled backups) is an interactive application and cannot
run in the background. This means that you have to be logged in at the
console as an admin user in order for the Scheduler to work. If this is
the type of machine where there's only one or two admins, and you're
comfortable using something like a screensaver password to protect the
console, then TSM can work quite well. The reason for this issue is
that IBM essentially carbonized the old Mac OS version, keeping the
single user paradigm. The client is being completely rewritten by IBM,
and a version that has a scheduler capable of running as a background
process will be available this year.

Jim Sporer


At 04:00 PM 1/13/2003 +, you wrote:
>Hi TSMers
>
>I've just installed the latest client release for a Mac OSX machine. I can
>run backups/restores no problem and can run the scheduler manually. When I
>run the scheduler as a daemon though, the dsmsched.log file shows that the
>daemon contacted the server for the next schedule, but then it says
>'Scheduler stopped'. Is this correct? I would expect to see something like
>'Schedule will be refreshed in 1 hour'.
>
>Anyone out there have experience with the OSX clients?
>
>Thanks
>
>Farren Minns - John Wiley & Sons Ltd