Pgbackrest kasutamine - Redigeerimiste ajalugu

Imre: /* Varundamine */

2026-05-18T06:52:31Z

Varundamine

←Vanem redaktsioon		Redaktsioon: 18. mai 2026, kell 06:52
128. rida:		128. rida:
	Varundamiseks sobib repo arvutis öelda nt		Varundamiseks sobib repo arvutis öelda nt

	$ pgbackrest --stanza=db-~~tf-vm-84~~ stanza-create		$ pgbackrest --stanza=db-primary stanza-create
	$ pgbackrest --stanza=db-~~tf-vm-84~~ check		$ pgbackrest --stanza=db-primary check
	$ pgbackrest --stanza=db-primary backup		$ pgbackrest --stanza=db-primary backup
	$ pgbackrest --stanza=db-primary --type=full backup		$ pgbackrest --stanza=db-primary --type=full backup

Imre: /* Süsteemide ettevalmistamine */

2026-05-18T06:51:33Z

Süsteemide ettevalmistamine

←Vanem redaktsioon		Redaktsioon: 18. mai 2026, kell 06:51
52. rida:		52. rida:
	root@tf-vm-84:~# grep archive_ /etc/postgresql/10/main/postgresql.conf		root@tf-vm-84:~# grep archive_ /etc/postgresql/10/main/postgresql.conf
	archive_mode = on		archive_mode = on
	archive_command = 'pgbackrest --stanza=db-~~tf-vm-84~~ archive-push %p'		archive_command = 'pgbackrest --stanza=db-primary archive-push %p'
	</pre>		</pre>

Imre: /* Varundamine */

2026-05-18T06:50:53Z

Varundamine

←Vanem redaktsioon		Redaktsioon: 18. mai 2026, kell 06:50
129. rida:		129. rida:

	$ pgbackrest --stanza=db-tf-vm-84 stanza-create		$ pgbackrest --stanza=db-tf-vm-84 stanza-create
			$ pgbackrest --stanza=db-tf-vm-84 check
	$ pgbackrest --stanza=db-primary backup		$ pgbackrest --stanza=db-primary backup
	$ pgbackrest --stanza=db-primary --type=full backup		$ pgbackrest --stanza=db-primary --type=full backup

Imre: /* Vanade varunduste eemaldamine */

2025-11-11T01:52:11Z

Vanade varunduste eemaldamine

←Vanem redaktsioon		Redaktsioon: 11. november 2025, kell 01:52
155. rida:		155. rida:
	* kustutada mida tabataks		* kustutada mida tabataks

	$ pgbackrest --config /etc/pgbackrest.conf --stanza=pgcluster_13_main_toodang --dry-run expire		<pre>
	$ pgbackrest --config /etc/pgbackrest.conf --stanza=pgcluster_13_main_toodang expire		$ pgbackrest --config /etc/pgbackrest.conf --stanza=pgcluster_13_main_toodang --dry-run expire
			$ pgbackrest --config /etc/pgbackrest.conf --stanza=pgcluster_13_main_toodang expire
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: expire full backup 20230516-210533F
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: expire full backup 20230823-035915F
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: expire full backup 20231018-172449F
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: remove expired backup 20231018-172449F
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: remove expired backup 20230823-035915F
			2025-11-11 03:51:29.783 P00 INFO: [DRY-RUN] repo1: remove expired backup 20230516-210533F
			2025-11-11 03:51:29.806 P00 INFO: [DRY-RUN] repo1: 15-1 remove archive, start = 0000000100000220, stop = 00000001000002210000004C
			2025-11-11 03:51:29.820 P00 INFO: [DRY-RUN] expire command end: completed successfully (40ms)
			</pre>

	* seadistada tagasi retention sobiv suurus		* seadistada tagasi retention sobiv suurus

Imre: /* Timeline */

2025-10-30T10:30:27Z

Timeline

@@ 257. rida: / 257. rida: @@
 recovery_target_time = '2025-10-30 03:15:38+02:00'
 recovery_target_timeline = '7'
 </pre>

Imre: /* Timeline */

