Please enter search query.
Search <book_title>...
Veritas Access Troubleshooting Guide
Last Published:
2018-08-10
Product(s):
Appliances (7.3.2)
Platform: 3340
- 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 Veritas Access CIFS issues
- Troubleshooting Veritas Access GUI startup issues
Insufficient delay between two successive OpenStack commands may result in failure
If sufficient delay is not there between two successive OpenStack commands, it may lead to failure of the operation in some cases.
For example:
# for i in {01..32}; do cinder create --image zesty-server-cloudimg- amd64 --volume-type vrts_vol_type --name zesty-vol-$i 10; done
The command may fail to create the new volumes.
To avoid this kind of failure, introduce sufficient delay between the commands by adding some sleep time.
For example:
# for i in {01..32}; do cinder create --image zesty-server-cloudimg-amd64 --volume-type vrts_vol_type --name zesty-vol-$i 10;sleep 20; done