Grigori,
Regarding the points you made below:
It is impossible to use MOVE DATA, because it is working with volume
level and each DISK volume contains data of many nodes
You won't be able to move data if you are trying to move data from any
primary storage storage pool to a secondary storage
Hello Bertaut,
FILE storage pool is a primary storage pool, not a copy storage pool.
MOVE DATA is working with volumes, not with nodes (it is not suitable at all
for my case).
MOVE NODEDATA requires both sequential storage pools: source and target. It
just gives an error about DISK storage
Hi TSM-ers!
We use the following SQL statement to report to our Oracle department if
their delete obsolete jobs are running ok for all nodes:
select node_name, filespace_name, ll_name, state, object_id,
date(backup_date) from backups where ((days(current_date) -
days(backup_date) = 30)) and
Hi Eric,
yes you can do something like
select * from a where fielda in (select fieldb from b)
but (usually) this is dog-slow in TSM = 5.5
On 10 aug 2009, at 15:18, Loon, EJ van - SPLXM wrote:
Hi TSM-ers!
We use the following SQL statement to report to our Oracle
department if
their delete
Grigori, you are right about the move data operation working only with
volumes and not nodes. You stated earlier that migration was not going
to work since you wanted to deal with a few nodes data only; are you
going to run move data on the sequential copy pool for the primary data
currently
We have approx. 12 TSM Server 5.4.2.0 instances, all being managed by a
single TSM Server / Library Manager also 5.4.2.0
We'd like to add a new TSM 6.x server instance into the environment.
My assumption is that the 6.x server instance cannot be managed by the
current 5.4.2.0 library
I need a way to get a list of files that have been migrated so I can exclude
them from being copied to a new server. The client is using Robocopy (don't
laugh!) and when it hits a migrated file the copy terminates. The problem is
that HSM was not setup correctly and the archive copygroup was left
Hello,
windows client-schedules do not start.
We use dsmcad and schedmode=prompt.
There is no special error message.
With client version 5.5.2.1 the schedules are working succesfull.
I'm wondering, if there is a problem with the tsm client 5.5.2.2 ?
Has anybody else the same problem?
with best
What are the failure messages? Does the job just show as missed?
Joseph A Abbott MCSE 2003/2000, MCSA2003
Partners Healthcare Systems Development Team
Tivoli Storage Manager
jabb...@partners.org
Cell-617-633-8471
Desk-617-724-4929
Page-# (617) 362-6341
jabb...@usamobility.netÂ
Be who you are
My assumption is that the 6.x server instance cannot be managed by the
current 5.4.2.0 library manager.
You are correct. The
library manager must be at the some or highest level of all library
clients and storage agents.
Can a TSM 6.x Library Manager manage 5.x TSM server instances /
We are about to three existing TSM 5.5.3 instances on a new AIX box
running Version 6. Current database sizes combined are around 115GB
used. Available disk for the Version 6 database and logs is an IBM 7311
with 10 available 146GB 15K drives and we are wondering what is the best
way to configure
Without the errorlog, it is difficult to diagnose. Try starting it in
the foreground first. Open a windows command line, and run dsmc
sched. This will give you a good idea of what is going wrong. Also,
look at the dsmwebcl.log and dsmsched.log. It could be a simple
password issue.
To answer
12 matches
Mail list logo
