Please enter search query.
Search <book_title>...
Veritas Access Release Notes
Last Published:
2020-10-16
Product(s):
Access (7.4.2)
Platform: Linux
- 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
The Veritas Data Deduplication storage server does not come online on a newly added node in the cluster if the node was offline when you configured deduplication
If a node is not online when you configure deduplication, the configuration file present in the node is not in sync with the cluster configuration. The soft link created during configuration is also not present in the node. When the node is made online, it does not get the required configuration details for starting the service.
Workaround:
Copy the
/opt/VRTSnas/conf/dedupe.yml
file from the master node to the newly added node.Create a soft link,
/etc/pdregistry.cfg
, that points to the/vx/fs_name/dedupe/etc/pdregistry.cfg
configuration file by using the following command on the newly added node:ln -sf /vx/fs_name/dedupe/etc/pdregistry.cfg /etc/pdregistry.cfg
Where fs_name is the name of the file system provided during configuration.