Issues configuring remote backup location FTP, SCP, for PGP Universal Server
|Article:TECH200737|||||Created: 2012-12-11|||||Updated: 2013-06-25|||||Article URL http://www.symantec.com/docs/TECH200737|
The configuration for the remote backup location does not seem to work.
PGP Universal Server 3.2.x
Symantec Encryption Management Server 3.3.x
The question how to configure remote backup location often arise with implementation backup policy strategies in corporate environment.
Cause for missing backup might be improper specification of FTP/SCP location on SEMS server or remote FTP/SCP server unavailability or misconfiguration.
In the PGP Universal Server Backup Location you need to insert:
- Hostname (you can use IP as well)
- Directory (seen from the point of view of the user) *
- Port (according to the protocol and configuration of the FTP/SCP server)
* This will depend on how you configure the FTP or SCP server. For instance, you want to backup to X:/PGP-Backup :
Example 1 - default "home directory" of the user is "X:/PGP", so I you have to configure in the PGP Universal Server the directory as: /
Example 2 - default "home directory" of the user is "X:/", so you have to configure in the PGP Universal Server the directory as: /PGP-Backup
An easy way to find it is to:
- Place a test file inside the directory you want to have the backups.
- With WinSCP or similar, open a session to the server.
- The first folder presented will be the root for that user, thus if you see immediately your test file you need to use / in the configuration window.
- If you see an higher-level directory, you need to browse until you reach the one you want. Then, still inside WinSCP (Commands > Open Terminal), open a console session and enter the command 'pwd', it will output the directory path you need to configure in PGP Universal Server.
- \ (backslash) is used when the destination is a Windows directory
- / (forward slash) when the directory is in Unix-like systems
- Use the exact case (the destination might be case sensitive)
- Ensure that the user has read/write/delete permissions in the target directory
Article URL http://www.symantec.com/docs/TECH200737