This page explains how to perform common tasks for AOF and RDB persistence.
For more information about persistence, see Persistence overview.
RDB persistence tasks
This section gives instructions for common RDB persistence tasks.
Create an instance that uses RDB persistence
Console
In the Data persistence strategy section, select the Memory Snapshot option when Creating an instance.
Select a snapshot interval from the Snapshot interval menu.
Select a start time from the Start time (local time) menu. Local time is the time where you are located.
gcloud
To create an instance that uses RDB persistence, run the create
command:
gcloud beta memorystore instances create instance \ --location=region-id \ --psc-auto-connections=network=projects/project-id/global/networks/network-id,projectId=project-id \ --replica-count=replica-count \ --node-type=node-type \ --shard-count=shard-count \ --persistence-config-mode=rdb \ --rdb-config-snapshot-period=snapshot-interval \ --rdb-config-snapshot-start-time=time
Replace the following:
instance is is the ID of the Memorystore for Valkey instance you're creating. Your instance ID must be 1 to 63 characters and use only lowercase letters, numbers, or hyphens. It must start with a lowercase letter and end with a lowercase letter or number.
region-id is the region where you want the instance placed.
project-id is the ID of the project where you want to create your instance.
network-id is the ID of the network you want to use to create your instance.
replica-count is your chosen number of replicas (per shard). Accepted values are
0
,1
, and2
.node-type is your chosen node type. Accepted values are:
shared-core-nano
standard-small
highmem-medium
highmem-xlarge
For more details on node types and instance configurations, see Instance and node specification.
shard-count determines the number of shards in your instance. Shard count determines the total memory capacity for storing instance data. For more information about instance specification, see Instance and node specification.
snapshot-interval is your chosen interval. Accepted values are
1h
,6h
,12h
, and24h
. The default value is24h
.time is the start time of your RDB snapshot in the ISO 1801 format. For example:
2024-04-08T03:00:00Z
. If you don't choose a start time when creating an instance that uses RDB persistence, the first snapshot is taken immediately.
Enable RDB persistence for an existing instance
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select the Memory Snapshot option.
Select a snapshot interval from the Snapshot interval menu.
Select a start time from the Start time (local time) menu. Local time is the time where you are located.
Click the Update Instance button.
gcloud
To enable RDB persistence for an existing instance, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --persistence-config-mode=rdb \ --rdb-config-snapshot-period=snapshot-interval \ --rdb-config-snapshot-start-time=time
Replace the following:
instance is the ID of the Memorystore for Valkey instance you're creating. Your instance ID must be 1 to 63 characters and use only lowercase letters, numbers, or hyphens. It must start with a lowercase letter and end with a lowercase letter or number.
region-id is the region where you want the instance placed.
snapshot-interval is your chosen interval. Accepted values are
1h
,6h
,12h
, and24h
. The default value is24h
.time is the start time of your RDB snapshot in the ISO 1801 format. For example:
2024-04-08T03:00:00Z
. If you don't choose a start time when enabling RDB persistence on an existing instance, the first snapshot is taken immediately.
Adjust RDB snapshot interval
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select your chosen snapshot interval from the Snapshot interval menu.
Click the Update Instance button.
gcloud
To adjust the RDB snapshot interval, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --rdb-config-snapshot-period=snapshot-interval
Replace the following:
snapshot-interval is your chosen interval. Accepted values are
1h
,6h
,12h
, and24h
. The default value is24h
.time is your chosen start time in the ISO 1801 format. For example:
2024-04-08T03:00:00Z
.
Adjust the RDB snapshot start time
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select your chosen start time from the Start time (local time) menu. Local time is the time where you are located.
Click the Update Instance button.
gcloud
To adjust the RDB snapshot start time, run the update
command. Changing the start time also changes the snapshot alignment time. For example, if you change the start time from 6:00 AM to 6:30 AM, with a snapshot frequency of 1h
, future snapshots align at 7:30 AM, 8:30 AM, 9:30 AM and every hour after that.
gcloud beta memorystore instances update instance \ --location=region-id \ --rdb-config-snapshot-start-time=time
Replace the following:
- time is your chosen start time in the ISO 1801 format. For example:
2024-04-08T03:00:00Z
.
Pause RDB persistence
gcloud
To pause RDB persistence, you must set the snapshot schedule to a future time. When you want to unpause snapshots, you can re-adjust the time to when you want the next snapshot to occur.
To pause RDB snapshots, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --rdb-config-snapshot-start-time=time
Replace the following:
- time is your chosen start time in the ISO 1801 format. For example:
2024-04-08T03:00:00Z
.
Disable RDB persistence
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select the No persistence option.
Click the Update Instance button.
gcloud
To disable RDB persistence, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --persistence-config-mode=disabled
Monitor RDB persistence
You can use Cloud Monitoring to view metrics for RDB persistence.
For a list of available metrics for RDB persistence, see persistence metrics.
AOF persistence tasks
This section gives instructions for common AOF persistence tasks.
Create an instance that uses AOF persistence
Console
In the Data persistence strategy section, select the Append Only File (AOF) option when Creating an instance.
Select a sync setting from the AOF Fsync mode menu.
gcloud
To create an instance that uses AOF persistence, run the create
command:
gcloud beta memorystore instances create instance \ --location=region-id \ --psc-auto-connections=network=projects/project-id/global/networks/network-id,projectId=project-id \ --replica-count=replica-count \ --node-type=node-type \ --shard-count=shard-count \ --persistence-config-mode=aof \ --aof-config-append-fsync=fsync-frequency
Replace the following:
instance is the ID of the Memorystore for Valkey instance you're creating. Your instance ID must be 1 to 63 characters and use only lowercase letters, numbers, or hyphens. It must start with a lowercase letter and end with a lowercase letter or number.
region-id is the region where you want the instance placed.
project-id is the ID of the project where you want to create your instance.
network-id is the ID of the network you want to use to create your instance.
replica-count is your chosen number of replicas (per shard). Accepted values are
0
,1
, and2
.node-type is your chosen node type. Accepted values are:
shared-core-nano
standard-small
highmem-medium
highmem-xlarge
For more details on node types and instance configurations, see Instance and node specification.
shard-count determines the number of shards in your instance. Shard count determines the total memory capacity for storing instance data. For more information about instance specification, see Instance and node specification.
fsync-frequency is your sync setting. Accepted values are
always
,everysec
, andno
.everysec
is the default for this parameter.
Enable AOF persistence for an existing instance
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select the Append Only File (AOF) option.
Select a sync setting from the AOF Fsync mode menu.
Click the Update Instance button.
Replace the following:
- fsync-frequency is your sync setting. Accepted values are
always
,everysec
, andno
.everysec
is the default for this parameter.
Adjust the AOF sync setting for your instance
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select your chosen sync setting from the AOF fsync mode menu.
Click the Update Instance button.
gcloud
To adjust the sync setting for an instance that uses AOF persistence, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --aof-config-append-fsync=fsync-frequency
Replace the following:
- fsync-frequency is your sync setting. Accepted values are
always
,everysec
, andno
.everysec
is the default for this parameter.
Disable AOF persistence
Console
Go to the Memorystore for Valkey page in the Google Cloud console.
Click your instance ID.
In the Configurations section, click the pencil icon next to Persistence.
Select the No persistence option.
Click the Update Instance button.
gcloud
To disable AOF persistence, run the update
command:
gcloud beta memorystore instances update instance \ --location=region-id \ --persistence-config-mode=disabled
Monitor AOF persistence
You can use Cloud Monitoring to view metrics for AOF persistence.
For a list of available metrics for AOF persistence, see persistence metrics.