2025-10-30T10:26:52Z

Timeline

←Vanem redaktsioon		Redaktsioon: 30. oktoober 2025, kell 10:26
221. rida:		221. rida:

	* kui andmebaasist hoitakse erinevatele timeline'idele vastavaid eksemplare, siis vist teoreetiliselt saab neid varundada vastu ühte ja sama pgbackrest varundust (kuna erinevate timeline'ide wal failide kohta hoitakse iseseisvalt järge)		* kui andmebaasist hoitakse erinevatele timeline'idele vastavaid eksemplare, siis vist teoreetiliselt saab neid varundada vastu ühte ja sama pgbackrest varundust (kuna erinevate timeline'ide wal failide kohta hoitakse iseseisvalt järge)

			Taastel võib tekkida takistusi timeline soovimatu ületamise tõttu

			<pre>
			Oct 30 11:08:48 pg-01.moraal.ee systemd[1]: Starting postgresql@16-main.service - PostgreSQL Cluster 16-main...
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [1-1] 2025-10-30 11:08:48.487 EET [477590] LOG: ending log output to stderr
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [1-2] 2025-10-30 11:08:48.487 EET [477590] HINT: Future log output will go to log destination "syslog".
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [2-1] 2025-10-30 11:08:48.489 EET [477590] LOG: starting PostgreSQL 16.10 (Ubuntu 16.10-1.pgdg24.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, 64-bit
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [3-1] 2025-10-30 11:08:48.492 EET [477590] LOG: listening on IPv4 address "0.0.0.0", port 5432
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [4-1] 2025-10-30 11:08:48.494 EET [477590] LOG: could not create IPv6 socket for address "::": Address family not supported by protocol
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477590]: [5-1] 2025-10-30 11:08:48.497 EET [477590] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [6-1] 2025-10-30 11:08:48.508 EET [477595] LOG: database system was interrupted; last known up at 2025-10-30 03:14:35 EET
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [7-1] 2025-10-30 11:08:48.569 EET [477595] LOG: restored log file "00000008.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [8-1] 2025-10-30 11:08:48.611 EET [477595] LOG: restored log file "00000009.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [9-1] 2025-10-30 11:08:48.651 EET [477595] LOG: restored log file "0000000A.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [10-1] 2025-10-30 11:08:48.692 EET [477595] LOG: restored log file "0000000B.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [11-1] 2025-10-30 11:08:48.733 EET [477595] LOG: restored log file "0000000C.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [12-1] 2025-10-30 11:08:48.774 EET [477595] LOG: restored log file "0000000D.history" from archive
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [13-1] 2025-10-30 11:08:48.812 EET [477595] LOG: starting point-in-time recovery to 2025-10-30 03:14:42+02
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [14-1] 2025-10-30 11:08:48.813 EET [477595] LOG: starting backup recovery with redo LSN 0/6D000028, checkpoint LSN 0/6D005820, on timeline ID 7
			Oct 30 11:08:48 pg-01.moraal.ee postgres[477595]: [15-1] 2025-10-30 11:08:48.853 EET [477595] LOG: restored log file "0000000D.history" from archive
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477595]: [16-1] 2025-10-30 11:08:49.149 EET [477595] LOG: restored log file "00000007000000000000006D" from archive
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477595]: [17-1] 2025-10-30 11:08:49.176 EET [477595] FATAL: requested timeline 13 is not a child of this server's history
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477595]: [17-2] 2025-10-30 11:08:49.176 EET [477595] DETAIL: Latest checkpoint is at 0/6D005820 on timeline 7, but in the history of the requested timeline, the server forked off from that timeline at 0/6E00DD48.
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477590]: [6-1] 2025-10-30 11:08:49.178 EET [477590] LOG: startup process (PID 477595) exited with exit code 1
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477590]: [7-1] 2025-10-30 11:08:49.178 EET [477590] LOG: aborting startup due to startup process failure
			Oct 30 11:08:49 pg-01.moraal.ee postgres[477590]: [8-1] 2025-10-30 11:08:49.179 EET [477590] LOG: database system is shut down
			</pre>

			Lahenduseks on öelda süsteemile, et püsida taastel timeline 7 juures

			<pre>
			# cat /var/lib/postgresql/16/main/postgresql.auto.conf \| tail -n 4
			restore_command = 'pgbackrest --stanza=pg_16 archive-get %f "%p"'
			recovery_target_time = '2025-10-30 03:15:38+02:00'
			recovery_target_timeline = '7'
			</pre>

	===Minio===		===Minio===

