Veritas InfoScale 7.3.1 Release Notes - Windows
- Release notes for Veritas InfoScale
- Limitations
- Deployment limitations
- Cluster management limitations
- Storage management limitations
- Multi-pathing limitations
- Replication limitations
- Solution configuration limitations
- Internationalization and localization limitations
- Interoperability limitations
- Known issues
- Deployment issues
- Cluster management issues
- Cluster Server (VCS) issues
- Cluster Manager (Java Console) issues
- Global service group issues
- VMware virtual environment-related issues
- Cluster Server (VCS) issues
- Storage management issues
- Storage Foundation
- VEA console issues
- Snapshot and restore issues
- Snapshot scheduling issues
- Storage Foundation
- Multi-pathing issues
- Replication issues
- Solution configuration issues
- Disaster recovery (DR) configuration issues
- Fire drill (FD) configuration issues
- Quick recovery (QR) configuration issues
- Internationalization and localization issues
- Interoperability issues
- Miscellaneous issues
- Fibre Channel adapter issues
- Deployment issues
MirrorView resource cannot be brought online because of invalid security file
If a configured MirrorView resource cannot be brought online successfully, the problem may be an invalid security file. Review the steps for executing the addArrayuser action in the Cluster Server Hardware Replication Agent for EMC MirrorView Configuration Guide and verify that the steps were followed correctly. If you did not specify a password as an Action Argument when executing the addArrayUser action, an invalid security file for the SYSTEM user is created on the local and remote arrays. Executing the addArrayuser action again with a valid password does not overwrite the invalid security file.
To resolve this issue, you must modify the addArrayUser.pl action script and re-execute it to remove the invalid security file. The addArrayUser.pl
script is located in the directory, %ProgramFiles%\Veritas\cluster server\bin\MirrorView\actions.
Make a copy of the original addArrayUser.pl script before you make any changes to the script.
The following procedure removes the security file created for the SYSTEM user. (769418)
To remove the security file created for the SYSTEM user
- In the addArrayUser.pl script, replace the line:
my $cmd = "\"" . $java_home . "\\java\" -jar \"" . $NaviCliHome . "\\navicli.jar\" -h " . $LocalArraySPNames[$i] . " -AddUserSecurity -Password $arrayPasswd -Scope 0";
with the line:
my $cmd = "\"" . $java_home . "\\java\" -jar \"" . $NaviCliHome . "\\navicli.jar\" -h " . $LocalArraySPNames[$i] . " -RemoveUserSecurity";
- In the addArrayUser.pl script, replace the line:
my $cmd = "\"" . $java_home . "\\java\" -jar \"" . $NaviCliHome . "\\navicli.jar\" -h " . $RemoteArraySPNames[$i] . " -AddUserSecurity -Password $arrayPasswd -Scope 0";
with the line:
my $cmd = "\"" . $java_home . "\\java\" -jar \"" . $NaviCliHome . "\\navicli.jar\" -h " . $RemoteArraySPNames[$i] . " -RemoveUserSecurity";
- After you have modified the addArrayUser.pl script, save the changes.
- Execute the addArrayUser action to remove the invalid security file. Consult the Cluster Server Hardware Replication Agent for EMC MirrorView Configuration Guide for more details on executing the addArrayUser action. You do not need to specify an Action Argument.
- The action should complete successfully. If an error is returned, verify that the changes to the addArrayUser.pl script were made correctly and verify that the script is in the correct location.
- After the invalid security file has been removed, revert the modified addArrayUser.pl script back to the original script, and follow the procedure for executing the addArrayUser action again.