Error on Version 5.1.5 Client

[Robert Ouzen]

Hi

I installed a new version client 5.1.5 on Windows XP  and got when running a
gui backup this error message:

ANS0106E Read index: Message index not found for message 15257

The backup after it run successfully (included restore ...)

Please advice ... Regards

Robert Ouzen
Helpdesk Manager Computing Division
Haifa University
E-mail: [EMAIL PROTECTED] 

Re: Error on Version 5.1.5 Client

[Kurt Beyers]

Just reinstall the client, some files weren't installed properly.

- Original Message -
From: "Robert Ouzen" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, December 25, 2002 8:11 AM
Subject: Error on Version 5.1.5 Client


> Hi
>
> I installed a new version client 5.1.5 on Windows XP  and got when running
a
> gui backup this error message:
>
> ANS0106E Read index: Message index not found for message 15257
>
> The backup after it run successfully (included restore ...)
>
> Please advice ... Regards
>
> Robert Ouzen
> Helpdesk Manager Computing Division
> Haifa University
> E-mail: [EMAIL PROTECTED] 
>
>

Dominique Costantini/ITServices/Unicible est absent(e).

[Dominique Costantini]

Je serai absent(e) du  23.12.2002 au 29.12.2002.

Je répondrai à votre message dès mon retour. Voir avec PHL si besoin.Merci.

ATTN: WINDOWS CLIENT USERS

[Andrew Raibeck]

Two Windows client fixtests, 5.1.5.4 and 5.1.5.6, have been removed from
the FTP server because of a potential data corruption problem with online
LAN image backups only, and only on Windows 2000 with those two fixtests.
The 5.1.5.0 PTF and 5.1.5.2 fixtest do not contain the problem.

Windows client 5.1.5.6 fixtest (package name IP22546_06) and 5.1.5.4
fixtest (package name IP22546_04) have been removed from the FTP server,
because our internal testing detected a potential data corruption problem
with certain Online LAN Image Backups with these fixtest levels only, for
the Windows client only. APAR IC35333 has been opened for this problem,
and it will be fixed in fixtest 5.1.5.7.

Customers should re-backup the online LAN image backups made with those
two fixtests, using either an older level client or the new 5.1.5.7 client
(when it is available) to do the re-backups.

The Windows client 5.1.5.4 fixtest (package name IP22546_04) was also
removed because it can cause an abend in the API client. The API client is
used by other processes, such as the IBM TSM for Mail or Database
products. The problem is described by APAR IC35271, and it is only a
problem in Windows client fixtest 5.1.5.4. It is fixed in 5.1.5.7 (when
available), and customers can use older level API clients as well.

If you have already downloaded and applied fixtests 5.1.5.4 or 5.1.5.6 for
the Windows client, please go back to the 5.1.5.2 or earlier level now,
and then replace your client with the 5.1.5.7 or later Windows client
fixtest (package name IP22546_07 or later) when it becomes available.

We are sorry for the inconvenience. Fixtests are meant to help customers
with critical problems that can't wait for the next fully-tested
deliverable. We do test fixtests, but in a more limited fashion which did
not detect these side effect problems of other fixes. For the future, we
are working to improve our fixtest testing.

I will make a post when the 5.1.5.7 client is available (currently
targeted for Friday, January 3).

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

Re: Client code upgrade

[Zlatko Krastev]

That's why IBM Tivoli Configuration Manager (former Tivoli Software
Distribution) is made for. And there are many other similar products on
the market. This can be a long discussion irrelevant to this list so you
can contact me directly.

Zlatko Krastev
IT Consultant






"Macmurray, Andrea (CAG-CC)" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
18.12.2002 22:33
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Client code upgrade


We are planning to upgrade all our clients to V5.1.5. My question is if
there is some way to distribute the client code to all our NT clients
automatically. We have several hundert clients and upgrading client code
is
a stable fight with my NT admins, they are plain getting tired of me
asking
twice a year to upgrade.
Help would be appreciated
Thanks
Andrea Mac Murray

Re: Comm timeout value

[Zlatko Krastev]

You are already having the value too high. Do not mess commtimeout with
idletimeout.
Commtimeout is for client-server conversation. In LAN environment default
value of 60 (seconds) ought to be more than enough. For WAN links it may
need to be increased but I will not go beyond 150-180 sec.
Idletimeout is for sessions doing nothing to be cancelled by the server.
For long running backups (several hours) the collector thread's session
might be cancelled by the server. Increase of this option's value to the
length of longest backup might be a workaround. But even for it the value
of 1500 (it is measured in minutes) is too high - more than 24 hours.

You are having some network problem and the best way ought to be
discussion with your network admin.

--> ... The most I have seen out here posted is the 1500 ...

Number 1500 gets too often in list postings but as default TSM server port
not as commtimeout option setting !?!

Zlatko Krastev
IT Consultant






"Anderson, Michael - HMIS" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
23.12.2002 21:33
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Comm timeout value


