For the "logical" provisioning mode, the "sync" instance is not yet supported (although, it is possible to implement based on logical replication) and the only option to get fresh data on Database Lab Engine is to refresh it fully. Follow these instructions to automate this process. Note, that it is designed for ZFS; if you have a different setup, adjust the snippets accordingly.
Note, that the process described here requires a maintenance window (brief period of downtime) for the Database Lab Engine. Also, the existing clones are deleted and completely lost during the process. It means that the proper planning of the maintenance windows is needed.
If you are using the "physical" privisoning mode, read how to configure the "sync" instance instead.
Stop and remove the existing containers, then clean up the data directory and destroy the pool:
Further, we will need
$DBLAB_DISK environment variable. It must contain the device name corresponding to the disk where all the Database Lab Engine data will be stored.
To understand what needs to be specified in
$DBLAB_DISK in your particular case, check the output of
AWS local ephemeral NVMe disks; EBS volumes for instances built on the Nitro system:$ sudo lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT...xvda 202:0 0 8G 0 disk└─xvda1 202:1 0 8G 0 part /nvme0n1 259:0 0 777G 0 disk$ export DBLAB_DISK="/dev/nvme0n1"
AWS EBS volumes for older (pre-Nitro) EC2 instances:$ sudo lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT...xvda 202:0 0 8G 0 disk└─xvda1 202:1 0 8G 0 part /xvdb 202:16 0 777G 0 disk$ export DBLAB_DISK="/dev/xvdb"
Optionally, if you do it manually, check the logs:
And check the instance status using the client CLI: