Testflag or option to restore from Primary STG pool instead of ACTIVE data pool

Currently if an activedata pool exist for a primary stgpool and a client restore is performed, the client will attempt to restore the data from activedata pool. Only in the following conditions it will restore the data from primary stg pool.

1. If the activedata pool volumes are unavailable or destroyed.

2. The server does not attempt to retrieve client files from an active-data pool during a point-in-time restore. Point-in-time restores require both active and inactive file versions. Active-data pools contain only active file versions. For optimal efficiency during point-in-time restores and to avoid switching between active-data pools and primary or copy storage pools, the server retrieves both active and inactive versions from the same storage pool and volumes.

We use ACTIVEDATA POOL for the purpose of DR and data from the primary pool is copied to ACTIVE data pool during the whole month and at the end of the month these active data tapes are sent out of country.
and at that time we update these tapes to unavailable.

The primary stg pool data resides in a VTL (on disk).

In case of a client restore during the month when active data pool tapes are in READW mode, the client first tries to restore the data from activedata pool. So, in our case instead of restoring the data from disk, it tries to restore from active data pool on tape and this delays the restore since we have limited tape drives.

We are looking for a server option or a testflag so that we can force the client to restore the data from primary storage pool instead of default behaviour of restoring the data from active data pool. This is a big operational issue for us since it slows down our restores and effects SLA's