Not Mounting BCV Units in EVM Jobs
If you do not choose to mount BCV units in Step 5 of an EVM job, the units can be mounted later. However, to mount the BCV units later will require use of SANworks programs, such as CLI Window, and a reboot of the server on which they are being mounted.
Avoiding Mount Point Mismatches in EVM Jobs
When you create an EVM job, be sure that you correctly associate the storage units and mount points.
Including Existing Mount Points in EVM Jobs
When you create an EVM job, you must ensure that the mount points specified in Step 5 will not be in use by another device when the job is run. If a mount point is in use when the EVM job attempts to mount the BCV unit on the server, it is considered an error condition and the job is stopped.
When a mount point exists, but is not in use by another device, the data will become inaccessible while the BCV unit is mounted by EVM. When the BCV unit is unmounted by EVM, the original data becomes accessible again.
Including Mount Points in Tape Backup Jobs
When using a backup application to create a tape backup job, you must enter or select the mount points of the BCV units that you want to back up. When the backup application does not allow the mount points to be entered from the keyboard, they must be selected from a graphical interface. For these applications the mount points must already exist when you create the tape backup job. In these situations, you will have to temporarily create the required mount points.
Avoiding Inter-Job Mount Point Mismatches
If you develop script files to run an EVM job that mounts BCV units on a server, and then run an application that uses the BCV units as input, be sure that the mount points in each job are correctly matched. This calls for management of EVM and application jobs as job pairs. If you change the mount points in one, you should check the impact on the other.