/testfs may grow to 1 TB
there is a way to cheat:
def v filepool /test2fs/file
def v filepool /test2fs/file0001
...
so using a script you can manually define more volumes outside the
devclass-defined directory. their sizes are as defined in the devclass.
another approach might be hierarchy
The manual you are looking for is named IBM Informix Backup and Restore
Guide. You can find it at URL
http://www-306.ibm.com/software/data/informix/pubs/library/interim/ct1slna-pdf.html
Or you can browse the whole library of Informix Dynamic Server manuals at
The answer can be found at IBM (what an answer to an IBMer :-)) using
copy/paste:
IBM Announcement Letter No. ZG03-0323 dated May 06, 2003 (find the
corresponding one for AP):
New 3583 features, in addition to native switched fabric Fibre Channel
drive attachment, include patented Multi-Path
I assume OEM stands for Oracle Enterprise Manager.
You can protect OEM's repository as any other regular Oracle database. If
your DBA is having some specific problems it would be good to provide
details. If only a generic answer is needed, the answer is TDPO can
backup online through RMAN any
Chuck,
I would say these files are very good candidates for exclude as any other
temporary file. If they are existing for a very limited period and even
now you are not backuing up those files without any harm, then I would
classify them as temporary.
IMO this is not a limitation of the product
Joni,
there is an easy and straightforward method to verify it:
1. open a console admin client session(s) to TSM server from your
workstation
2. modify your *workstation's* dsm.sys/dsm.opt and set
tcpserveraddress=storage agent's address
3. now open a console admin client session(s) to the
Matt,
indeed you are :-)
The storage agent and the server must be at the same
version.level.maintenance.patch! The client vs. StA versioning follows
client vs. server supported combinations. In Pattie's case v4.2.x client
being supported (in the past) when used with v5.1.1.6 server, ought to
work
He does not need to use Atape for 7336, but `lsdev -Cc tape` output might
reveal some other problems. So the Anderson's approach is better :-))
Zlatko Krastev
IT Consultant
Dan Foster [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
23.06.2003 07:02
Please respond to
It depends on your definition of qualifying storage pool but it might be
worth to look at STGPOOLS table and select from it.
Zlatko Krastev
IT Consultant
Steve, Taylor [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
22.06.2003 00:28
Please respond to ADSM: Dist Stor
page you see a seperate section about other drives in a library., since
th
TSM device driver controlls the library, then the drives section should
matter and tell you what to use.
Peter
At 13:19 16-6-2003 +0300, Zlatko Krastev/ACIT wrote:
Yes, I've opened the list and followed the link
Actually, that page is slightly misleading. Because StorageTek can equip
their libraries with any vendor LTO drives you may need different driver
and the site specifies only one of them. For STK with IBM LTO drives, OS
native IBM driver should be used. For STK with HP or Seagate drives, TSM
driver
also that someone
needs an ID to see what hardware is working with a software product.
Anyway, I saw several descriptions of the STK libraries with the differant
tapedrive vendors mentioned.
Did you also saw the list with a key symbol on the left.
Peter
At 10:06 16-6-2003 +0300, Zlatko Krastev
The answer is no. You have to go at v5.1.6.1 or beyond to have support for
LTO-2. Later proceed as usual - def libr; def path destt=libr; def dri;
def path destt=dri;
Zlatko Krastev
IT Consultant
Hector Chan [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
15.06.2003
Best approach (IMO) is to create EtherChannel. Thus the load balancing
will be automatic. 1/2 of the nodes does not mean always 1/2 of the data
flow.
Two cards on same IP subnet can accept connections simultaneously on two
addresses but the outbound traffic will be routed only through one of
them.
Without a description of the test procedure you are following is little
bit hard to find the mistake. Anyway an attempt to explain:
0. filesystem is not backed up at all
TSM has no knowledge of the files it contains.
1. dsmc incr /fs_mount is invoked and completes with success (full
incremental
You can look on Dwight's answer on thread Archives are much slower than
backup back in January or the answer from David Smith on thread
Duplicate Archive Entries...and deleting them in April 2002. You can
search through list archives for the word archdir.
In short - `cleanup archdir` might be
Thanks Gretchen, as usual you are our tester for new versions. Aren't
exhausted sometimes serving as guinea pig to IBM/Tivoli ;-)
Zlatko Krastev
IT Consultant
Gretchen L. Thiele [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
13.06.2003 21:27
Please respond to ADSM:
Do you have some spare space on the TSM server?
1. fill few GB filesystem with *uncompresable* data only, zip files for
example. No need for 100s of MB files. Everything bigger than 1-2 MB is
fine. TSM aggregation will bundle them to 10s or 100s.
2. backup that fs direct to tape (via loopback or
The requirement is set for a *supported* version. As it was known before
the announcement that v4.2 will be out of support when TDP 5.2 is out, it
isommited from the list.
It might work and might not. But in case of problems you cannot get
support from IBM, that's it.
Zlatko Krastev
IT Consultant
Deon,
IMO the main problem is not in the drivers but in supported kernel levels.
People can cope with the limited number of devices supported (which is
device driver problem). But providing support only for rather old kernels
(though reliable) is a problem - whenever an update is required we fall
Another good example how doing things by the book leads to guaranteed
success.
Well done Tab.
Zlatko Krastev
IT Consultant
P.S. There are many backup products on the market but few restore products
(borrowed the idea from Paul).
ZK
Tab Trepagnier [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor
David,
why not to create another primary pool and direct that node in such own
pool (or shared with few similar requirements nodes). Setting collocation
off will have little or no impact on your restores. In fact allowing
backups to parallelize, you will set the ground for parallel restores.
Rajesh,
when I was installing v5.1.5 from CDs I had no problems. Maybe you were
able to resolve it also by uninstalling and reinstalling v5.1.5 without
going back to v2.2. Of course aside of very likely Del's suggestion,
Joshua might have different problem.
Zlatko Krastev
IT Consultant
rhetorical answer to a rhetorical question:
I am under impression that TSM DB and DB2 are some sort of cousins -
derived from same SQL/370 design or code. Thus the answer to your question
might be when TSM DB is going to catch up with recent improvements on
DB2/Informix front.
I still remember
More info about your current and your target version would help. And the
information are you eligible for the target version might sched some
light.
You do not need to visit any v4.2.x.y level before upgrade to v5.1. The
upgrade procedure is designed to work for all old TSM versions (v3.7, v4.1
Lisa,
the problem is in the following:
tsm: TSM_HQ_1define path tsm_hq_2 3494b srct=server destt=libr
devi=/dev/lmcp1
You should invoke this on TSM_HQ_2:
HQ_2 def libr
HQ_2 def path ... destt=libr
HQ_2 def path hq_2 drive1
HQ_2 def path hq_2 drive2
HQ_2 def path hq_2 driveN
!!!
HQ_1 def libr
Mark,
based on additional info I would rather recommend going with AIX. The
suggestion to go with the OS you have more in-house expertize (i.e. Win)
is still valid.
However moving 1 TB you approach the limits of Windows. Dig down the list
archives and you will find a lot of discussions, my
SCO is trying to be David beating Goliat but might become the mice smashed
under the elephant. For sure they've got some support from M$ but we will
see where the story ends only after we reach that point.
This is an expected move. More than a month ago I predicted to my
colleague such an attempt
What is your *exact* target - collocation, IBM/Tivoli happiness or faster
backups/restores. Have in mind that even IBMers are human beings and can
err. Sometimes disabling collocation might give *improvements* (usually
does not)
Zlatko Krastev
IT Consultant
David E Ehresman [EMAIL
You were not precise on the adapter. Was it 2940 (Fast SCSI-2, 10 MB/s),
2940W (F/W SCSI-2, 20 MB/s), 2940U, 2940UW or 2940U2W ? SCSI bus speed
might be part of the bottleneck.
What drivers and at what version are you using? Try IBM ones from
www.pc.ibm.com/support.
Zlatko Krastev
IT Consultant
The danger with XP Pro lies on the other side - you can apply a security
patch and your network connection could be secured too much (cut off),
thank to M$:-((
Zlatko Krastev
IT Consultant
Alexander Lazarevich [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
12.06.2003
To: [EMAIL PROTECTED]
cc:
Subject:Re: New to TSM
The estimates were 50-75GB daily (not 1 TB daily), 22 clients - a pretty
simple load for W2K.
-Original Message-
From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]
Sent: June 12, 2003 1:49 AM
To: [EMAIL
Dell,
we should not do this or there would be no benefit of doing so? Are there
any known issues (like transaction sending to more than one stgpool) if
these zero-lenght object are bound to different class?
Zlatko Krastev
IT Consultant
Del Hoobler [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor
Total data backed up * (100 - Objects compressed by) = Total number
of bytes transferred
In your case this equation would mean that you have compressed over 1.5 TB
with compression ratio over 99.5% (to have TSM report is as 100%) down to
reported 7.81 GB. A read rate of 3.25 GB/s (1.5 TB divided
You can identify which volumes contain that node's data on old copypool.
Then delete those volumes which would remove the data for the node in
question along with other nodes' data. On the end re-backup all affected
primary storage pools to recover the data for collateral damage nodes.
Works on
-- A large disk pool does not appear useful for:
1) Small number of nodes with large to huge size backups. TDP nodes
would be a good example of this (our case).
Switch to convinient tape backup technology. The benefits:
- small mount time delay will be well paid by increased speed of
Are you using same nodename on all platforms, i.e. connect as nodename A
from NetWare, Linux and Windows?
You should use separare nodes for each platform. After you have connected
from Windows, the node was upgraded to work with Unicode-enabled
filespaces. After that upgrade you will not be
You can look at Andy Raibeck's answer from 19.09.2002 on thread LAN-free
backup goes SAN, LAN, SAN:
For AIX 4.3, client patch levels 4.2.2.5 and 5.1.1.5 contain the fix for
IC33316.
For Windows, client patch levels 4.2.2.8 and 5.1.1.5 contain the fix for
IC33316 (the README for 4.2.2.8 does not
-- ... from storage pool COPY01 to storage pool COPY01 ...
TSM is smart enough. Try using TOstgpool=another copypool parameter of
MOVe NODEdata command.
Zlatko Krastev
IT Consultant
Jurjen Oskam [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
19.05.2003 14:17
Please
You do not say is the reclamation performed on primary or copy pool,
collocated or non-collocated, how many source volumes were mounted.
For example reclamation of non-collocated copypool volume reading from
collocated primary pool volumes may require a lot of mounts. And DLT7000
mount time is now
I always thought TSM is not so much CPU intensive. The main CPU
consumption is to drive I/O. In the past in IBM manuals there was info how
much load each adapter can put on the processor. Even if I have not seen
such info recently, does not automatically mean it does not exist. CPUs
are getting
Is your client scheduler in POlling or PRompted mode? Have you changed the
mode during upgrade?
Zlatko Krastev
IT Consultant
Mark Hayden [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
13.05.2003 00:30
Please respond to ADSM: Dist Stor Manager
To: [EMAIL
I've done export followed by import with mergefilespaces on TSM for AIX
v.5.1.6.2. The result was *almost* the expected one - the imported files
merged to the filespaces as if you have performed both backups on new
server. The almost part was that newly imported versions/objects were
incorrectly
Maybe, but in list archives definitely. Look at Tab Trepagnier's answer
from 16.12.2002 on the thread Setting up DIRMC seq pool on disk (you can
learn from other Tab's experiments alot).
Now in recent versions IBM claims that have fixed copypool reclamation
reading from primary random access
If I was a developer of TSM I wouldn't bother myself with caching DNS
lookups. Probably TSM relies purely on operating system's TCP stack
(gethostbyname or socket). Of course manual says nothing and we have no
access to source code, so can only guess ;-)
If you experience some caching of old
-- NT-DCO-VCSF, DOMINO, 2003-05-02, 09:32:34.00
Deletion of filespaces does not count as lack of usage, deletion of the
*node* does. The definition of in-use license is 30 days after last use.
Therefore today it would stop counting as in-use - May 2 + 30 days = June
1 (sorry, just have read
You can try this:
select vol.volume_name, vol.pct_utilized -
from volumes vol, libvolumes libv -
where vol.volume_name=libv.volume_name -
and devclass_name='' -
order by vol.pct_utilized
Change the devclass with the one defined over the library or join also
visit
http://publib-b.boulder.ibm.com/Redbooks.nsf/RedbookAbstracts/sg244877.html?Open
There you can find a nice redbook named Tivoli Storage Management
Concepts (SG24-4877-02). Read carefully all chapters from 1 to 8 (and
some of the others might also be very helpful).
For example, in Chapter 3
Yes to both.
Of course you may also install IBMtape v4.0.7.3.
Zlatko Krastev
IT Consultant
Joni Moyer [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
30.05.2003 21:53
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Check the messages fileset is updated. In some versions of the AIX client
the update was incomplete. Check with `lslpp -L tivoli.tsm\*`
Other possibility might be different LANG environment. When I am
installing a client I perform the following:
# cd /usr/tivoli/tsm/client/ba/bin
# ln -s en_US
As you have already learned the hard way, library sharing would not work
if you have not defined paths to *all* drives for sharing.
Quote from TSM for AIX, Managed System for SAN Storage Agent User's Guide
(GC32-0771-00; just the same wording I quoted for v4.2 in June last year):
Define paths to
1. On first backup after include/exclude list change the new bindings will
take effect.
- *All* old versions of the files will be rebound to new class.
- New class copygroup settings will mandate the expiration
2. Rebind to another class does not force backed up data move.
- All
Read carefully Tivoli Storage Manager for AIX Quick Start Guide. Pay more
attention to Chapter 2. Installing Tivoli Storage Manager. It may save you
a lot of grief.
If you perform migrate install and dsmserv.dsk is in the
/usr/lpp/adsmserv/bin (for ADSM as in your case) or
There also other reasons *not* to create an admin on node registration -
to avoid confusion.
Using passwordaccess=generate the node is recycling its password
regularly. When the admin's password expires the human on next login is
asked to change it. What would be the chance to get it just the same
You must restore to same platform (AIX) and can later move the .nsf files
to Windows using ftp or Notes replication.
Zlatko Krastev
IT Consultant
Gerald Wichmann [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
30.05.2003 03:53
Please respond to ADSM: Dist Stor Manager
Use both. Create a filepool with MaxScr=1000 over devclass with
MaxCap=2GB. Set a smaller diskpool in front of it with HighMig=10-30,
LowMig=0 and MaxSi=something reasonable.
It might be that the NFS repository works considerably better with files
under 32-bit limits.
Zlatko Krastev
IT Consultant
And the reply to your second question is:
There is no need to expand your db and dbvols. Follow the sequence:
- install the server
- configure tape library, drives and devclass. checkin the DB backup
volume.
- halt the bare TSM server (with default small DB)
- using dsmfmt
What - AIX itself.
How:
- put OpenSSH on it (download from bullfreeware.com; comes with latest AIX
versions)
- disable all unnecessary and plain-text authentication services
(including telnet and ftp - use ssh and scp instead)
- use built-in IP filtering (don't make way too many filters, IP
You do not need two separate dsm.sys files. Just make two stanzas in
dsm.sys and address them in two seprate dsm.opt files. Example:
dsm.sys:
servername os_backup
nodenameOS node
passwordaccess generate
...
servername tdpo
nodenameTDP node
As usual you can find pretty good answers in list's archives.
You can look at the thread IBM 3494 from September 2001 and find some
good ideas there. It is funny (at least to me) that Dwight contributed to
that thread (and being not an IBMer :-).
Zlatko Krastev
IT Consultant
Thomas A. La
This ought to be achievable by modifying
/etc/adsm/SpaceMan/config/dsmmigfstab file.
Zlatko Krastev
IT Consultant
Thomas Denier [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
17.03.2003 21:30
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
Extra Versions=180 and Retain
Only Version=180.
How TDPMGMT class can be used for TDP/RMAN configuration? Is there any
other way to accomplish this?
Thanks
SD
Zlatko Krastev/ACIT [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
03/16/2003 07:43 PM
Please respond
Paul,
if I am UNIX root I would be able to perform su user and act on his
behalf. I fully agree with you that TSM ought to provide some kind of
logging in this case (just to write in actlog admin's name instead of node
ought to be enough). OTOH going back to UNIX I can edit the /var/adm/sulog
It is possible but has its limitations. I even made TSM working with
single drive (manual lib) for both primary and copypool. In such cases
periodic selective (forced fulls) might be of some use.
Zlatko Krastev
IT Consultant
Etienne Brodeur [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager
2176000 - 1787528 = 388472 empty pages
388472 * 4096 bytes/page = 1591181312 bytes = 1553888 kB = 1517,46875 MB
Maximum reduction is 1492 MB, thus the fragmentation is 1,7% - you ought
to happy with it.
Zlatko Krastev
IT Consultant
Farren Minns [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor
Steve,
I assume you have point-based TSM v4.2 licenses (you are talking about
MgSysSAN licenses). TSM v4.2 does not include licenses for Tivoli SANergy
and your company should acquire that product separately.
If you had current maintenance agreement when ITSM v5.1 went out (April
2002) or
Incorrect. The question was about SAN-sharing of disk not tape. Managed
Library is for *tape* libraries having more than certain ammount of
drives and media slots. For disk sharing Tivoli SANergy license is needed
and Managed Library *is not* required (regardless of number of hard disk
drives).
Some old versions of the client had memory leaks but were fixed long time
ago. If you are using such an old version (many people still do not
describe their environment asking questions) the problem can show up.
There is generic solution to this - use Client Acceptor Daemon (dsmcad).
It would
Jack,
it was discussed many times on this list (and with inclusion of DRM in
ITSM XE will be even more):
When DRM is used let it handle expiration of DB backup tapes. Otherwise
deletion through del volh t=dbb would shift off-site inventory and tapes
could stay in the vault instead of recalled
Have you tried include.systemobjectALL expiring?
Have in mind IBM/Tivoli call this System Object while Microsoft calls it
System State and it is not a path (that you can access using 'dir
System State' :-)
Zlatko Krastev
IT Consultant
James R Owen [EMAIL PROTECTED]
Sent by: ADSM:
The BACKUPS table contains the info which object is active and which is
inactive. The CONTENTS table knows where is stored each object.
If you dare you can use a select performing join between the two (but this
would mean to search almost the whole DB minus the archives).
VOLUMEUSAGE does not
Yes, I overlooked this. But in revenge we can force the manager to keep
track of them as well :-)
Or will have to make stgpool backups once a week just to keep him happy.
Zlatko Krastev
IT Consultant
Steve Harris [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
You are not binding a whole node. You can bind a set of files to a class,
another set to different class, etc.
If bindings are not defined through include options (dsm.sys for UNIX,
dsm.opt from Windows, cloptset for both) it is equivalent to binding of
everything to the default class.
Only one
If *all* your storage pools have reuse delay and this reuse delay has not
passed since you started the show there is still a chance: restore again
the DB, restore only the dirdisk stgpool, perform regular incrementals.
If reuse delay have passed (it is if equals to 0) and after reclamation
some
Sias,
the snapshot *does not* clear the log. It is a snapshot, not a backup. Its
goal is to make copy of the DB without touching the Full+Incremental+Log
chain.
Look at the Administrator's Guide:
A snapshot database backup is a full database backup that does not
interrupt the current full and
The explanation is pretty simple:
1. TSM is installed using raw Logical Volume (LV).
2. I would guess /dev/rtsmvglv11 is DB or Log volume (if it was diskpool
TSM ought to start and have the volume offline).
3. Someone have enlarged the logical volume using chlv command in AIX -
look at the
Michelle,
it *is* one PP! Actually TSM measures DB in pages of 4kB. Thus 16384 pages
is exactly 64 MB == 1 PP.
If you have TSM mirrored volume just rename the LV and start TSM. It fill
not find the LV, use the mirror and that is.
Zlatko Krastev
IT Consultant
Michelle Wiedeman [EMAIL
I would second Allen's opinion about your manager (if you dare you can
show him both responses) - beat him with all the manuals on the head until
it opens to different opinions.
I would understand requirement to keep offsite copies longer than onsite
ones but hard to see good business reason for
Filespace deletion removes both active and inactive versions thus removing
more entries than expiration in the DB.
Zlatko Krastev
IT Consultant
Stapleton, Mark [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
09.03.2003 23:21
Please respond to ADSM: Dist Stor Manager
With TSM v3.7 you can do node export/import through tapes only.
If you can afford upgrade to v5.1.5 (or later) you can export+import on
the fly through server-server communication.
Zlatko Krastev
IT Consultant
Ben Geldenhuys [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL
Justin,
a delayed answer but still an answer.
1. Can we move optical platters out of one library into another ...
Yes, you can but as a whole. You can replace a library with bigger one,
checkout *all* libvolumes from old one, checkin them in new lib and update
device class to point new library.
I would say it *is* the right approach! To make a fair comparison you have
to get information from all competitors. Otherwise you will make the
decision
Nearly all answers on this thread point to the TSM vs. NetBackup
comparison report from Progressive Strategies Inc. And all miss that the
GUILLAUMONT
e-mail : [EMAIL PROTECTED]
RGB Technologie
Parc d'Innovation, Bâtiment PYTHAGORE
11 Rue Jean SAPIDUS
67400 ILLKIRCH
Tél : 03 90 40 60 60
Fax : 03 90 40 60 61
Zlatko
Krastev/ACIT To: [EMAIL PROTECTED
Please respond to ADSM: Dist Stor Manager
To: [EMAIL PROTECTED]
cc:
Subject:Re: Need ideas for offsite copy of HSM tapes
At 12:08 PM +0200 2/23/03, Zlatko Krastev/ACIT wrote:
- HSM client sends the data in a storage pool. That storage pool can be
backed up
Look at section Logging Events to the Tivoli/Enterprise Console in TSM
5.1 Administrator's Guide.
Zlatko Krastev
IT Consultant
Dan Carlo Freitas Peres [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED]
17.02.2003 11:16
Please respond to ADSM: Dist Stor Manager
Since v5.1 licensing is based on processors - no matter are they server or
client. Having 10 processor licenses you can have 1 server and 9 clients
or 10 servers for the same price. The price for maintaining these 10
servers
Zlatko Krastev
IT Consultant
Gill, Geoffrey L. [EMAIL
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
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
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
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
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*
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
-- ... 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
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.
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 Stor
-- 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 on
Carsten, Paul,
the three biggest contributors to TSM's DB size are tables BACKUPS,
ARCHIVES and CONTENTS. First two show what was backed up/archived and the
third show where the objects are stored. Everything hitting the TSM server
is either a backup or an archive or a space-managed file. Usually
Jose Rivera
Ris Infrastructure
908-298-3568
1-800-PAGE-MCI#1376812
-Original Message-
From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 06, 2003 1:59 AM
To: [EMAIL PROTECTED]
Subject: Re: LTO 3583 Drive errors with TSM 5.1.5.2 on AIX 5.1
Henry
You did not provided version and OS of the server. Can you provide also
some information about your library - vendor, model, number of drives,
types of drives (it is possible the library is brand new with LTO2 or
upgraded with mixed LTO/DLT). Output of some commands may show the
situation in
Eric,
new product ITSM for Databases is just a new licensing scheme for:
- TDP for Informix
- TDP for MS SQL
- TDP for Oracle
ITSM for DBs 5.1.5 is successor version of TDP for Oracle v2.2. Versions
3.x and 4.x are skipped to aligh numbers with ITSM ones.
Actually in ITSM for DBs v5.1.5 TDPO
1 - 100 of 594 matches
Mail list logo