As of right now the communications time out on my TSM server is
1500. I still get some time outs every so often, so
I would like to increase it. The most I have seen out here posted is
the
1500, is there some formula for this, or is it hit and
   miss.  I am running TSM ver 4.2.3 on AIX 4.3.3. Any suggestions
appreciated

Mike Anderson
[EMAIL PROTECTED]


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

Re: Difference between Archive & Selective

[Richard Sims]

>I have an AIX client running very slow backups, we have been looking into a
>couple of things, when we noticed something strange. If we run an archive on
>the box instead of a selective backup the speed improves by like 4 times...

So many factors...apples, oranges, and grapefruit.  Various affecters, including
software level, may be involved.  In particular, keep the following in mind
(from my notes):

Selective Backup, more overhead thanRunning a Selective Backup can be
 Archiveexpected to entail more overhead than a
comparable Archive operation, in that
more complex retention policies are
involved in Backup policies than in
Archive. Remember that Archive retention
is based purely upon time, whereas
Backup involves both time and versions
decisions. File expiration candidates
processing based upon versions (number
of same file) is performed during client
Backups (in contrast to time-based
retention rules, which are processed
during a later, separate Expiration).
The more versions you keep, the more
work the server is distracted with at
Backup time.
  Richard Sims, BU

Re: Slow tape to tape performance...

[Richard Sims]

>I am getting agonizingly slow (~1GB/hr) performance on tape to tape copies
>(such as during reclamations).

What experiments have you performed to try to narrow down the problem?
What results do you see in an experiment where data is copied between the
same two tape drives outside of TSM?
Given the cost of FC adapters, is it the case that you have one, and
you are seeing "tidal action" as drive-to-drive copies are performed?
As Kelly suggested, the driver level for the FC adapter may greatly
affect performance.  I presume that you are seeing this performance
problem with all tapes?  Marginal tape samples can result in a lot of
retries, and degraded performance.  Don't overlook microcode level on
the drives: some mc levels are bow-wows.

  Richard Sims, BU

Re: Gigabit Ethernet speed

[Kelly J. Lipp]

What kind of performance are you seeing?

I would expect a number greater than 20,000 KB/sec as reported by a client
summary.

I also would expect it to be highly variable and dependent on client speed.
I believe that Gig E is going to be faster than just about anything else in
all but the highest end systems so suspect a bottleneck elsewhere.

As with 100 Mbit networks, duplex and link speed incompatibilities are
killers.  100/1000 full is the way to go.  Stay away from Auto unless you
have un-managed network switches.

Thanks,

Kelly

Kelly J. Lipp
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Conko, Steven
Sent: Tuesday, December 24, 2002 7:44 AM
To: [EMAIL PROTECTED]
Subject: Gigabit Ethernet speed


anybody have any tips on what type of "Network transfer rate" we should be
seeing for our backups over gigabit ethernet? the clients backup via copper
Gb ethernet dedicated for backups to a tsm server connected to a 3494 tape
library with 10 3590 tape drives via fibre channel/brocade switch.

there is only one client on one gigabit interface and 3 on another.

any tips for improving network performance?

thanks

Steven A. Conko
Senior Unix Systems Administrator
ADT Security Services, Inc.

Re: Slow tape to tape performance...

[Kelly J. Lipp]

Performance is good when writing from disk to tape?  How good?  When I hear
of this I suspect driver issues.  I know on Win2K driver selection is
paramount when having a performance problem with tape.

