New backup copies will go to new stg, existing backup copies gets rebound
to new mgmt class but won't be automatically moved from 1 stg pool to
another.
Op 13 aug. 2015 08:05 schreef Robert Ouzen rou...@univ.haifa.ac.il:
I to all
I try to figure a scenario to change a backup for a client that
Hi Karel
Did is a way to trigger the move ? I think a full backup maybe will do it . But
I tried to figure another workaround , huge client.
Best Regards
Robert
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Karel
Bos
Sent: Thursday,
Hi Karel
I think I found the solution, to change on the backup copy group on the
management class mgtest1 the copy mode to absolute.
Run an incremental backup , the pst will be rebound and store to the correct
storage pool and put back the copy mode to modified
Best Regards
Robert
The library manager needs access to the control path anf data path as it
mounts tapes and reads labels. Storage agents only need access to the data
path because they only read and write data.
On 13 Aug 2015 2:28 am, S Kumar our@gmail.com wrote:
Hi Team,
I have mixed library filled with
I to all
I try to figure a scenario to change a backup for a client that only pst files
to go to another storage
I created a new management class and different copygroup destination for pst
files call: mgtest1
? For all files management mgtest (default) go to TSMSTG1 storage
?
Hi,
I haven't used the OC since 6.3 or 6.4. But, if this feature is not
there, this is the one thing that I need and the only reason I'm holding
on to the old TSM v5 Management Console software:
- Custom SQL queries that can be created and ran against the TSM server
environments ona regular
Just went from v6.3.5.100 to v7.1.1.300. The procedure went smoothly,
but so far I'm not impressed with the client backup - slow to start, slow
to run. I'd hate to think that the only solution for the performance is a bit
of sleight of hand to reconstruct the tablespace.
Database is only ~350G
On Thursday 13 August 2015 14:10:16 you wrote:
Just went from v6.3.5.100 to v7.1.1.300. The procedure went smoothly,
but so far I'm not impressed with the client backup - slow to start, slow
to run. I'd hate to think that the only solution for the performance is a
bit of sleight of hand to
