One other question, if you don't mind Bill: Do you have Copy Storage Pools?
If so, are they on tape or file? If tape, is the small volume size on the
primary pool an issue? I.e., does TSM optimize output tape mounts?
Thanks.
..Paul
At 05:48 PM 11/14/2013, Colwell, William F. wrote:
Paul,
Paul,
I describe my copypool setup in a previous reply, last Friday.
If you lost it somehow, it is on adsm.org.
But quickly, they are on virtual volumes. I have never seen any issues
related to the primary pool volume size.
- bill
-Original Message-
From: ADSM: Dist Stor Manager
Is vSphere 5.5 supported by TSM VE 6.4? If so, can you point me to the
relevant documentation?
David
http://www-01.ibm.com/support/docview.wss?uid=swg21647461
Protection for VMware Version 6.4.1
_Supported VMware vSphere versions_
The following VMware vSphere versions are supported:
* vSphere 4.1
* vSphere 5.0
* vSphere 5.1
http://www-01.ibm.com/support/docview.wss?uid=swg21652843
Data
Bill,
Are you virtual volumes purely on tape on the target server, or are they
fronted by some sort of disk storage pool? I am trying to understand whether a
small volume size for the ingest dedup file pool will cause a lot of tape
mounts on the copy storage pool during a backup storage pool
Paul,
the virtual volumes land on a disk buffer in the target server.
Actually there are 3 filesystems of raid 5 sata which are round
robin'ed as the target; a script updates the devclass directory
at midnight. Then the previous days virtual volumes are migrated to
tape. My intent is to
