We started using Virtual Volumes earlier this year for some new branch locations with no local, long-term storage. As it works, multiple virtual volumes will get stacked into one "real" sequential volume.
The problem is that periodically, a reclamation process will require two volumes that happen to be stacked together. On the destination side, it cancels one of the mounts with a "being preempted by higher priority operation", then the whole reclamation fails and the first volume is marked "read-only" As I write this an idea come to the fore. Perhaps I should be using the RECLAIMSTGpool feature. Does anyone else have this problem? Is RECLAIMSTGpool the standard workaround? Regards, Shawn ________________________________________________ Shawn Drew This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
