Veritas Access Troubleshooting Guide
- Introduction
- General troubleshooting procedures
- Monitoring Veritas Access
- Common recovery procedures
- Bringing services online
- Speeding up replication
- Troubleshooting the Veritas Access cloud as a tier feature
- Troubleshooting Veritas Access installation and configuration issues
- Troubleshooting the LTR upgrade
- Troubleshooting Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
Troubleshooting pre-upgrade issues for LTR
Following are the pre-upgrade scenarios with the recommended workaround:
Failure in provisioning of
odd_cache_fs
: Ensure that sufficient storage space is available in default pool(s) that is configured for ObjectAccess.
Failure in backup of configuration file
: Ensure that theodd_vipgrp_map.conf
file is successfully copied to/shared/opendedup/
.Failure in backup of XML configuration files
: Ensure that all the OpenDedup volume configuration XML files are successfully copied to/shared/opendedup/sdfs/
.Failure in shutdown of OpenDedup volume(s)
:
Ensure that the volume is unmounted by using the mount -t fuse command.
Ensure all the jsvc processes are stopped. If the processes are not stopped, use the kill command to stop them.
Shutdown of the OpenDedup volume may result in java stack trace to be printed on console. This can be ignored as long as the volume is unmounted.
Failure in backup of the OpenDedup cache data
: Ensure that the size of the local cache location, that is,/opt/sdfs/ volumes/<vol-name>
is equivalent to the shared cache location, that is,/vx/odd_cache_fs/volumes/<vol-name>
.