![Fujitsu ETERNUS SF Express V16.6 Migration Manual Download Page 43](http://html.mh-extra.com/html/fujitsu/eternus-sf-express-v16-6/eternus-sf-express-v16-6_migration-manual_121469043.webp)
absolute path. When the files related to the performance management function is not backed up, it is unnecessary to specify a
directory for the
tmpDir
.
# /mnt/dvd/Manager_unix/vuptools/esfpostinst.sh backupDir [tmpDir]
When the restore fails, after confirming the output error message and removing the cause of the failure, execute the command
again.
Point
-
Spaces and the characters " / ` * ? \ $ [ ] , % ! { } are not supported for directory names.
-
The number of characters in a directory name must be up to 220.
5.
Unmount the DVD-ROM.
Example:
# umount /mnt/dvd
6.
Eject the DVD-ROM.
7.
Restart the daemon of ETERNUS SF Manager.
# /opt/FJSVesfcm/bin/startesf.sh
3.2.3.2 Importing Configuration Information
Import the configuration information from the previous version by executing the
privileges.
Check that the managed devices and servers can be accessed before executing the
command.
# /opt/FJSVesfcm/bin/esfadm devconf import -all
After executing the
command, confirm that "Complete" is displayed in IMPORT STATUS column in the
In addition, confirm that "Complete" is displayed in STATUS column of the import status of the migration target resources. When
"Failed" is displayed, the import of configuration information has failed. Refer to "
12.2 What to Do When Error Occurs
" to take the
corrective action.
Note
When executing the
command, if a managed device or server is not accessible, the
command should be re-executed since the device configuration information is not imported.
3.2.3.3 Redefining Operational Environment
-
Restarting the performance monitoring
If the performance monitoring was performed with the previous version, restart the performance monitoring.
Refer to "Instruction for Performance Management" in the
ETERNUS SF Express Operation Guide
for information on how to restart
the performance monitoring.
Note
Information related to the captured capacity before the upgrade is not displayed on the Dashboard. Confirm with the Capacity
Graph screen of Thin Provisioning Pool.
- 19 -