Hi all,
It's a possibility that our 3 sister companies on the same site currently
sharing
the same LAN maybe split into 3 network domains using Vlans and firewalls.
All 3 Domains will somehow, have access to central services like internet,
accounting applications, etc.
We intend to ret
Hello Bill,
Granted that have the appropriate trust relationships configured between
the domains, appropriate firewall rules and efficient performance
tuning, you can backup clients residing in a domain different to that of
your TSM server. In our Storage environment, we backup numerous clients
in
Hi everyone,
Just wonder if anyone have type down the total Dependency list to install TSM
6.1 on Linux 86_64?
This is how far I got
* rpm
* jre-6
* libstdc++5
* libaio, libaio0 and libaio1
* glibc
Does anyone know anything else that should be added to this list?
Best Regards
Christian Svenss
Hello Bill,
As other have posted, TSM should handle the backups without problems related to
the use of different network domains.
But. You might want to look at why there are different domains. Might you
expect that in the future that one or more of the 3 sister companies might be
sold or sp
People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCS
We have one Windows NT domain and one Active Directory domain and back
both up with the same TSM server without problem
Buddy Howeth
Computer Operations Specialist
Information Systems
Pacific Coast Producers
Corporate Offices
631 N. Cluff Ave
Lodi, CA 95240-0756
(209) 367-8800 - Main#
(209) 367
I'm a little confused on what you are trying to do. Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?
Also, are you using Atape multi
I agree entirely that "VCB" and "beauty" together does not compute, and the
2-phase vmdk restore is dorky.
But regarding the backup cycle, there is an "in between" option most TSM
folks can use without taking the hit of two complete backups ("virtual
drive" and "image" as described below) daily.
Confusing!!
1. In UNIX, special characters are reserved for special functions and
special care must be taken to not have these characters interpreted during
code execution. As a result, using UNIX specific device names as names for
your TSM resources is asking for trouble!
2. Why aren't you using
I am not sure of your use of the word domain.
Windows domains are not relevant because TSM does need a Windows account to
work. We have two domains, no problem.
DNS domains are only troublesome if the TSM server is unable to resolve the
nodes IP address due to a DNS lookup problem. We have 2 in
Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the o
Hi Nicholas!
1) I know, but it has always worked this way and it does still work for
the other TSM instance running on the same host!
2) Because we use multiple libraries and drives. In fact it's an AIX
cluster which runs two TSM instances on every node. Since it's a HACMP
cluster, one cluster node
I don't have any real idea, but if it works as /dev/rmtX, and not after
renaming - I wonder if the binding is getting messed up on the rename.
Check the device attributes before the rename, and then after, and see if
the scsi_id, wwn, lun_id is the same.
lsattr -El rmt9
lsattr -El r123_4
Good Day all,
About a month ago, I was prepping to split a TSM DB because it was growing out
of control after the addition of a number of remote imaging sites. After much
review I was able to find failures in the expiration process. I tracked it down
to a single client and after a call to IBM it
Hi Richard!
They are identical...
It must be a TSM issue then. I will try to create a path to the renamed drive
tomorrow (which will fail) and then try to create a path to the same drive on
the other TSM server on the same host. If that one does not fail, it must be
related to that specific TSM
Hi Eric,
If I understand you correct.
You can define a drive and the path.
As soon you rename the drive the path is stop working?
And now you can't you update the path anymore or delete / define it again?
Have you compare the output from q drive f=d before and after rename?
Same thing with q pa
Provide a "q db f=d" output.
Also, might want to do a "ESTimate DBREorgstats" for more information.
But yes, most likely an unloaddb, loaddb is your only option (other than
upgrading to 6.1, which is supposed to let you optimize while running)
Regards,
Shawn
_
Hello All,
Thanks for your help!!
When using DRM, tapes are moved from the mountable state to the vault state
using the s=dbs option ,they remain in the Vault state until they are empty
and the reuse delay on the storage pool has elapsed and DRM moves them into
the "vault retrieve" state. My ques
I am not sure shrinking the amount of disk space used by the DB will be worth
the time. TSM will use the pages in the DB, even if they are not at the end.
You will still have to add new disks at the same point in the future.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manage
Hi Andy,
Do you know if the 6.1.0.1 version works for XSERVE as well? I tried the
fix of switching the java version preferences, but it seems to have no
effect. Thanks!
Jim Neal
Sr. TSM Administrator
U.C. Berkeley
IS&T Storage and Backup Group
-Original Message-
Fr
Dear Duane,
we currently face the same problem, as we had to expand one of our
databases beyond the limit we had set and cannot shrink it now. Short of
taking the System offline for dump and load of the database, we are going
to restore the database to another TSM instance and do the dump and load
21 matches
Mail list logo
