Migrating the file hash data from one server to another
You might need to migrate the file hash data from one server to another when disk is full or for any other reasons.
To migrate the hash from one server to another
- Stop the crond and spws services on the existing server:
service crond stop /usr/openv/pdde/vpfs/etc/init.d/pdde-spws stop
- Configure the file hash service on the new server.
- Stop the crond and spws services on the new server:
service crond stop /usr/openv/pdde/vpfs/etc/init.d/pdde-spws stop
- Copy the following folders from the existing file hash server to
<new_file_hash_storage_path>/hashdb/on the new file hash server:<existing_file_hash_storage_path>/hashdb/recv < existing_file_hash_storage_path>/hashdb/catalog < existing_file_hash_storage_path>/hashdb/sqlite < existing_file_hash_storage_path>/hashdb/history
- Change the folder's owner to file hash service user on the new file hash server.
Get the service user on the new file hash server.
cat /usr/openv/netbackup/bp.conf |grep "^SERVICE_USER"
Change the owner.
chown -Rv ${service_user} <new_file_hash_storage_path>/hashdb/
- Start the crond and spws services on the new server:
service crond start /usr/openv/pdde/vpfs/etc/init.d/pdde-spws start
- Enable the new file hash server on the NetBackup primary server.
See Enabling the file hash server on the NetBackup primary server.
Note:
After you enable the new file hash server on the primary server, the existing file hash server will no longer be used.