After this switching between copy pool and primary pool, I changed the mount
retention on the device classes affected. This speeded up the restore and
ended the constant mount and dismount of the same tape volumes over and over
and over again.
-Original Message-
From: ADSM: Dist Stor
An alternative to the export node option (and works well if you want the
active data sum for everything, is to set up an empty active data pool and
do a preview of a stgpool copy.
It'll be faster than multiple exports.
Steven
On 4 February 2015 at 12:08, Rhodes, Richard L.
Yes, that worked great. An occupancy gives you the totals, and this gives just
the active.
Just for curiosity I created a sql cmd to join contents and backups for a
single node with very little data. It never returned, as expected.
Rick
-Original Message-
From: ADSM: Dist Stor
Nice one!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Reese,
Michael A (Mike) CIV USARMY 93 SIG BDE (US)
Sent: Wednesday, February 04, 2015 8:53 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Query syntax
select char(node_name,50) as
What is the select statement syntax for concatenating
client_version,client_release,client_level,client_sublevel from the nodes table
into a single string, e.g. 7.1.1.3?
David
select char(node_name,50) as Node Name, cast(client_version as char) || '.'
|| cast(client_release as char) || '.' || cast(client_level as char) || '.' ||
cast(client_sublevel as char) as Version from nodes
From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on
When the mounting of both primary and copypool volumes occurs, does the restore
run successfully anyway, even if the copypool is nor marked Unavailable? Is
the mounting of both primary pool and copypool volumes just a waste of tape
drives, or does it crash the restore or export? Our client
In our case the restore time increased substantially(2-3hours to 8
hours) but eventually finished. TSM seemed to prefer the copypool
data that was stored on virtual volumes on a remote TSM server. So,
this also increased network usage by quite a bit. Oddly, TSM would
mount the correct primary
