Specify alternate failover volumes

Learn how to specify alternate failover volumes when a volume is marked as read-only or inaccessible. When a volume size exceeds a certain threshold, you may set the volume as read-only and create a new volume with the same assigned users and groups. All subsequent file operations should then use this new volume. There are conditions under which file write operations from the Dispatcher Server fail because it cannot write back to the original volume. To overcome this problem, the TC_Volume_Failover_Volume_Map preference allows specifying fail-over (alternate) volumes for one or more volumes in the system. Use this when a volume is marked as read-only or otherwise inaccessible for new write operations. Specifying the alternate volume ensures that future writes are done to this alternate volume rather than the currently set volume. Each value set in the preference should be of the form: source-volume:destination-volume. The mappings can be cascaded, for example: VolA:VolB and VolB:VolC. This indicates that the system should use VolC when VolA is the current volume. The Teamcenter administrator typically follows these steps to enable this mechanism: Create the new volume in Teamcenter. Grant permissions for the required users and groups to access the new volume. Set the values in the TC_Volume_Failover_Volume_Map preference in Teamcenter, for example, original-volume:new-volume. Set the original volume as read-only. Note If permissions are not granted to a certain user to access the new volume, the system does not report an error. Instead, it defaults to the volume currently set for that user and group.