backup_pitr_test.go

/*
Copyright 2022 The Vitess Authors.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

package mysqlctld

import (
	"testing"

	backup "vitess.io/vitess/go/test/endtoend/backup/vtctlbackup"
)

// TestIncrementalBackupAndRestoreToPos - tests incremental backups and restores.
// The general outline of the test:
//   - Generate some schema with data
//   - Take a full backup
//   - Proceed to take a series of inremental backups. In between, inject data (insert rows), and keep record
//     of which data (number of rows) is present in each backup, and at which position.
//   - Expect backups success/failure per scenario
//   - Next up, we start testing restores. Randomly pick recorded positions and restore to those points in time.
//   - In each restore, excpect to find the data (number of rows) recorded for said position
//   - Some restores should fail because the position exceeds the last binlog
//   - Do so for all recorded positions.
//   - Then, a 2nd round where some backups are purged -- this tests to see that we're still able to find a restore path
//     (of course we only delete backups that still leave us with valid restore paths).
//   - Last, create a new tablet with --restore_from_backup --restore-to-pos and see that it bootstraps with restored data
//     and that it ends up in DRAINED type
func TestIncrementalBackupAndRestoreToPos(t *testing.T) {
	tcase := &backup.PITRTestCase{
		Name:           "BuiltinBackup",
		SetupType:      backup.BuiltinBackup,
		ComprssDetails: nil,
	}
	backup.ExecTestIncrementalBackupAndRestoreToPos(t, tcase)
}

// TestIncrementalBackupAndRestoreToTimestamp - tests incremental backups and restores.
// The general outline of the test:
//   - Generate some schema with data
//   - Take a full backup
//   - Proceed to take a series of inremental backups. In between, inject data (insert rows), and keep record
//     of which data (number of rows) is present in each backup, and at which timestamp.
//   - Expect backups success/failure per scenario
//   - Next up, we start testing restores. Randomly pick recorded timestamps and restore to those points in time.
//   - In each restore, excpect to find the data (number of rows) recorded for said timestamp
//   - Some restores should fail because the timestamp exceeds the last binlog
//   - Do so for all recorded tiemstamps.
//   - Then, a 2nd round where some backups are purged -- this tests to see that we're still able to find a restore path
//     (of course we only delete backups that still leave us with valid restore paths).
//   - Last, create a new tablet with --restore_from_backup --restore-to-timestamp and see that it bootstraps with restored data
//     and that it ends up in DRAINED type
func TestIncrementalBackupAndRestoreToTimestamp(t *testing.T) {
	tcase := &backup.PITRTestCase{
		Name:           "BuiltinBackup",
		SetupType:      backup.BuiltinBackup,
		ComprssDetails: nil,
	}
	backup.ExecTestIncrementalBackupAndRestoreToTimestamp(t, tcase)
}

// TestIncrementalBackupOnTwoTablets runs a series of interleaved backups on two different replicas: full and incremental.
// Specifically, it's designed to test how incremental backups are taken by interleaved replicas, so that they successfully build on
// one another.
func TestIncrementalBackupOnTwoTablets(t *testing.T) {
	tcase := &backup.PITRTestCase{
		Name:           "BuiltinBackup",
		SetupType:      backup.BuiltinBackup,
		ComprssDetails: nil,
	}
	backup.ExecTestIncrementalBackupOnTwoTablets(t, tcase)
}