Imre: /* Minio */

2025-10-30T01:16:43Z

Minio

←Vanem redaktsioon		Redaktsioon: 30. oktoober 2025, kell 01:16
250. rida:		250. rida:

	<pre>		<pre>
	mc alias set pgrepotest https://s3-by-minio.moraal.ee:9000 key-division-project-test keysecret-parool		# mc alias set pgrepotest https://s3-by-minio.moraal.ee:9000 key-division-project-test keysecret-parool

	# mc ls pgrepotest/bucket-division-project-test/path-project-test-pgbackrest-1		# mc ls pgrepotest/bucket-division-project-test/path-project-test-pgbackrest-1

Imre: /* Timeline */

2025-10-30T01:16:19Z

Timeline

←Vanem redaktsioon		Redaktsioon: 30. oktoober 2025, kell 01:16
207. rida:		207. rida:
	00000003000000000000006B		00000003000000000000006B
	(1 row)		(1 row)
			</pre>

			Milliseid wal logisid taastes kasutati

			<pre>
			# grep "pg_wal/RECOVERYXLOG" /var/log/postgresql/postgresql-16-main.log \| sed -r 's/exec-id.*//' \| grep 03:1
			2025-10-30 03:13:23.407 P00 INFO: archive-get command begin 2.56.0: [00000006000000000000006A, pg_wal/RECOVERYXLOG] --
			2025-10-30 03:13:23.545 P00 INFO: archive-get command begin 2.56.0: [00000006000000000000006B, pg_wal/RECOVERYXLOG] --
			#
	</pre>		</pre>

Imre: /* Timeline */

2025-10-29T23:33:52Z

Timeline

←Vanem redaktsioon		Redaktsioon: 29. oktoober 2025, kell 23:33
208. rida:		208. rida:
	(1 row)		(1 row)
	</pre>		</pre>

			Märkused

			* kui andmebaasist hoitakse erinevatele timeline'idele vastavaid eksemplare, siis vist teoreetiliselt saab neid varundada vastu ühte ja sama pgbackrest varundust (kuna erinevate timeline'ide wal failide kohta hoitakse iseseisvalt järge)

	===Minio===		===Minio===

Imre: /* Timeline */

2025-10-29T23:31:30Z

Timeline

←Vanem redaktsioon		Redaktsioon: 29. oktoober 2025, kell 23:31
179. rida:		179. rida:

	* üks postgresql andmebaas st teenus ning temaga tegelev pgbackrest varundus viibivad ühel ajahetkel nö ühes ja samas kohas, st nad toimetavad kooskõlaliselt		* üks postgresql andmebaas st teenus ning temaga tegelev pgbackrest varundus viibivad ühel ajahetkel nö ühes ja samas kohas, st nad toimetavad kooskõlaliselt
	* kui mingeid nö segajaid ei ole (nt äsja ei ole taastatud andmebaasi varundusest), siis postgresqli baasi ja tema ~~pgbacrest~~ varundus nö kulgevad ajas edasi		* kui mingeid nö segajaid ei ole (nt äsja ei ole taastatud andmebaasi varundusest), siis postgresqli baasi ja tema pgbackrest varundus nö kulgevad ühtlaselt ajas edasi
	* postgresqli baasil ja pgbackrest varundusel on võimekus hallata erinevaid kombinatsioone töötavast baasist ja tema varundusest		* postgresqli baasil ja pgbackrest varundusel on võimekus hallata erinevaid kombinatsioone töötavast baasist ja tema varundusest
	* wal logi kuulub alati mingi ja ainult ühe timeline juurde		* wal logi kuulub alati mingi ja ainult ühe timeline juurde