Getting Started with Common Practices

After purchasing and connecting to a GeminiDB Redis DB instance, you can view common practices to better use it.

**Table 1** Common practices
Practice		Description
Data migration	From On-Premises Redis to GeminiDB Redis API	Describes how to use Redis-Shake to migrate data from an on-premises Redis instance (source) to a GeminiDB Redis instance (destination). Full and incremental migrations are both supported. The source can be a single-node, primary/standby, or cluster instance, or an RDB file.
	From Kvrocks to GeminiDB Redis API	Describes how to use the open-source tool kvrocks2redis to migrate data from a Kvrocks instance to a GeminiDB Redis instance. GeminiDB Redis source code is refactored so that GeminiDB Redis supports the namespace function of Kvrocks.
	From Pika to GeminiDB Redis API	Describes how to migrate data from a Pika instance to a GeminiDB Redis instance. pika-port acts as a slave node of the Pika instance. Data is replicated from the slave node to the master node of the instance to complete data migration. The master node compares its own binlogs with those on pika-port to determine whether to perform full migration or incremental migration. If full migration is required, the master node sends a full snapshot to pika-port, which parses the snapshot and sends the obtained data to the GeminiDB Redis instance. After the full migration is complete, incremental migration starts. pika-port parses incremental data and sends the obtained data to GeminiDB Redis by running Redis commands.
	From SSDB to GeminiDB Redis API	Describes how to migrate data from an SSDB instance to a GeminiDB Redis instance. ssdb-port acts as the slave node of the SSDB instance and migrates data through master-slave replication. Then, ssdb-port parses the obtained data and converts its format to a format that GeminiDB Redis API supports, and then sends the data to the GeminiDB Redis instance specified in the configuration file. After the full synchronization is complete, the new data in the SSDB instance is also synchronized to the GeminiDB Redis instance.
	From LevelDB to GeminiDB Redis API	Describes how to migrate data from a LevelDB instance to a GeminiDB Redis instance. The self-developed migration tool leveldb-port is used to deploy LevelDB on the same server as your services. With the configuration file prepared, you can start the migration task to automatically complete full and incremental migration.
	From Kvrocks to GeminiDB Redis API	Describes how to migrate data from a RocksDB instance to a GeminiDB Redis instance. The self-developed migration tool rocksdb-port is used to deploy RocksDB on the same server as your services. With the configuration file prepared, you can start the migration task to automatically complete full and incremental migration.
Data backup	Managing Automated Backups	Describes how to enable automated backup so that GeminiDB Redis API can automatically create backups for a DB instance during a backup window and saves the backups based on the configured retention period.
Data backup	Managing Manual Backups	Describes how to manually create backups for a DB instance. These backups can be used to restore data for improved reliability.
Data restoration	Restoring Data to a New Instance	Describes how to restore an existing automated or manual backup to a new instance. The restored data is the same as the backup data.
Log management	Slow Query Logs	Describes how to view slow query logs of a GeminiDB Redis database. The unit of the execution time is ms. You can identify the SQL statements that take a long time to execute and tune them based on slow query logs.