Starting Managed Server Transactions; Resuming Operation - Fujitsu ETERNUS SF Express V16.6 Migration Manual

Table of Contents

Advertisement

5.
Perform the kernel parameter tuning.
See
Refer to "Before Installation" in "Installation of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this
version for information on tuning.
6.
Check the cluster application (transaction) is stopped.
If not stopped, refer to the relevant cluster software manuals for information on stopping it.
7.2.2.6

Starting Managed Server Transactions

After performing
"7.2.2.4 Tasks to Be Performed After Upgrade (Primary
(Secondary
Node)", perform the following procedure:
1.
Check that the cluster application (transaction) is started on the primary node.
If not started, start the cluster application (transaction) of ETERNUS SF Manager.
Refer to the relevant cluster software manuals for information on starting it.
2.
If Managed Server transactions coexist in a clustered system, start the Managed Server transactions in the primary node for a
target transaction.
Refer to the relevant cluster software manuals to start the Managed Server transactions.
If multiple Managed Server transactions exist, apply this procedure for each Managed Server transaction.
3.
Start the local transactions on all the nodes.
Start the communication daemon for local transactions of AdvancedCopy Manager's manager.
Refer to "Starting and Stopping Communication Daemon" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant
to the OS of the Management Server for this version for information on starting the daemon.
Subsequently, go to
"7.2.3 Resuming

7.2.3 Resuming Operation

When the tasks described above have been performed, the upgrade of the Storage Cruiser's manager is complete. Restart operation
after performing the following actions.
1.
Changing SELinux Setting to "enforcing" Mode
When you change the SELinux setting to "enforcing" mode during the upgrade, refer to the following section in the chapter "Setup
of ETERNUS SF Manager" in the ETERNUS SF Installation and Setup Guide for this version and restart the operation after the
installation of the SELinux policy module for snmptrapd.
-
"Setup of Storage Cruiser's Manager" > "SNMP Trap Setting" > "SNMP Trap Setting (for Linux)" > "Installation of SELinux Policy
Module for SNMP Trap Daemon"
2.
Deleting Web Browser's Cache
If operating Web Console from the same web browser as before the upgrade, delete the web browser's cache prior to operation.
3.
Reloading Device Information
If all the following conditions are satisfied, this procedure is not required:
-
The pre-upgrade environment is Version 16.3.
-
In the pre-upgrade environment, the patch for Problem Report Number PH09090 has already been applied to the
Management Server.
-
The storage device that is in use is the ETERNUS DX S3 series or the ETERNUS DX200F, whose firmware version is V10L60 or
later.
If the above conditions are not satisfied and you use the new supported function from this version level, perform the following
operations with Web Console to reload the server information.
Operation".
- 104 -
Node)" and
"7.2.2.5 Tasks to Be Performed After Upgrade

Advertisement

Table of Contents
loading

This manual is also suitable for:

Eternus sf storage cruiser v16.6Eternus sf advancedcopy manager v16.6

Table of Contents