After changing the Database Target Account and Device to a new host, the scheduled database backups fail to get copied to the new host. The session log shows an error related to the old host. "PAM-CMN-2141: Error uploading gkscheddbxxxxxx.gz to [email protected]:/var/pam/dbbackup!"
4.1.3-4.1.6
PAM 4.1.3 introduced new functional enhancement Admins Can Now See All Target Account Information When Scheduling a Database Backup. This allows the selection of one of multiple target accounts on the UI. But when the actual DB backup runs, it is possible that it finds the wrong target application with name "CAPAM_DatabaseBackup" to get the device address and therefore uses the wrong address when trying to securely copy the backup file.
As a workaround, change the old target application to point to the new backup device, instead of creating a new target application for it. Update the target account credentials as needed.
This problem is fixed in 4.1.7+ and 4.2+, see the following item on page Resolved Issues in 4.1.7:
33588631 DE583599 Database backup scheduler gets stuck trying to send a file to old target server.