Kelly J. Lipp
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
[EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com or www.storserver.com
(719)531-5926
Fax: (240)539-7175


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Remeta, Mark
Sent: Tuesday, December 24, 2002 10:08 AM
To: [EMAIL PROTECTED]
Subject: Re: Slow tape to tape performance...


do you have tape drive compression and client compression turned on?
I've seen this before with AIT drives trying to compress already compressed
data...



-Original Message-
From: Wheelock, Michael D [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 11:33 AM
To: [EMAIL PROTECTED]
Subject: Slow tape to tape performance...


Hi,

I am getting agonizingly slow (~1GB/hr) performance on tape to tape copies
(such as during reclamations).  Is this normal?  This is a new install,
fairly fresh with some basic policies and copy groups.  The server is an AIX
5.1 ML02 7026-M80 with 8GB RAM.  The tape library is an IBM 3584 with 8 FC
attached LTO drives.  TSM is at 5.1.5.4.  Any ideas would be appreciated.

Michael Wheelock
Integris Health of Oklahoma

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: restores

[Zlatko Krastev]

Burak,

I recall you asked the same question in May.
You cannot achieve what you want but you can get something close. Set
MAXNUMMP=0 for all "offending" nodes. Backups should go to disk and server
will migrate data to tape. Restores from diskpool ought not to hurt you.
For the node you want to "allow" restore you may increase maxnummp or use
"move nodedata".

Zlatko Krastev
IT Consultant






Burak Demircan <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
24.12.2002 10:45
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:restores


hi,
how can i disable restores under normal conditions and allow some node
to restore at any time i want? but this shouldn't prevent daily backup
schedules.
regards,



Burak Demircan
CEO / ITT
MERCEDES-BENZ TURK A.S.

[EMAIL PROTECTED]
tel:+90 212 482 35 00 (4676)
fax :+90 212 481 11 54

Re: TDP R/3

[Zlatko Krastev]

Bill,

main portion of the R/3 data is within the RDBMS (be it DB2, Oracle or
other) but not *all*! You can perform online backup of the DB2 database
but it will be out of sync with R/3 activity and other data. The result -
you may get an inconsistent backup, restore will be down an unsupported
way (and you will be on your own), etc. Without ITSM for ERP (former TDP
for R/3) you will not be able to use R/3 tools.

Zlatko Krastev
IT Consultant






Bill Zhang <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
20.12.2002 18:01
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:TDP R/3


Can somebody explain me why use TDP for R/3 to backup
SAP DB2 database while you can backup DB2
offline/online directly to TSM?
What are the binifits?

Thanks a lot.

Bill

__
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com

Re: synthetic fullbackup

[Zlatko Krastev]

---> ... I don't know if this is necessary or not.

It is not necessary and will not help (you may even lose performance if
several drives are available). TSM server is smart enough and even without
collocation setting each process will migrate data for separate node (to
separate tape). With collocation enabled, when only one node's data is in
the diskpool you will have only one migration process despite the diskpool
settings.

Zlatko Krastev
IT Consultant






"Ford, Phillip" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
20.12.2002 20:47
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: synthetic fullbackup


Make the tape pool "collocation enabled" and do a migration on the disk
pool
(update stg diskpool hi=0 low=0).  Also helps to have migration process
set
to 1 for the disk pool.  I don't know if this is necessary or not.



--
Phillip Ford
Senior Software Specialist
Corporate Computer Center
Schering-Plough Corp.
(901) 320-4462
(901) 320-4856 FAX
[EMAIL PROTECTED]

Re: BackupSet on CD?

[Zlatko Krastev]

You have to define FILE class and set maxcap less than CD size. The data
will be split in several TSM volumes (files) and each volume will go on
separate CD.
Have in mind that volume label of the CD must match the filename (TSM
volume label). Look at TSM Administrator's Reference (v5.1 for AIX,
GC32-0769-00, p.174):
"The label on the media must meet the following restrictions:
- No more than 11 characters
- Same name for file name and volume label "
This might not be problem for local backupset restores but is mandatory
for server backupsets over devclass with type REMOVABLEFILE. DirectCD
creates random CD volume label beginning with creation date. This label
will not match TSM volume label.

Zlatko Krastev
IT Consultant






Murthy V Gongala <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
21.12.2002 09:36
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: BackupSet on CD?


The size of the Backup set files generated will be more what a single CD
can hold.
Do we have to generate files which a CD can hold.
Is there a CD Burning Software available which can write to multiple CD's
for a single file image.

TIA
regards
murthy



I am sure this question has come across before, I just can't seem to find
the answer.

I would like to generate a set of CDs as a backupset for a client.

How do I go about this?

Current environment is TSM 4.2.3.1 on Win2K.

TIA ... Jack

Re: Apparent memory leak

[William F. Colwell]

Tom, I have seen the server get sluggish after running a long time,
and I suspect a memory leak was the cause.  I can't remember if 4.2.1.9
had the problem.  I am at 4.2.3.2 and it is running good.

Bill

At 11:37 AM 12/24/2002, you wrote:
>We are running a 4.2.1.9 TSM server under OS/390. We started seeing
>crippling performance problems when the database got up around 15
>gigabytes. Increases in bufpoolsize, region size, and available real
>memory (by shifting memory from another logical partition on the
>same processor complex) had only a temporary effect. It now appears
>that each time we stop and restart the server we get about one day
>of pretty good performance, followed by a day of margional performance,
>followed by one or more days of catostrophic performance. The buffer
>pool hit rate seems to decrease steadily after each restart. This
>pattern of behavior suggests a memory leak. Does the 4.2.1.9 server
>have known problems in this regard?

--
Bill Colwell
C. S. Draper Lab
Cambridge Ma.

Difference between Archive & Selective

[Anderson, Michael - HMIS]

I have an AIX client running very slow backups, we have been looking
into a couple of things, when we noticed something
 strange. If we run an archive on the box instead of a selective backup
the speed improves by like 4 times. It went from over six
 hours down to just over an hour. The numbers on the files inspected and
backed up look the same. Has anybody else seen
 anything like this? The server level is 4.2.3. on aix 4.3.3  client is
4.2.2.1 on aix 4.3.3

 Mike Anderson
 [EMAIL PROTECTED]


CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.

Re: TSM Policy Model

[Andrew Raibeck]

D'oh! Don't know what I was thinking, of course you are correct. And yes,
while this is theoretically possible, it's not something that most users
would wish to do.

Thanks!

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Robert L. Rippy" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/24/2002 11:31
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Re: TSM Policy Model



How would the files expire once you deleted them off the server if you had
unlimited retention? Wouldn't that negate the necessity for unlimited
retention? I was only showing that it could be done, but I wouldn't
suggest
it.

Thanks,
Robert Rippy.



From: Andrew Raibeck <[EMAIL PROTECTED]> on 12/24/2002 11:31 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

Even unlimited copies/retention wouldn't guarantee this: if someone
deleted a bunch of files on their client drive, then they will be expired
during the next incremental backup. If the deleted files happen to
comprise 95% of a tape, the voile! you now have a full volume with only 5%
valid data.

The best way to deal with this is to be more aggressive with reclamation,
i.e. set the storage pool's reclamation threshold to something like 60 or
75 rather than 90 or 95. But the trade-off is that you will be doing
reclamation more frequently. Since reclamation uses TSM server resources
(tape drives, CPU, etc.), you'll have to balance your reclamation needs
with other TSM management requirements.

In general, I would recommend reading the Admin Guide from cover to cover
(if you haven't done so already) to familiarize yourself with how TSM
works. In particular, you can read up on reclamation in the chapter on
"Managing Storage Pools and Volumes".

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.


-Original Message-
From: Robert L. Rippy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 10:28 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Policy Model


Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay
full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <[EMAIL PROTECTED]> on 12/24/2002 10:23 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you
have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.

Re: TSM Policy Model

[Robert L. Rippy]

How would the files expire once you deleted them off the server if you had
unlimited retention? Wouldn't that negate the necessity for unlimited
retention? I was only showing that it could be done, but I wouldn't suggest
it.

Thanks,
Robert Rippy.



From: Andrew Raibeck <[EMAIL PROTECTED]> on 12/24/2002 11:31 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

Even unlimited copies/retention wouldn't guarantee this: if someone
deleted a bunch of files on their client drive, then they will be expired
during the next incremental backup. If the deleted files happen to
comprise 95% of a tape, the voile! you now have a full volume with only 5%
valid data.

The best way to deal with this is to be more aggressive with reclamation,
i.e. set the storage pool's reclamation threshold to something like 60 or
75 rather than 90 or 95. But the trade-off is that you will be doing
reclamation more frequently. Since reclamation uses TSM server resources
(tape drives, CPU, etc.), you'll have to balance your reclamation needs
with other TSM management requirements.

In general, I would recommend reading the Admin Guide from cover to cover
(if you haven't done so already) to familiarize yourself with how TSM
works. In particular, you can read up on reclamation in the chapter on
"Managing Storage Pools and Volumes".

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.


-Original Message-
From: Robert L. Rippy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 10:28 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Policy Model


Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay
full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <[EMAIL PROTECTED]> on 12/24/2002 10:23 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you
have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.

Re: ---URGENT! migration of yearly went to wrong pool

[Remeta, Mark]

Yes just backup the stgpool you migrated the data to to the offsitepool.
This will backup all the data on the next stgpool though, not just the stuff
you migrated off last.


-Original Message-
From: Taha, Hana [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 12:18 PM
To: [EMAIL PROTECTED]
Subject: ---URGENT! migration of yearly went to wrong pool


--HELP !
---I took yearly backups last night and archived them for a year. But the
migration utility ---migrated them to backuppool instead of offsite pool.
How can I get these copied off of ---backuppool to offsite pool now?

---This is what I wanted to kick off: "backup stgpool 8mmexpool offsitepool"

---But this schedule was the one that kicked off first:" UPDATE STG
BACKUPPOOL HI=0"

---Is there a way to move them from BACKUPPOOL to offsitepool?

---Thanks in advance to all!

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

---URGENT! migration of yearly went to wrong pool

[Taha, Hana]

--HELP !
---I took yearly backups last night and archived them for a year. But the
migration utility ---migrated them to backuppool instead of offsite pool.
How can I get these copied off of ---backuppool to offsite pool now?

---This is what I wanted to kick off: "backup stgpool 8mmexpool offsitepool"

---But this schedule was the one that kicked off first:" UPDATE STG
BACKUPPOOL HI=0"

---Is there a way to move them from BACKUPPOOL to offsitepool?

---Thanks in advance to all!

Re: Slow tape to tape performance...

[Remeta, Mark]

do you have tape drive compression and client compression turned on?
I've seen this before with AIT drives trying to compress already compressed
data...



-Original Message-
From: Wheelock, Michael D [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 11:33 AM
To: [EMAIL PROTECTED]
Subject: Slow tape to tape performance...


Hi,

I am getting agonizingly slow (~1GB/hr) performance on tape to tape copies
(such as during reclamations).  Is this normal?  This is a new install,
fairly fresh with some basic policies and copy groups.  The server is an AIX
5.1 ML02 7026-M80 with 8GB RAM.  The tape library is an IBM 3584 with 8 FC
attached LTO drives.  TSM is at 5.1.5.4.  Any ideas would be appreciated.

Michael Wheelock
Integris Health of Oklahoma

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Apparent memory leak

[Thomas Denier]

We are running a 4.2.1.9 TSM server under OS/390. We started seeing
crippling performance problems when the database got up around 15
gigabytes. Increases in bufpoolsize, region size, and available real
memory (by shifting memory from another logical partition on the
same processor complex) had only a temporary effect. It now appears
that each time we stop and restart the server we get about one day
of pretty good performance, followed by a day of margional performance,
followed by one or more days of catostrophic performance. The buffer
pool hit rate seems to decrease steadily after each restart. This
pattern of behavior suggests a memory leak. Does the 4.2.1.9 server
have known problems in this regard?

Re: TSM Policy Model

[Andrew Raibeck]

Even unlimited copies/retention wouldn't guarantee this: if someone
deleted a bunch of files on their client drive, then they will be expired
during the next incremental backup. If the deleted files happen to
comprise 95% of a tape, the voile! you now have a full volume with only 5%
valid data.

The best way to deal with this is to be more aggressive with reclamation,
i.e. set the storage pool's reclamation threshold to something like 60 or
75 rather than 90 or 95. But the trade-off is that you will be doing
reclamation more frequently. Since reclamation uses TSM server resources
(tape drives, CPU, etc.), you'll have to balance your reclamation needs
with other TSM management requirements.

In general, I would recommend reading the Admin Guide from cover to cover
(if you haven't done so already) to familiarize yourself with how TSM
works. In particular, you can read up on reclamation in the chapter on
"Managing Storage Pools and Volumes".

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.


-Original Message-
From: Robert L. Rippy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 10:28 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Policy Model


Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay
full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <[EMAIL PROTECTED]> on 12/24/2002 10:23 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you
have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.

Slow tape to tape performance...

[Wheelock, Michael D]

Hi,

I am getting agonizingly slow (~1GB/hr) performance on tape to tape copies
(such as during reclamations).  Is this normal?  This is a new install,
fairly fresh with some basic policies and copy groups.  The server is an AIX
5.1 ML02 7026-M80 with 8GB RAM.  The tape library is an IBM 3584 with 8 FC
attached LTO drives.  TSM is at 5.1.5.4.  Any ideas would be appreciated.

Michael Wheelock
Integris Health of Oklahoma

Re: Reclamation not reclaiming carts

[Michael Raine]

Thanks...
All cart have an access of onsite or offsite.  The data is intact.
The data can be manually moved but reclamation will not move it or tell me why.








Richard Sims <[EMAIL PROTECTED]> on 12/23/2002 07:44:08 PM

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








 To:  [EMAIL PROTECTED]

 cc:  (bcc: Michael Raine/NOTES)



 Subject: Re: Reclamation not reclaiming carts








>There are no errors in the acticity log.  Once the reclamation process is
>started the tapes are selected/listed in the activity log but not reclaimed.
>It appears to recognize the tape is available for reclamation but does not even
>mount the tape.
>Collocate is on and there are hundreds of tapes with the same STG.
>Some of the tapes are 99.9% even reclaimable.

In my experience, with large storage pools it can take a while for Reclamation
to initiate - perhaps longer than the window that it is alloted by server
administration commands.

I presume that the subject volumes themselves have good Access values, which
allow them to be mounted and reclaimed?
If you are not already doing so, you must perform regular administrative
queries on your resources to catch those which have gotten bad Access and State
values.  (Do regular 'Query Volume Access=Destroyed',
'Query Volume Access=Reado Stat=Fill', 'Query Volume Access=Unavail', etc.)
This can allow you to discover victim and culprit conditions before they get
out of hand.

The small occupation exhibited by your tapes may involve storage pool files
which span volumes, and reclamation may not be happening because the volume that
the files span to/from are in a state which precludes their use.  I would begin
by performing 'Query CONtent  F=D' on the least occupied volumes,
looking for Segment numbering other than 1/1 in the first and/or last files,
which indicates spanning from/to other volumes.  The aforementioned queries will
help prevent and detect such conditions.

  Richard Sims, BU



All electronic communications, including company provided email, are the sole
property of Allfirst.  This system may not be used to transmit, receive or
download solicitations or offensive, vulgar or otherwise disruptive messages or
materials, including, but not limited to, those that violate Allfirst's policies
regarding Equal Employment Opportunity and Sexual Harassment.  All messages
transmitted by or received through the Allfirst email system shall be regarded
as non-personal, business communications.  Employees are reminded to only use
this system for legitimate business purposes.  Allfirst reserves the right to
monitor, intercept and retrieve electronic communications in the normal course
of business.

loaddb performance

[Thomas Denier]

We have a 4.2.1.9 TSM server running under OS/390. The database has been
getting bigger and performance has been getting worse. We decided to run
a test to see how long it would take to dump and reload the database. We
ran a 'prepare' command to create a recovery plan based on our onsite
database backup. We modified the output to use a different set of
dataset names and volumes for recreating the server. We also modified
the server options in the recovery plan to use a different TCP/IP stack
and to remove the volume deletion exit. We needed to use a different
stack because we wanted to run the recovery jobs under a different
OS/390 image. This eliminated most resource contention between the
recreated server and the production server. It also enable us to rule
out some nerve-wracking scenarios involving attempts to use the same
devices. We executed 'vary' commands to prevent the recreated server
from getting access to the tape drives used by the production server
and the disks containing production storage pool volumes. Once we
recreated the server, we ran a full backup of the database. We then
ran dumpdb, loadformat, and loaddb jobs modeled after the samples in
the back of the "Administrator's Reference". We specified a 384
megabyte region size rather than the 128 megabytes in the samples.
I attended an IBM presentation on TSM performance a couple of years
ago. The speaker indicated that dumpdb would run at about 6 gigabytes
per hour and that loaddb would be somewhat slower. The dumpdb job
actually did better than the prediction, dumping 15 gigabytes in just
under two hours. The loadformat job took about 15 minutes. The loaddb
job ran for 17 hours, reporting progress at a rate that extrapolated
to finishing in about 4 days. To me, the phrase "somewhat slower" does
not suggest a factor of 50 increase in running time. Is there something
we could have done to get the loaddb performance more nearly comparable
to the dumpdb performance?

Re: TSM Policy Model

[Richard Sims]

>Where can I find some documented examples of TSM policies for backup and
>archive operations ?

Have you read through the Administrator's Guide?  It fully details all
aspects of the product, with examples.

Re: TSM Policy Model

[Remeta, Mark]

I would not recommend it either. I would recommend reading some TSM
documentation to get a better understanding of the way the product works.
Depending on how much data he backs up on a nightly basis this would make
his database grow quite fast. Not to mention the number of tapes he would go
through.
Having a tape full with 5% of data on it is not a bad thing, it just means
you need to reclaim that volume.



-Original Message-
From: Robert L. Rippy [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 24, 2002 10:28 AM
To: [EMAIL PROTECTED]
Subject: Re: TSM Policy Model


Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <[EMAIL PROTECTED]> on 12/24/2002 10:23 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.








Mario Behring
IT Consultant
55 11 9540-8383
[EMAIL PROTECTED]


-
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: TSM Policy Model

[Robert L. Rippy]

Its possible. Just create retention policies that retain unlimited copies
with a nolimit retention. That way once a volume is full, it will stay full
because nothing will expire. Not that I would recommend it, but it is
possible.

Thanks,
Robert Rippy.



From: "Remeta, Mark" <[EMAIL PROTECTED]> on 12/24/2002 10:23 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: TSM Policy Model

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.








Mario Behring
IT Consultant
55 11 9540-8383
[EMAIL PROTECTED]


-
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Re: TSM Policy Model

[Remeta, Mark]

That is impossible. It's the way TSM works.


-Original Message-
From: Mario Behring [mailto:[EMAIL PROTECTED]]
Sent: Sunday, December 22, 2002 4:39 PM
To: [EMAIL PROTECTED]
Subject: TSM Policy Model


Hi list,

Where can I find some documented examples of TSM policies for backup and
archive operations ?

I have to create a policy that does not create the situation where you have
a tape with only 5% of real data stored and 95% marked for reclamation.

Thanks.








Mario Behring
IT Consultant
55 11 9540-8383
[EMAIL PROTECTED]


-
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

Confidentiality Note: The information transmitted is intended only for the
person or entity to whom or which it is addressed and may contain
confidential and/or privileged material. Any review, retransmission,
dissemination or other use of this information by persons or entities other
than the intended recipient is prohibited. If you receive this in error,
please delete this material immediately.

Gigabit Ethernet speed

[Conko, Steven]

anybody have any tips on what type of "Network transfer rate" we should be
seeing for our backups over gigabit ethernet? the clients backup via copper
Gb ethernet dedicated for backups to a tsm server connected to a 3494 tape
library with 10 3590 tape drives via fibre channel/brocade switch.

there is only one client on one gigabit interface and 3 on another.

any tips for improving network performance?

thanks

Steven A. Conko
Senior Unix Systems Administrator
ADT Security Services, Inc.

Re: Backup stops abruptely - rc=933

[Andrew Raibeck]

This is IC33280.

- For 4.2 clients: fixed in 4.2.2 and up
- For 5.1 clients: fixed in 5.1.1 and up

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED] (change eye to i to reply)

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.




"Lambelet,Rene,VEVEY,GL-CSC" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
12/24/2002 06:58
Please respond to "ADSM: Dist Stor Manager"


To: [EMAIL PROTECTED]
cc:
Subject:Backup stops abruptely - rc=933



Hi,
have you experienced such incomplete incremental, following this error
message ?

12/24/2002 05:34:22 PrivIncrFileSpace: Received rc=933 from
fioGetDirEntries:  \\hqvevw04\f$  \Users\aboulet\Nestle
12/24/2002 05:34:23 ANS4987E Error processing '\\hqvevw04\f$ ': the object
is in use by another process

Instead of skipping the file in error, TSM quit the incr, giving rc 4 for
the schedule. We run 4.2.1.20 w2k client onto server 4.2.1.15.

Very annoying as only 400'000 files got inspected on a total of 900'000.
Bypass consists of a temporary exclude.dir of '\Users\aboulet\Nestle'

Any advice ?

I wish you all a merry Christmas Eve,

R. Lambelet, Nestle Vevey

Re: Backup stops abruptely - rc=933

[Robert L. Rippy]

Run a CHKDSK of the drive and you will probally find some problems there
that is causing TSM to stop. I've ran into something similar like this
before.

Thanks,
Robert Rippy.




From: "Lambelet,Rene,VEVEY,GL-CSC" <[EMAIL PROTECTED]> on 12/24/2002
  08:58 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Backup stops abruptely - rc=933

Hi,
have you experienced such incomplete incremental, following this error
message ?

12/24/2002 05:34:22 PrivIncrFileSpace: Received rc=933 from
fioGetDirEntries:  \\hqvevw04\f$  \Users\aboulet\Nestle
12/24/2002 05:34:23 ANS4987E Error processing '\\hqvevw04\f$ ': the object
is in use by another process

Instead of skipping the file in error, TSM quit the incr, giving rc 4 for
the schedule. We run 4.2.1.20 w2k client onto server 4.2.1.15.

Very annoying as only 400'000 files got inspected on a total of 900'000.
Bypass consists of a temporary exclude.dir of '\Users\aboulet\Nestle'

Any advice ?

I wish you all a merry Christmas Eve,

R. Lambelet, Nestle Vevey

Backup stops abruptely - rc=933

[Lambelet,Rene,VEVEY,GL-CSC]

Hi,
have you experienced such incomplete incremental, following this error
message ?

12/24/2002 05:34:22 PrivIncrFileSpace: Received rc=933 from
fioGetDirEntries:  \\hqvevw04\f$  \Users\aboulet\Nestle
12/24/2002 05:34:23 ANS4987E Error processing '\\hqvevw04\f$ ': the object
is in use by another process

Instead of skipping the file in error, TSM quit the incr, giving rc 4 for
the schedule. We run 4.2.1.20 w2k client onto server 4.2.1.15.

Very annoying as only 400'000 files got inspected on a total of 900'000.
Bypass consists of a temporary exclude.dir of '\Users\aboulet\Nestle'

Any advice ?

I wish you all a merry Christmas Eve,

R. Lambelet, Nestle Vevey

Timo Kilchenmann, Bechtle Data AG ist abwesend.

[Kilchenmann Timo]

Ich werde ab  24.12.2002 nicht im Büro sein. Ich kehre zurück am
06.01.2003.

Die E-Mail wurde nicht weitergeleitet!

Re: Error deleting volume

[Robert L. Rippy]

Try updating the volume to READO and then run 'AUDIT VOLUME 'volume name'
FIX=Y' then try 'DELETE VOLUME 'volume name' DISCARDDATA=YES'
that might work for you.

Thanks,
Robert Rippy.




From: Mario Behring <[EMAIL PROTECTED]> on 12/22/2002 07:03 PM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Error deleting volume

Hi list,

I have several volumes (tape) that I cannot manage to delete. The volumes
status are all set to DESTROYED and the physical tapes does not exist
anymore. The error message I get when I try to delete the volume (delete
vol  discarddata=YES wait=NO) is the following:

ANR0104E imarins.c(1503): Error deleting row from table
"Archive.Descriptions"

I had found some explanations at the Ask Tivoli website, but none could
solve my problem.

Thanks in advance.




Mario Behring
IT Consultant
55 11 9540-8383
[EMAIL PROTECTED]


-
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

Re: Data expire on tape simple question

[Robert L. Rippy]

If the storage pool that the volume belongs to has a reuse delay of 0 then
the volume will goto empty and then return to scratch. Else, it will goto
PENDING and wait until those days pass then goto empty.

Thanks,
Robert Rippy.



From: Tony W <[EMAIL PROTECTED]> on 12/24/2002 07:37 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Data expire on tape simple question

Hello Advancer
i have a simple question:
A tape(volume) status=full or filling access=readonly. if my wait someday
then 100% data expire,The tsm server will automatic change status=empty or
not?

Thank you:)
Tony W

Data expire on tape simple question

[Tony W]

Hello Advancer
i have a simple question:
A tape(volume) status=full or filling access=readonly. if my wait someday
then 100% data expire,The tsm server will automatic change status=empty or
not?

Thank you:)
Tony W

Re: Reclamation not reclaiming carts

[Robert L. Rippy]

Try this process:

Run QUERY CONTENT on the volumes that won't reclaim and see if it comes
back with 'No Data'. If so then change the volume to READO, run AUDIT
VOLUME 'volume name' FIX=YES. Then DELETE VOLUME 'volume name'
DISCARDDATA=yes'  BUT ONLY IF VOLUME CONTENT CAME BACK WITH NO DATA.

Thanks,
Robert Rippy



From: Michael Raine <[EMAIL PROTECTED]> on 12/23/2002 10:27 AM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  Re: Reclamation not reclaiming carts

Thanks.
There are no errors in the acticity log.  Once the reclamation process is
started the tapes are selected/listed in the activity log but not
reclaimed.  It
appears to recognize the tape is available for reclamation but does not
even
mount the tape.
Collocate is on and there are hundreds of tapes with the same STG.
Some of the tapes are 99.9% even reclaimable.









"Miller, Ryan" <[EMAIL PROTECTED]> on 12/20/2002 03:01:59 PM

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








 To:  [EMAIL PROTECTED]

 cc:  (bcc: Michael Raine/NOTES)



 Subject: Re: Reclamation not reclaiming carts








Are there errors in the activity log associated with why they won't
reclaim?  or
are they have not just reclaimed yet?  do you have a reclamation process
running?  also, do you collocate, if so is it possible that this is the
only
tape associated with a node and can't reclaim?  lots of issues to look at
here...

Ryan Miller

Principal Financial Group

Tivoli Certified Consultant
Tivoli Storage Manager v4.1


-Original Message-
From: Michael Raine [mailto:[EMAIL PROTECTED]]
Sent: Friday, December 20, 2002 1:47 PM
To: [EMAIL PROTECTED]
Subject: Re: Reclamation not reclaiming carts


Thanks...

Ran audit vol and no errors were found.  The funny thing is that
reclamation
realizes the carts have space to reclaim because it identifies them
in the activity log but will not move the data.

Currently I am moving the data manually but this process will take awhile
as
there are over a hundred carts like this.









"Wayne T. Smith" <[EMAIL PROTECTED]> on 12/20/2002 02:37:26 PM

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








 To:  [EMAIL PROTECTED]

 cc:  (bcc: Michael Raine/NOTES)



 Subject: Re: Reclamation not reclaiming carts








You might try doing an AUDIT VOLUME on each.

Michael Raine wrote:
> When running reclamation have the reclaim pct for the STG at 60%.
>
> Have several volumes meeting this requirement but TSM does not reclaim
the
data.
>   It recognized the carts in the activity log but does not reclaim the
space.

Holiday cheers, wayne
--

Wayne T. Smith -- [EMAIL PROTECTED] -- University of Maine System -- UNET



All electronic communications, including company provided email, are the
sole
property of Allfirst.  This system may not be used to transmit, receive or
download solicitations or offensive, vulgar or otherwise disruptive
messages or
materials, including, but not limited to, those that violate Allfirst's
policies
regarding Equal Employment Opportunity and Sexual Harassment.  All messages
transmitted by or received through the Allfirst email system shall be
regarded
as non-personal, business communications.  Employees are reminded to only
use
this system for legitimate business purposes.  Allfirst reserves the right
to
monitor, intercept and retrieve electronic communications in the normal
course
of business.



All electronic communications, including company provided email, are the
sole
property of Allfirst.  This system may not be used to transmit, receive or
download solicitations or offensive, vulgar or otherwise disruptive
messages or
materials, including, but not limited to, those that violate Allfirst's
policies
regarding Equal Employment Opportunity and Sexual Harassment.  All messages
transmitted by or received through the Allfirst email system shall be
regarded
as non-personal, business communications.  Employees are reminded to only
use
this system for legitimate business purposes.  Allfirst reserves the right
to
monitor, intercept and retrieve electronic communications in the normal
course
of business.

Re: auditdb question

[Robert L. Rippy]

I have ran many many auditdb's and it has never once asked me to insert a
volume so that it can compare that info with the database. I belive it will
not volumes to compare information. If that was the case then IBM would
allow for more information on this subject like..."Be sure you have every
volume ever written to available incase the auditdb asks for it." The audit
doesn't actually audit volumes to compare against the database, that is
what AUDIT VOLUME is for.

Thanks
Robert Rippy




From: Mario Behring <[EMAIL PROTECTED]> on 12/22/2002 07:16 PM

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

To:   [EMAIL PROTECTED]
cc:
Subject:  auditdb question

Hi list,

I am under the impression that a "dsmserv auditdb fix=yes logmode=normal
detail=yes" will not only fix inconsistencies in the TSM database but will
also ask for volumes to compare information from the physical tapes with
the database. Is this correct ?

The environment is TSM Server 5.1 runnig on a W2K box and a SCSI tape
library, an IBM 3590 with two drives and 10 slots each. So, if the TSM
Server asks for a tape that is not in one of the twenty slots, an operator
will insert it into the proper slot.

I have several volume tapes that does not exists anymore and have a
destroyed status and cannot be deleted (error ANR0104E) and no audit have
been performed in the database for three years.

Please give some advise on this matter.

Thank you.




Mario Behring
IT Consultant
55 11 9540-8383
[EMAIL PROTECTED]


-
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now

restores

[Burak Demircan]

hi, 
how can i disable restores under normal conditions and allow some node 
to restore at any time i want? but this shouldn't prevent daily backup 
schedules. 
regards,



Burak Demircan
CEO / ITT 
MERCEDES-BENZ TURK A.S. 

[EMAIL PROTECTED] 
tel:+90 212 482 35 00 (4676) 
fax :+90 212 481 11 54