WEBVTT 00:00:00.030 --> 00:00:03.030 position:50% align:center size:88% Let’s review the recorded point-in-time restore. 00:00:03.080 --> 00:00:06.430 position:50% align:center size:88% We’ll separate measured recovery results from untested steps. 00:00:06.910 --> 00:00:09.835 position:50% align:center size:88% Start with the two database roles in this record. 00:00:09.885 --> 00:00:14.585 position:50% align:center size:88% The operator restored a separate copy while the platform kept using its source. 00:00:14.660 --> 00:00:18.860 position:50% align:center size:88% The source was Multi-AZ; the drill copy was single-AZ. 00:00:18.960 --> 00:00:23.380 position:50% align:center size:88% This was a copy-verification exercise, not a production cut-over. 00:00:23.455 --> 00:00:26.921 position:50% align:center size:88% The checks used the application image named in this record. 00:00:28.800 --> 00:00:32.425 position:50% align:center size:88% Read the chosen restore point and the time it was observed. 00:00:32.500 --> 00:00:35.175 position:50% align:center size:88% The gap was eight minutes and fourteen seconds. 00:00:35.250 --> 00:00:38.032 position:50% align:center size:88% That is inside the five to ten minute planning range. 00:00:38.107 --> 00:00:39.882 position:50% align:center size:88% Later samples improved. 00:00:39.932 --> 00:00:42.857 position:50% align:center size:88% They do not replace the measurement used for this restore. 00:00:42.932 --> 00:00:45.223 position:50% align:center size:88% Keep the planning range beside the result. 00:00:47.760 --> 00:00:51.010 position:50% align:center size:88% Follow the restore start through the two checkpoints. 00:00:51.085 --> 00:00:55.260 position:50% align:center size:88% The copy became available after nineteen minutes and twenty-four seconds. 00:00:55.335 --> 00:00:59.910 position:50% align:center size:88% Its first automated backup accounted for nine minutes and fifteen seconds. 00:00:59.985 --> 00:01:03.710 position:50% align:center size:88% The verified copy took twenty-one minutes and fifty-six seconds. 00:01:03.785 --> 00:01:07.749 position:50% align:center size:88% An available database and a verified copy are different checkpoints. 00:01:09.240 --> 00:01:12.865 position:50% align:center size:88% Compare the five table counts at the chosen restore point. 00:01:12.940 --> 00:01:16.890 position:50% align:center size:88% Every recorded source count matches its restored-copy count. 00:01:16.965 --> 00:01:20.990 position:50% align:center size:88% The zero change-record count is also part of the comparison. 00:01:21.090 --> 00:01:23.715 position:50% align:center size:88% These are the rows selected for this drill. 00:01:23.790 --> 00:01:28.190 position:50% align:center size:88% Matching counts do not establish that a production cut-over has succeeded. 00:01:28.315 --> 00:01:30.531 position:50% align:center size:88% Scroll back to compare the two columns. 00:01:32.600 --> 00:01:35.650 position:50% align:center size:88% Both audit chains replayed without a broken link. 00:01:35.700 --> 00:01:39.475 position:50% align:center size:88% The copy holds three hundred and nineteen platform audit rows. 00:01:39.550 --> 00:01:42.325 position:50% align:center size:88% Its workspace chain has twenty-four rows. 00:01:42.375 --> 00:01:45.275 position:50% align:center size:88% The source sealed another batch after the restore point. 00:01:45.350 --> 00:01:47.550 position:50% align:center size:88% That explains the later head difference. 00:01:47.625 --> 00:01:50.300 position:50% align:center size:88% The check used the copy’s own login. 00:01:50.400 --> 00:01:53.784 position:50% align:center size:88% Stored-credential decryption was not documented by this drill. 00:01:55.840 --> 00:01:59.315 position:50% align:center size:88% The operator deleted the copy after preserving the result. 00:01:59.390 --> 00:02:03.165 position:50% align:center size:88% Its automated backups and managed secret were also removed. 00:02:03.215 --> 00:02:05.165 position:50% align:center size:88% The source stayed untouched. 00:02:05.240 --> 00:02:10.615 position:50% align:center size:88% This drill did not test cut-over, pre-upgrade snapshots, or the data volume. 00:02:10.715 --> 00:02:15.440 position:50% align:center size:88% Runner crash recovery is a separate exercise and is not demonstrated here. 00:02:15.515 --> 00:02:18.453 position:50% align:center size:88% Keep those limits with the measured recovery results.