Recently, for migration/testing purposes, I did a full conversion of a
5.5 server to 6.2 on my test TSM server.
I would like to continue using this server to test additional upgrades
without having to wipe and rebuild.
Unfortunately, since it is a copy of a real server, whenever I fire it up,
it
Is doing a TSM DB backup/restore the only way to remove a TSM DB directory in
V6.2?
David
If you really want to isolate it, change the IP address to one in an
unused/isolated subnet/vlan and don't give it a route statement. Make sure
DHCP is not enabled on any of your other NICs.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Z
What I do on our test server is put dummy entries in the /etc/hosts file
for my other tsm servers. The search order is set to check hosts file
entries first, then dns.
For example,
real server:tsm1 192.168.1.1
on server - in /etc/hosts: tsm2 99.99.99.99
Of course, this is ass
On 05/14/2012 09:45 AM, Zoltan Forray/AC/VCU wrote:
What else can I do to neuter it to avoid possible problems?
I would say:
+ delete the paths from this server to the tape drives
+ delete the paths from this server to the library
+ Remove this server from the FC zone that can access the lib
We are doing a 5.5 to 6.2 migration now by exporting all our nodes to
new servers. Some of our oracle nodes are very large, but exporting
works fine, it just takes a while. We had one node that took over a week
to complete. Here's an outline of our process:
TSM-A is the 5.5 server. TSM-B is the 6
Folks,
I'm trying to upgrade a TSM 6.2 server to 6.3 on AIX 6.1. The process
completes, but gives an error that DB2 failed to install. When I check the
db2_inst.log as directed, I'm getting the message:
DBI1149E To execute this program, you must be the owner of the
installation copy.
Expla
I have a customer with a 1.2 TB Exchange 2007 DB, expected to grow to 3 TB in
the next 4 months.
Fulls are already a problem (14 hours).
Is there any Exchange-related reason I can't do the fulls for a couple of
storage groups on Monday, the next 2 on Tuesday, next 2 on Weds. etc and spread
them
Hi,
Is there a standard SLA to draw a line between the duties of OS
admins/operators and TSM admin/operators? Many TSM admin duties like TSM
server maintenance, tape libraries, DRM, ... are evident. But some tasks
like verifying backups could be the point of dispute. Maybe it is dependent
upon the
Hi Mehdi
My take on this is that we as TSM admins provide an infrastructure that
clients use to back up, just as if they had a local tape drive attached
to their box. It is up to us to keep that infrastructure running and
ensure that things post-backup, such as BACKUP STG and offsiting of
tapes
On 14.05.2012 00:42, Xav Paice wrote:
- Original Message -
From: "Steve Harris"
Hi All
Like a lot of us, I'm contemplating a TSM 5.5 to 6.3 move for one of
my
customers.
Most clients are not a problem, point the client at the new server,
take the first backup, and then after an appro
11 matches
Mail list logo
