Using Google Cloud Storage (S3) as a primary storage for Enterprise Vault
- Overview
- Configuring Google Cloud Storage (S3) primary partition
- Troubleshooting
Using the DTrace utility for enabling SDK to view diagnostic logs
If you encounter any issues in storing or retrieving archived data with the Enterprise Vault Google Cloud Storage (S3) primary partition, run the DTrace utility to identify the cause for the issues.
You can also add an SDK-provided log level on the partition, which has been incorporated in the DTrace utility as additional support for troubleshooting. To details about enabling the SDK logs for troubleshooting purposes, See Configuring Google Cloud Storage (S3) primary partition.
The DTrace utility lets you monitor multiple services simultaneously, write the trace to a file, filter for specific words, and trigger tracing based on the filters.
The following table lists the processes for getting the diagnostic logs with DTrace.
Note:
Enterprise Vault recommends setting the monitoring level to in all cases.
Table:
Monitor this process | To do this |
|---|---|
StorageArchive.exe | Get diagnostic logs for archived files written in the Google Cloud Storage (S3). |
StorageOnlineOpns.exe | Get diagnostic logs for the retrieved and restored files in the Google Cloud Storage (S3). |
StorageFileWatch.exe | Get the diagnostic logs to know whether items are secure or not based on the replication setting configured on Google Cloud Storage (S3) partition. |
StorageManagement.exe | View the logged information when Enterprise Vault checks whether the partition has been configured correctly and validates the configured settings. Enterprise Vault logs this information when you click the button on the page of the vault store partition page and the vault store partition creation wizard. |
Note:
For more information on DTrace, see the Enterprise Vault™ Utilities Guide.