Hello,
Just pure curiosity, what forced you to do an Audit db?
If I had a 3 days service window I would do an Unload db. In the end of the
Load db I would be asked to do an Audit db if there was a need for it.
//Henrik
Good morning,
last weekend i use a 3 day servicewindow to do a audit db on our two tsm-server.
Here my experience:
Both tsm-server are S7A with 4GB Memory, the TSM-DB stay on SSA Harddisk,
Wlb06190:
Available Assigned Maximum MaximumPage Total
Used Pct
Just my two cents worth, but why not do move the database to the new server
then update to 5.1.5? This would allow you an easier path back to 4.1.4 if
there are problems.
Ray Baughman
Engineering Systems Administrator
TSM Administrator
National Machinery LLC
Phone 419-443-2257
Fax 419-443-2376
Em
Hello
I'm trying to label a tape using dsmlabel but with the ACSLS now having
volume access control I can't access any tapes in the library.
dsmlabel -drive=/dev/rmt/2mt,0,0,9,3 -library=acsls,0 -keep
Comes back with "ANR9759E unsuccessful ACSAPI response,
status=STATUS_VOLUME_ACCESS_DENIED."
I
Yes,that was it.
I changed it back to 1581 on feb21 , had to halt and restart tsm server to
load http also killed and restarted dsmcad daemon .
Thanks .
SD
f1n05 /usr/tivoli/tsm/client/ba/bin>ls -la dsm.sys
-rw-r--r-- 1 root system 1994 Feb 21 09:27 dsm.sys
f1n05 /usr/tivoli/tsm/cli
Thank you for the advice.
--- Francisco Molero <[EMAIL PROTECTED]> wrote: > Hi
Douglas,
> In Solaris you can get better performance if you use
> raw devices for DB, LOG and diskpools.
>
>
> > My organization recently migrated a 45GB TSM 5.1.5
> > database from an old AIX platform to a Sun V880
>
--> By the time I was apprised of the situation, the activity log had already
cycled past the relevant entries.
--> The retention policy, set by the IT Director for the particular Division
is 5/1/60/90
To prevent further frustration if I was you I would perform an export of
all node's data to be o
5 years is an easy one. Get LTO or 3590 or 9840/9940 and you have done the
job. The problems can come if go closer to 10 years (other issues to
consider as well). And if you have to achieve 20-30 years there is only
one answer - permanent WORMs + 2-3 (!) copypools.
Zlatko Krastev
IT Consultant
Yes, but someone have changed dsm.sys and set client's port to be 1580. If
dsmcad is started before rc.adsmserv in inittab ...
Zlatko Krastev
IT Consultant
shekhar Dhotre <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
20.02.2003 16:17
Please respond to "ADSM: Dist
Interpretation ought to be correct except the number. 98% used with 0.2%
migratable means 0.2% real data and 97.8% cached. If backup requires space
and file is not larger than maxsize/poolsize cached data ought to be
purged.
Verify for (order of probability):
1. maxsize limit on the diskpool
2. ex
--> ... or do I need to create seperate mgmtclass and bind those files to new mgmt
class ...
You have the answer yourself but are not self-confident. The answer is
correct.
- define new class (I usually name it LOGS), set serialization to dynamic
in backup copygroup
- yes, activate the policy set
Paul,
I am not sure it is a public/private encryption (RSA). My guess is for
licensing reasons 10 years ago DES was used and that part of the code
wasn't changed since. Guessing further I would say some hash-function
takes node's name and password as arguments and produces DES key. Same
function i
Todd,
For the original question: up to now majority of our customers have
Storage Agent nodes and we have no problems with upgrades. Mostly these
are AIX servers (Windows ones are smaller and go over LAN) and life with
AIX is very easy. You can perform upgrade during the day without *any*
signific
How you did the upgrade (4.1.6 -> 5.1.6.2 or 4.1.6 -> 5.1.0.0 -> 5.1.6.0
-> 5.1.6.2 or otherwise)?
What is the fileset and version for the ITSM device driver?
You hope wrong or you hope normal :-)
Zlatko Krastev
IT Consultant
GUILLAUMONT Etienne <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor
It would not work and that is intentional.
Assume you have a library in production (3494 in your case) and one or
more standalone drives (your 3590B/E/H) at disaster-recovery site. If TSM
volumes are hardly referred to library-libvolume you would be forced to
have *exact the same* library at DR sit
You had not looked enough through list archives. This was already
discussed few times and the answer was:
An update to TDPO v2.2.1 is part of IBM TSM for Databases v5.1.5. That
updated TDPO supports Oracle 9i Release 8.1.7, OPS 8.1.7, Oracle 9i (9.0.1
or later) and Oracle 9i RAC (9.0.1 or later). T
Hi Douglas,
In Solaris you can get better performance if you use
raw devices for DB, LOG and diskpools.
> My organization recently migrated a 45GB TSM 5.1.5
> database from an old AIX platform to a Sun V880
> running Solaris 8. The migration of the database was
> done by using "dsmserv restore db
On Sun, 23 Feb 2003 10:46:46 +0200
Zlatko Krastev/ACIT <[EMAIL PROTECTED]> wrote:
> What's the point? I see nothing buggy here except DDSPOOL not in the
> storage hierarchy (which might be intentional).
>
> Zlatko Krastev
> IT Consultant
>
>
>
Which is intentional. I guess it's a feature of copy
Thank you for the valuable input.
Quoting Zlatko Krastev/ACIT <[EMAIL PROTECTED]>:
> 0. (!) cease operations and backup the DB
> 1. upgrade old server to ITSM 5.1.5
> 2. backup the upgraded DB
> 3. attach the library to new server
> 4. restore DB from the library (it might be necessary to play w
Synopsis: Want an offsite image of HSM data for DR, but want to avoid
the use of tapes for an onsite backup image.
I would approach it this way: Via dsmmigfs, defined the stub size to be
512 to eliminate leading file data from the stub, to force all files to
be eligible for migration.
Synopsis: Performed unsupported, undefined cross-platform restoral of the
critical TSM component, its database, and now having odd problems.
The Year of Living Dangerously. That was the kind of posting we hope we
never see on the List. And if the executives of the companies where such
You already got a tons of opinions on this one but nobody commented that
your AIX admin is messing RAID levels:
RAID 0 is striping (no protection)
RAID 1 is mirroring (protected)
I can also bet he does not know the difference between RAID 10 and 0+1
(though it is easy to guess/mess).
Zlatko Kraste
I am surprised to see many answers to this thread not commenting the
standard TSM functionality sufficient to achieve the goal:
- HSM client sends the data in a storage pool. That storage pool can be
backed up to a copypool. If this is a storage hierarchy within the server
(diskpool migration to ta
So let me repeat in short to realize what you've done:
- you had a TSM server with lot of data (45 GB DB, 1000 desktops and
unknown number of servers, etc.);
- you had "vario(u)s errors" and intentionally ignored them;
- you preferred to abandon the supported export/import and step deeply in
unexpl
What's the point? I see nothing buggy here except DDSPOOL not in the
storage hierarchy (which might be intentional).
Zlatko Krastev
IT Consultant
Remco Post <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
21.02.2003 17:20
Please respond to "ADSM: Dist Stor Manager"
0. (!) cease operations and backup the DB
1. upgrade old server to ITSM 5.1.5
2. backup the upgraded DB
3. attach the library to new server
4. restore DB from the library (it might be necessary to play with library
definition)
Continue business as usual
Zlatko Krastev
IT Consultant
TSMadm <[
26 matches
Mail list logo
