Veritas Access Release Notes
- Overview of Veritas Access
- Fixed issues
- Software limitations
- Flexible Storage Sharing limitations
- Limitations related to installation and upgrade
- Limitation related to replication
- Known issues
- Veritas Access known issues
- Admin issues
- Backup issues
- CIFS issues
- Deduplication issues
- FTP issues
- General issues
- GUI issues
- Installation and configuration issues
- Internationalization (I18N) issues
- Networking issues
- NFS issues
- ObjectAccess issues
- OpenDedup issues
- OpenStack issues
- Replication issues
- SDS known issues
- SmartIO issues
- Storage issues
- System issues
- Target issues
- Upgrade issues
- Veritas Data Deduplication issues
- Veritas Access known issues
- Getting help
Rollback refresh fails when running it after running Storage> fs growby or growto commands
A rollback refresh fails if you run the rollback after running the Storage> fs growby or Storage> fs growto commands.
You create a rollback of a file system. After creating a rollback of a file system, you use the Storage> fs growby or Storage> fs growto commands to increate the size of the file system. If you perform a Storage> rollback refresh on the previously created rollback, the operation fails.
Currently the Storage> rollback command is designed to allow only using the same size in the Storage> rollback refresh command as that of the source file system. Automatically resizing snapshots before performing a rollback refresh is complicated, especially when a storage pool does not have enough space. The ability to automatically resize a snapshot is not implemented yet.
Workaround:
There is no workaround.