Unable to see Backups on physical disk

Technical Support
,
1

OS Name/Version: Ubuntu 22.04.5

Product Name/Version: AMP Release “Phobos” v2.6.1.6

Problem Description:
Can’t see Backups on Host

I had issues with taking backups, as in the whole backup menu being missing. After doing some research, I figured it might have been an issue with the Deployment Settings and overall directory/mount binding for my setup.

I currently have set the default settings to:
CustomMountBinds = {"/home/amp/backups":"/LocalBackups"}
LocalFileBackupPlugin.Storage.StorePath = /home/amp/backups/{{InstanceName}}/

Doing this now shows me the Backups Menu in new instances, I can schedule and create backups manually. However I can’t see the backup files in my host system, since I am using Docker for all of my instances. I can see the Backups in the Web GUI and can download them but I’d prefer having them on my physical storage as well so I can copy them onto my fileserver (cronjob).

Leaving that aside for now, I’d like to resolve the issue that the Backup files are being shown physically as well. I also checked for the permissions, the amp user has everything it needs:
drwxr-xr-x 2 amp amp 4096 Apr 20 08:13 backups

It is worth to note that the Backups aren’t being written to the “default” Backups folder, that is being created with the instance, as well as that I use a seperate mounting directory on my nvme to store my instances.
Path: /mnt/nvme/amp_data/

Here’s also an output of the current LocalFileBackupPlugin.kvp for a test-instance that I created:

root@gameserver:/mnt/nvme/amp_data/test01# cat LocalFileBackupPlugin.kvp
Limits.MaxTotalSizeMB=20280
Limits.MaxIndividualSizeMB=10140
Limits.MaxBackupCount=28
Limits.ReplacePolicy=DoNothing
Limits.MaxDirectoryTraversalDepth=8
Limits.CompressionLevel=Optimal
Limits.UseAutomaticExclusions=False
Limits.ShutdownTimeout=60
Storage.StorePath=/home/amp/backups/{{InstanceName}}/
Storage.OverrideOriginDirectory=False
Storage.OriginDirectory=
Storage.UseVDS=True

Steps to reproduce:

  • Log in to AMP
  • Manage an instance and see no Backups menu
  • In an instance, add a trigger then add a task and see there is no Take a backup option.
  • Adjust default settings with values as shown above
  • Adjust permissions of directories if not already created
  • Search for backup in the search bar in the top right and nothing is found.

Actions taken to resolve so far:

  • Changed default settings
  • Tried different directories (failure on nvme)
  • Changed permissions of directories
  • Confirmed that the amp user has all necessary permissions
  • Checked several AMP_Logs with no hints on what the issue behind this could be
2

You’re mounting a path into the docker container but then using a completely different path in the backup settings?

3

I suppose that could be the issue? Maybe I just got things confused up here. I want to use the /home/amp/backups as the main directory where the backups are being written to. Is that a change I have to do in the default settings?

Edit 1:

I changed the default settings to the following:

CustomMountBinds 	{"/home/amp/backups/":"/home/amp/backups/"} 	
LocalFileBackupPlugin.Storage.StorePath 	/home/amp/backups/{{InstanceName}}/

Still no luck of the backups being written onto the host for some reason.

I feel like I’m missing something very obvious here, I did check in the containers and the backups are being written to /home/amp/backups/{{InstanceName}}/ so I’m wondering why it’s not being written to the Host.

Edit 2:
I was able to fix it now after running through the docker containers. My default configs are now:
CustomMountBinds {"/home/amp/backups":"/AMP/Backups"}
LocalFileBackupPlugin.Storage.StorePath /AMP/Backups/

This way the backups will just be put into the interal instance folder, however I still struggle with using the Variables for Default Mount Bindings, I want to set it to /home/amp/backups/{{InstanceName}} as the hints on the GUI suggest but it just creates it plainly like that, which confuses me a lot.

Unless anyone has an idea for that, I’d say this issue is solved.

4

Hey! Been trying to do something similar myself and either it wouldn’t work or would also do {{InstanceName}} as a literal folder named that.
I’ve been trying to do it via the default deployments gui, am I misunderstanding where to change the config?