NetBackup Snapshot Manager: After changing default storage location for podman images and temporary files, fluentd is not starting.
Problem
After changing default storage location for podman images and temporary files, fluentd is not starting.
Error Message
The following error maybe seen in flexsnap-cloudpoint.log when attempting to start flexsnap-fluentd:Starting container: flexsnap-fluentd ...b'{"cause":"no such container","message":"no container with name or ID \\"flexsnap-fluentd\\" found: no such
container","response":404}\n'
This error is also seen attempting to start flexsnap-fluentd manually:# podman start flexsnap-fluentd
Error: no container with name or ID "flexsnap-fluentd" found: no such container
Cause
The /etc/containers/storage.conf file was modified to change the default location for storing container images and temporary files.
Solution
NetBackup Snapshot Manager currently does not support changing the default location. It is necessary to reset the podman storage defaults.
https://www.veritas.com/content/support/en_US/doc/140789355-158266811-0/v140790136-158266811
NetBackup Snapshot Manager uses the following file systems on the host to store all the container images and files during installation:
/ (root file system)
/var
The /var file system is further used for container runtimes. Ensure that the host on which you install or upgrade NetBackup Snapshot Manager has sufficient space for the following components.
Table: Space considerations for NetBackup Snapshot Manager components
Component |
Space requirements |
---|---|
NetBackup Snapshot Manager containers |
30 GB free space |
NetBackup Snapshot Manager agents and plug-ins |
350 MB free space, for every NetBackup Snapshot Manager plug-in and agent configured |