You can easyly proof you tape theorie by makeing an backupset on the TSM
serverdisk
and doing the same restore. There should be a significant difference if
that's true.
WR Stefan Holzwarth
-Ursprüngliche Nachricht-
Von: Mark Bryant [mailto:[EMAIL PROTECTED]]
Gesendet am: Donnerstag,
We have a problem with a file system in HSM, maybe somebody knows it
already.
Server- AIX 4.1.5.0 - ADSM 3.1.2.20
Client Solaris 2.6 - ADSM 3.1.0.8 with HSM 3.1.0
1)Firstly I add space management to one of the file systems as below and the
message is normal:
# dsmmigfs add /discoext/pool07
~~
Rita Groothuizen RC-ICT/Rijks Universiteit Groningen
E-mail: [EMAIL PROTECTED]
Tel: 050-3633491 Fax: 050-3633406
So I'd heard, but I don't have the liberty of choice, so I'm stuck with it
on the AS system.
Mike
-Original Message-
From: Joshua S. Bassi [SMTP:[EMAIL PROTECTED]]
Sent: ä ñôèîáø 21 2000 17:33
To: [EMAIL PROTECTED]
Subject: Re: Slow restore for large NT client outcome..
To answer your q's James,
1. ADSM sits on an AS400. BE sits on either an NT seerver or another Novell
server. Client on the server is (ADSMwise) version 3, Release 1, Level 0.8.
2. Network is Ethernet. All servers are connected 100MBHD. Backbone is 650MB
FO.
3. Damned if I know I'm afraid. On
Hi Tim!
Thank you very much for your reply! Indeed expiration is running during the
crashes.
I will download 3.7.3.8 and we will install it a.s.a.p.
Kindest regards,
Eric van Loon
-Original Message-
From: Williams, Tim [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 21, 2000 17:29
We are in the process of upgrading our OS/390 ADSM 3.1 server to TSM 3.7. We
have a number of client systems for which no 3.7 clients are available (one
Solaris 2.5.1, one SCO OpenServer, and a number of HP-UX 10.20 systems). We
will end up with these clients using 3.1 clients to connect to the
Hello,
Can anyone explain the following results to me?
tsm: TESTselect count(*) from events
Unnamed[1]
---
117
tsm: TESTselect count(*) from events where '08/01/2000' scheduled_st
art
Unnamed[1]
---
8507
It seems as if by narrowing down my
I have problems trying to restore files from an AIX box to another. I'm
following the instruccions given in "Using the Backup-Arching Clients",
v 3.7, chapter 3 (Authorizing Another User to Restore/Retrive Your Files
and Restoring or Retrieving Another User's Files).
What I do is:
1) In the
Does TSM do anything about managing the database backup volumes? Or do I
need to do that manually? (ie delete old versions before it runs out of
space). As far as I can tell, the database doesn't see them as volumes,
because they don't show up when I do Q VOL (although Q VOLHIST describes
them
Do a query volhist type=dbb to see the volumes consumed by db backups. To
remove them, use delete volhist type=dbb todate=today-3 (to keep three
versions).
If you have DRM, you can set the parameter drmdbbackupexpiredays to 3 and
DRM will wipe them for you.
Kelly J. Lipp
Storage Solutions
I couldn't tell you. Each persons definition of a small file and large amount of
small files can be completely different. In one area a 100meg file can be
considered small while another group may consider it huge. I have a volume with
over 3 million files which average about 24k bytes in size.
Paul,
You are correct. the design of the SELECT * FROM EVENTS was intended
to present only events for today (just like QUERY EVENTS). However,
I agree that the design ought to be changed to reflect the SQL
standard: that is, SELECT * FROM anytable presents *all* records
in that table, not just
Hi all,
There was a recent inquiry concerning *SM DB unloading-loading and the
potential benefits/drawbacks.
The stated benefit was a significant reduction in DB size (90% to 52%) but the
drawback was that the process took
approximately 24 hours (this was on a 46 GB DB).
I'm running ADSM
Does TSM do anything about managing the database backup volumes? Or do I
need to do that manually? (ie delete old versions before it runs out of
space). As far as I can tell, the database doesn't see them as volumes,
because they don't show up when I do Q VOL (although Q VOLHIST describes
Also, I didn't see anything in the ADSM Admin. Reference manual about
"unloading" the *SM DB.
It's in the Admin Guide. Also in ADSM.QuickFacts.
I'm not convinced that this has any net positive effect, or that it's
worth the protracted effort. It's going to compact database records -
bring them
When is the planned release date of Connect Agent for Exchange 2000
Mehdi Amini
ValueOptions, MIS/LAN
703-208-8754 - Voice
703-205-6879 - Fax
**
This email and any files transmitted with it are confidential
and intended
Hi,
I've report this problem to Tivoli support but haven't get any feedback yet.
I figured I might get a faster response here...
Environment:
TSM server version = 3.7.2.0
TSM server host o/s = AIX 4.3.3.0
TSM client version = 3.7.2.0
TSM client host o/s = AIX 4.3.2.0
TSM
Richard,
Yes, I just install HSM two weeks ago. But I have restarted the
Solaris machine several times and the kernel extension has been added.
Indeed, the rest of the file systems have been created with the same
process at the same time, and they work okey.
When I
Please delete me from the group.
Thank-you
Alan Lewis
I am seeing something wierd on my 3590 volumes..
When a tape becomes full, ie, I receive:
ANR8341I End-of-volume reached for 3590 volume AD0441.
But, when TSM 3.7.3 dismounts the volume, I receive these messages:
ANR8336I Verifying label of 3590 volume AD0441 in drive E5632 (/dev/rmt0).
UNLOADDB is a DSMSERV utility added in TSM 3.7.
It's documented in the Admin ref for 4.1 under the topic "TSM Utilities".
It's not there in 3.1.2.40.
-Original Message-
From: Tim Melly [SMTP:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 10:52 AM
To: [EMAIL PROTECTED]
I haven't seen in this thread (or I missed it) any comments about using
BACKUPSETS.
Has anyone tried that?
Does anyone know if the backupset is constructed in a way that overcomes any
of the problems with recreating zillions of small files?
Or do we need an image backup capability like the AIX
There's problem with the silent install, see:
http://www.tivoli.com/asktivoli/data/cleanapars/IC27/IC27909
Here's my work-around, it isn't pretty and uses brut force (maybe you can refine it)
but has worked so far You'll need to tweak for your environment. If you have any
questions, please
Mehdi,
We are targeting Q1 2001. As usual...no promises.
Thanks,
Del
Del Hoobler
IBM Corporation
[EMAIL PROTECTED]
"Amini, Mehdi" [EMAIL PROTECTED]@VM.MARIST.EDU on 09/22/2000
11:44:42 AM
Please respond to "ADSM: Dist Stor Manager"
Thanks Wanda. Actually I did try to generate a server backupset
for a different smaller NT client with similar data
characteristics. The generate ran for a couple days. I was
thinking of giving it a try for this NT client.
Jeff
"Prather, Wanda" [EMAIL PROTECTED]@VM.MARIST.EDU on
OK, another question and I'm going to answer this one myself in a couple of
weeks when I participate in a trial of it...
Let's talk about a big time TSM restore that worked well and was reasonably
fast. Anyone with such an experience?
I know in some testing I restored 18 GB in an hour using
Hee Hee. Out of the frying pan...
So much for that idea!
-Original Message-
From: Jeff Connor [SMTP:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 1:51 PM
To: [EMAIL PROTECTED]
Subject: Re: Slow restore for large NT client outcome.. appeal to
Tivoli D
I'm trying to move a node from one AIX machine to another; both are AIX
4.3.2, TSM 3.7.3.8, and clients 3.7.2.16. The export goes fine, but the
import doesn't do anything. The logs follow.
TIA
Date/TimeMessage
---
I have an unexplained message from the dsmerror.log
My Client is 3.7.2.01 NT 4.0 SP 6
I get the following message:
9/22/2000 14:55:19 Unable to open Acknowledgement Mailslot
'\\.\mailslot\client'.
I have not been able to find anything out on this...any ideas.
Bill Slaughter
Lawrence,
Try exclude /db02/oradata/.../*
-Original Message-
From: Lawrence Clark [SMTP:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 4:16 PM
To: [EMAIL PROTECTED]
Subject: Re: inclexcl puzzle
Hi:
In my inclexcl.list , at the bottom is:
exclude
How do you delete OnBar backups?
I inherited an ADSM setup where OnBar backups are filling our tape
library. How do I get delete the old backups that are no longer
relevant. I can see them sometimes.
In dsmadmc I can run these commands:
adsm q file ibm12_db
Node Name
Try exclude /db02/oradata/.../*
_ _
David Beardsley
Kimberly-Clark Corporation
E-Mail: [EMAIL PROTECTED]
Phone: (920) 721-6127
-Original Message-
From: Lawrence Clark [mailto:[EMAIL PROTECTED]]
Sent: Friday, September 22, 2000 3:16 PM
To: [EMAIL
Unless I am mistaken, your exclude statement only covers files in that
directory. To cover all files and files in subdirectories you need to specify
/db02/oradata/.../*.
Darlene E. Wnukowski
Lead Systems Programmer
Schreiber Foods, Inc.
[EMAIL PROTECTED]
920-455-6268
--(
Hi Ken,
We had this problem and after a while we figured out the empty tapes
were not in the 3575 library (Move Media). We had to do another Move
Media to get them to go to scratch. The reason is, if the tapes are out
of the library and go to scratch you will lose track of them. We pull
the
35 matches
Mail list logo
