CLI reference

norcube backup restore-tests settings update

Change a data source's automated restore tests

Not verified yet

Changes only what you pass; the rest stays as it is.

How often automated tests run (one of):

--every N        one in every N successful backups
--schedule CRON  on a cron schedule (in --timezone)
--sample SHARE   a random share of backups (0.25 or 25%)

Any of them turns the tests on; --disable turns them off and keeps the settings, --enable turns them back on.

Where a test restores (--target): managed_ephemeral, a database Norcube spins up for the test, or customer_scratch, a server of yours given with --scratch-uri-file (a file, - for standard input; it must not be the server being backed up). --level sets how deep the validation goes: l1 (the restore succeeds), l2 (the data is there), l3 (also runs --validation-query).

Usage

norcube backup restore-tests settings update [flags]

Examples

norcube backup restore-tests settings update -d 9f8e7d6c-… --every 7
norcube backup restore-tests settings update -d 9f8e7d6c-… --schedule "0 4 * * 0" --timezone Europe/Prague --level l2
norcube backup restore-tests settings update -d 9f8e7d6c-… --target customer_scratch --scratch-uri-file scratch.uri
norcube backup restore-tests settings update -d 9f8e7d6c-… --disable

Flags

FlagDefaultDescription
-d, --datasourceData source (id)
--disableTurn automated restore tests off (the settings are kept)
--enableTurn automated restore tests on
--everyTest one in every N successful backups
--levelValidation depth: l1, l2, l3
--sampleTest this share of backups (0.25 or 25%)
--scheduleTest on this cron schedule
--scratch-uri-fileRead the scratch server's connection string from this file (- for standard input)
--targetWhere tests restore: managed_ephemeral, customer_scratch
--timezoneTime zone of --schedule (IANA name)
--validation-queryQuery an l3 validation runs against the restored data

Every command also takes the global flags: --profile, --org, -o, --query, --debug and more.

See also

On this page