Database Backup Not Listed in Operations Console (8.1 SP1 Patch 5)

[TyraDowns]

I am attempting to restore a customer database in my test environment.

The customer is running AM 8.1 SP1 Patch 5 and I am running the same version in my test environment.

I copy the customer database to /opt/rsa/am/backup directory on my AM appliance but when I attempt to restore the database from the Operations Console, it doesn’t appear in the list.  Something I should note is that the customer database is 47MB.  I performed this same task with a different customer database last week and was successful.  The successful restore database size was 18MB.    

Does anyone have any ideas???

[JustinMitchell]

Guessing permissions related. Make sure rsaadmin user:group (chown rsaadmin:rsaadmin) owns the backup you have dropped in /opt/rsa/am/backup. After confirming, run "chmod 770" against the backup package and try again.

[TyraDowns]

Checking the permissions and ownership was one of the first things I tried thinking that would be the culprit.  I am wondering if the size of the database could be an issue.  Do you know if there are logs that would provide more detail around why the backup is not considered a "valid" backup file?

[StevenSpicer]

Dumb question: what's the name of the backup file?

[ChristopherSalv]

Did you mean you ran a backup via the UI? I'm going to guess you're backing up to the local AM server vs the remote location, or are you backing up to a remote location, then copying the backup file to the AM server via scp or the like? 

Backup folder permissions should look like this

drwx------  3 rsaadmin rsaadmin 4.0K Apr 17 10:56 backup

Backup file permissions should look like this

-rw-------  1 rsaadmin rsaadmin 7.5M Apr 17 10:57 201904171056.RSAbackup

I copy the customer database to /opt/rsa/am/backup directory on my AM appliance but when I attempt to restore the database from the Operations Console, it doesn’t appear in the list.

[JustinMitchell]

Ensure the backup has the ".RSAbackup" extension...

[TyraDowns]

The database backup file was a file that I received from a customer to restore to my test environment. In order to restore the database backup to my test environment I copied the customer’s backup file to my AM instance (directory location /opt/rsa/am/backup). Logged into the Operations Console and proceeded to restore the database backup. The customer’s database backup file was not listed as an option of database files to restore. 

Does that make sense?

[TyraDowns]

Resolution: 

The database backup file provided by the customer was corrupted. Attempted to edit the backup file using 7-Zip and found that the file was broken. 

Had the customer re-copy the backup file from their remote backup location and re-send; restore was successful. 

Using 7-Zip is a good tool to determine if a file is corrupted. 

[JustinMitchell]

Double check the extension of the backup is ".RSAbackup". The backup file must end with this extension.