How to collect logs from a container MSDP/VDD instance on Access
As of Access 8.0 (WORM) or 8.1 and beyond (both WORM and non-WORM), Access runs the MSDP (aka VDD, Veritas Data Deduplication) processes within a Docker/Podman container. You can use one of the following methods to collect MSDP logs from the instance.
Once the files are generated, you can use the LogBrowser (Log Transfer Console) to download them.
Debuginfo method:
By using the Access Management (cluster) CLISH, you can choose to collect only the VDD module:
Support Debuginfo:
Collecting time-based and archived logs:https://sort.veritas.com/doc_viewer/#/content?id=146126434-161714788-0%2Fv164304474-161714788
> support debuginfo upload <nodename> <debug-URL> <module>
To collect only VDD logs, you would specify the module as 'vdd':
> support debuginfo upload accessn1 file:///log/ vdd
Please wait. Debug information is being collected. It will take few minutes to complete.
Remove the debuginfo .tar files after the files are uploaded to the server.
vdd module logs from accessn1 is starting, please wait.....
accessn1 log collection is complete.
accessn1 uploading /log/nas_debuginfo/accessn1_202502251314.tar.xz to file:///log/, please wait.....
accessn1 log upload /log/nas_debuginfo/accessn1_202502251314.tar.xz to file:///log/ is complete.
We're specifying to collect from appliance node 'accessn1' and using the 'file:' debug URL to copy these files directly to /log/ of whichever node is running the 'console' service:
accessclus> support services showall
Service accessn1 accessn2
------- ------------- -------------
...
console ONLINE OFFLINE
...
Since 'console' is online on accessn1, the logs generated will be uploaded to the /log/ directory on node 01. The VDD logs are cluster-mounted so they're accessible on either node, regardless of which one is running the MSDP/VDD instance.
The output file is copied from /log/nas_debuginfo/ to /log/ and can be collected using the Log Transfer Console (logbrowser).
Elevated Support Shell method:
The VDD logs are accessible from Access within an elevated shell.
[access-8.3] accessn1.example.com > support elevate
<!-- Maintenance Mode --!>
maintenance's password:
accessn1:~ #
There is a symlink in the VRTSnas logs directory for each VDD instance, pointing to the source filesystem where the spoold/spad logs are kept.
Access logs location: /opt/VRTSnas/log/
The Dedupe logs are at the following location, where "msdp-engine" is the name of the MSDP/VDD instance:
/opt/VRTSnas/log/dedupe_store_link_msdp-engine/spad/spad.log
/opt/VRTSnas/log/dedupe_store_link_msdp-engine/spoold/spoold.log
In the below example, there are two VDD instances, each with their own symlink to a different directory.
accessn1:/opt/VRTSnas/log/ # ls -l |grep dedupe_storelrwxrwxrwx 1 root root 25 Sep 9 12:56 dedupe_store_link_msdp-engine20_4 -> /vx/D3_7142838/dedupe/log
lrwxrwxrwx 1 root root 24 Dec 3 09:38 dedupe_store_link_msdpworm -> /vx/wormvddfs/dedupe/log
accessn1:/opt/VRTSnas/log/ # cd dedupe_store_link_msdp-engine20_4
accessn1:/opt/VRTSnas/log/dedupe_store_link_msdp-engine20_4 # ll
total 128896
drwxr-x--- 2 msdpsvc pduser 96 Sep 9 12:53 crash
drwxrwx---+ 2 msdpsvc pduser 96 Feb 25 10:24 debug
-rw-r--r-- 1 msdpsvc pduser 1061 Feb 14 12:11 engine-health.log
-rw-r----- 1 msdpsvc pduser 351 Feb 14 12:10 fslockd.log
-rw-r----- 1 msdpsvc pduser 1283 Feb 14 12:11 health-server.log
drwxr-x--- 3 msdpsvc pduser 96 Sep 9 12:53 nbcert
-rw-r----- 1 msdpsvc pduser 13355 Sep 9 12:54 pdde-config.log
-rw-r----- 1 msdpsvc pduser 14787083 Feb 25 13:30 pdde-health.log
-rw-r--r-- 1 msdpsvc pduser 15298 Feb 14 12:10 pdde-mgmt.log
-rw-r--r-- 1 msdpsvc pduser 1149 Feb 14 12:11 pdde-resize.log
-rw-r----- 1 msdpsvc pduser 46510 Feb 14 12:11 pdde-server.log
-rw-r----- 1 msdpsvc pduser 31364 Feb 14 12:10 pdde-setup.log
-rw-rw---- 1 msdpsvc pduser 100687984 Feb 25 13:21 pdde-shell.log
-rw-r--r-- 1 msdpsvc pduser 171 Sep 9 12:53 pdde-tune.log
drwxr-x--x 3 msdpsvc pduser 8192 Feb 14 12:10 spad
drwxr-xr-x 3 msdpsvc pduser 8192 Feb 23 04:33 spoold
drwxr-x--- 3 msdpsvc pduser 96 Sep 9 12:53 vpfs
From here, the spoold/spad directories can be browsed manually to review and/or collect whichever files may be needed.
(8.1 or later) You can also print the contents of /shared/conf/dedupe/dedupe.yml to find the log path for the VDD instance(s):
accessn1:/vx/D3_7142838/dedupe/log # cat /shared/conf/dedupe/dedupe.ymldedupe:
VERSION: '7.0'
msdp-engine20_4:
affinity: accessn1
catalog_filesystem: CAT_4404778
config_status: 'yes'
dedupe_storage_size_gb: 10240
filesystems:
- D3_7142838
host_based: false
logpath: /vx/D3_7142838/dedupe/log <<<<
msdp_version: '20.4'
pdregistry_path: /vx/D3_7142838/dedupe/etc/pdregistry.cfg
secondary_vips: []
vip: 192.168.10.140
worm: false
msdpworm:
affinity: accessn2
catalog_filesystem: wormcatfs
config_status: 'yes'
dedupe_storage_size_gb: 10
filesystems:
- wormvddfs
host_based: false
logpath: /vx/wormvddfs/dedupe/log <<<<
msdp_version: '20.4'
pdregistry_path: /vx/wormvddfs/dedupe/etc/pdregistry.cfg
secondary_vips: []
vip: 192.168.10.141
worm: true
MSDP Restricted Shell method:
You can connect directly to the MSDP-Restricted shell to collect logs as well.
Using SSH to directly connect to the MSDP instance using the instance IP and the Access administrator username/password:
(In the below example, the Access admin username is "accessadmin" and the IP is for the "msdp-engine20_4" instance.
https://sort.veritas.com/doc_viewer/#/content?id=146127092-161714787-0%2Fv152454187-161714787
# ssh accessadmin@192.168.10.140Password:
Last login: Tue Feb 25 10:24:42 2025 from 192.168.10.136
msdp-20.4 is starting (maximum 5 seconds).
Welcome to the Veritas NetBackup Deduplication Shell
This interface provides tab-completed options for managing
the lifecycle of your storage server.
* For a list of available commands, press '?'
* For a list of shell shortcuts, press 'Alt-s'
* To get more information on a command, press '?' while typing or
after tab-completing it
[msdp-20.4] accessclusvip1 >
You can also connect directly to the docker/podman container and "su - <admin user" within the docker container to connect to the restricted shell.
accessn1:~ # docker ps -aCONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e6706ec0e684 localhost/uss-engine/tool:20.4_latest /bin/sh -c sh 11 days ago Created msdp-engine20_4_tools
4f43a29c37ad localhost/uss-engine:20.4_latest /usr/sbin/init --... 11 days ago Up 11 days (healthy) msdp-engine20_4
accessn1:~ # docker exec -it msdp-engine20_4 bash
engine : su - accessadminLast login: Tue Feb 25 13:39:43 PST 2025 from 192.168.10.136 on pts/0
msdp-20.4 is starting (maximum 5 seconds).
Welcome to the Veritas NetBackup Deduplication Shell
This interface provides tab-completed options for managing
the lifecycle of your storage server.
* For a list of available commands, press '?'
* For a list of shell shortcuts, press 'Alt-s'
* To get more information on a command, press '?' while typing or
after tab-completing it
[msdp-20.4] accessclusvip1 >
To collect logs for the previous 2 days, you can use the below syntax to build the file list.
[msdp-20.4] accessclusvip1 > support MSDP-log collect mtime="-2"
/usr/bin/find: '/vx/D3_7142838/dedupe/log/vpfs/spws': Permission denied
/vx/D3_7142838/dedupe/log/pdde-health.log
/vx/D3_7142838/dedupe/log/pdde-shell.log
...
/vx/D3_7142838/dedupe/log/spoold/storaged.log
Successfully created file list /vx/D3_7142838/dedupe/log/debug/msdp-log.txt
Operation completed successfully
This command does not create an archive, but you can use the next command with the 'scp' argument to collect the files from the list and upload them to a remote server, specifying the username, hostname (or IP), and target path:
[msdp-20.4] accessclusvip1 > support MSDP-log scp scp_target=remote_user@linux_host1:/path_to_file
Creating a tar file from collected files..
Do you want to add MSDP log files to the tar file? (y/n) y
/usr/bin/tar: Removing leading `/' from member names
/usr/bin/tar: Removing leading `/' from hard link targets
Successfully created /vx/D3_7142838/dedupe/log/debug/accessclusvip1.tar (539M)
Compressing /vx/D3_7142838/dedupe/log/debug/accessclusvip1.tar
Uploading /vx/D3_7142838/dedupe/log/debug/accessclusvip1.tar.gz (33M) to remote_user@linux_host1:/path_to_file
Are you sure you want to upload? (y/n)
If the upload fails via SCP, the .tar.gz log package is kept in the 'debug' location:
accessn1:/vx/D3_7142838/dedupe/log/debug # ll
total 33344
-rw-rw-r-- 1 accessadmin pduser 34138725 Feb 25 13:46 accessclusvip1.tar.gz
From here, you can move, SCP, or extract the file as needed.
Downloading collected files using LogBrowser:
Once the files are generated within an Access node, the easiest way to download the files is to use the Log Transfer console (aka logbrowser). This creates a HTTP webserver in which you can browse the contents of /log/ on a per-node basis.
https://sort.veritas.com/doc_viewer/#/content?id=146126550-161714756-0%2Fv146276243-161714756
AppShell (appliance CLISH) > support logbrowser start
- [Info] V-409-960-1: The log transfer web service started successfully. To transfer the logs, access https://192.168.10.135:8514/appliance/logs/ using the local account or an account authenticated with Active Directory or LDAP. The log transfer web service will stop running after 720 minute(s).
Operation completed successfully
You can connect to a Windows client that has network access to the cluster node and access that URL with a web browser. The username/password will the Access administrator user.
Anything that's within the /log/ directory can be downloaded using the logbrowser utility in a web browser.
Once the files have been downloaded, it is recommended to stop the logbrowser service.
AppShell (appliance CLISH) > support logbrowser stop
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.