- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Storage Direct Agent Overview
- Enabling the Storage Direct Agent for VMAX Systems
- About the Storage Direct agent
- Storage Direct agent prerequisites
- Storage Direct agent limitations
- Provide asset configuration file during update
- Storage Direct agent coexistence with other application agents is not supported
- Configuration Change Management is not supported for existing Storage Direct users
- Storage Direct policies do not support Smart Scale system pools
- Updating DD domain name is not supported
- Installing or updating the Storage Direct agent
- Updating an existing Storage Direct agent
- Changing the preferred host address
- Managing Storage, Assets, and Protection
- About asset sources, assets, and storage
- Add protection storage
- Manage the Storage Direct agent
- Enable an asset source
- Add and discover the SMIS server for the Storage Direct agent
- Add a self-service protection policy for Storage Direct
- Add a centralized protection policy for Storage Direct
- Add a service-level agreement
- Add assets to an existing storage group protection policy
- Remove assets from an existing storage group protection policy
- Edit the retention period for backup copies
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Delete backup copies
- Restoring a Storage Direct VMAX storage group
- Restore backup copies from replication DD when source Storage Direct agent host, PowerProtect Data Manager server, and VMAX are unavailable
- Manage the PowerProtect agent service
- About the PowerProtect agent service
- Start, stop, or obtain the status of the PowerProtect agent service
- Troubleshooting PowerProtect agent service installations
- Troubleshooting PowerProtect agent service operations
- Register the PowerProtect agent service to a different server address on Windows
- Recovering the PowerProtect agent service from a disaster
- Storage Direct Best Practices and Troubleshooting
- Storage Direct agent limitations
- Provide asset configuration file during update
- Storage Direct agent coexistence with other application agents is not supported
- Configuration Change Management is not supported for existing Storage Direct users
- Storage Direct policies do not support Smart Scale system pools
- Updating DD domain name is not supported
- Troubleshooting installation and operation
- Troubleshooting backups
- Storage Direct agent limitations
- Glossary
PowerProtect Data Manager 19.14 Storage Direct User Guide
Troubleshooting SDFSA install/update failure when using absolute path
An SDFSA installation or update fails when performed using the absolute path. For example:
Installation using absolute path
[root@xxxxx /]# /Softwares/builds/sdfsa_19.x_36/install.sh 2019/09/18 23:18:42 adm-agent rpm not found in current working directory...
Update using absolute path
[root@xxxxx sd_cfs]# /Softwares/builds/sdfsa_19.x_40/install.sh -u 2019/09/17 01:49:35 storagedirectagent rpm not found in current working directory... /Softwares/builds/sdfsa_19.x_40/install.sh: line 595: [: -gt: unary operator expected /Softwares/builds/sdfsa_19.x_40/install.sh: line 597: [: -gt: unary operator expected /Softwares/builds/sdfsa_19.x_40/install.sh: line 599: [: -gt: unary operator expected /Softwares/builds/sdfsa_19.x_40/install.sh: line 601: [: -gt: unary operator expected 2019/09/17 01:49:35 storagedirectagent rpm not found in current working directory... rpm -U --quiet --test rpm: no packages given for install 2019/09/17 01:49:35 storagedirectagent upgrade failed... 2019/09/17 01:49:35 storagedirectagent upgrade failed...
To work around this issue, change the directory to the location of install.sh and run ./install.sh.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\