Files

T

Antigravity Agent c24165b8bc refactor(topics): 멀티 에이전트용 지식 재편 — _Common(공통 기본기) + Domain_* 구조

에이전트 8종(대화형/프로그래머 C·S/디자이너/설계자/기획자/QA/PD/PM)에게
[공통 기본 능력 + 롤별 Specialty] 2층으로 지식을 주입하기 위한 재분류.
문서 내용·포맷은 무수정, 폴더 이동만 (6,372개 문서 수 보존 확인).

- Topic_Programming → Domain_Programming (내부 구조 보존)
- Topic_Graphic → Domain_Design
- Topic_Business → Domain_Product
- Topic_General → Domain_General
- _Common 신설: Math(구 Topic_Math_Specialty), Reasoning(구 General/From_Thinking & Reasoning),
  Reasoning_Creativity(구 General/From_창의성), Communication(Poetic_Blog_Writing + From_writing)
- 타 도메인의 From_* 폴더는 유지 (출처 표기일 뿐, 이미 도메인에 맞게 분류된 문서)
- 빈 폴더 정리 (memory/procedures)
- 에이전트→폴더 매핑은 workspace의 .astra/agent-knowledge-map.json (9개 에이전트)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-11 11:05:56 +09:00

4.7 KiB

Raw Blame History

id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack

title

Backups

매 한 줄

"매 backup 은 restore 가 검증된 backup 만이다.". Backups 는 매 3-2-1 rule (3 copies, 2 media, 1 offsite) + RTO/RPO target + 정기 restore drill 의 trio. 2026 의 standard: incremental dedup (restic/borg) + immutable object lock (S3 Object Lock, Azure Immutable Blob) + ransomware-resistant air gap.

매 핵심

매 3-2-1-1-0 Rule (modern)

3 copies of data.
2 different media types.
1 offsite copy.
1 immutable / air-gapped (anti-ransomware, 매 2020+ 추가).
0 errors after restore verification.

매 RTO vs RPO

RTO (Recovery Time Objective): 매 outage 후 service 복구까지 허용 시간.
RPO (Recovery Point Objective): 매 허용 가능한 data loss window.
매 RTO=1h / RPO=15min 이면 hot standby 필요.

매 Backup Type

Full: 매 전체 — slow, large, simple restore.
Incremental: 매 since last backup — fast, smaller, restore chain.
Differential: 매 since last full — middle ground.
Snapshot (CoW): 매 ZFS/btrfs/LVM/EBS — instant, space-efficient.
Continuous (CDC): 매 every transaction — Postgres WAL, MySQL binlog.

매 응용

DB backup (pg_basebackup + WAL archive).
File backup (restic, borg, Time Machine).
VM/disk snapshot (EBS, GCP PD, ZFS).
Object store replication (S3 CRR).
App-level (export-import, logical dump).

💻 패턴

restic encrypted incremental backup

# 매 init repo (one-time)
restic init --repo s3:s3.amazonaws.com/my-backup-bucket
# 매 daily backup
restic -r s3:s3.amazonaws.com/my-backup-bucket backup /var/data \
  --exclude '*.tmp' --tag daily --host $(hostname)
# 매 retention: keep 7d, 4w, 12m
restic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 12 --prune
# 매 verify
restic check --read-data-subset=10%

Postgres PITR setup

# postgresql.conf
wal_level = replica
archive_mode = on
archive_command = 'aws s3 cp %p s3://pg-wal/%f'
# 매 base backup
pg_basebackup -D /backup/base -Ft -z -P -U replicator
# 매 restore: recovery.conf or postgresql.auto.conf with restore_command + recovery_target_time

S3 Object Lock (immutable, ransomware-proof)

aws s3api put-object-lock-configuration \
  --bucket my-backup-bucket \
  --object-lock-configuration '{"ObjectLockEnabled":"Enabled","Rule":{"DefaultRetention":{"Mode":"COMPLIANCE","Days":30}}}'

Restore drill automation

#!/usr/bin/env bash
# 매 nightly drill — restore latest to scratch, verify checksums
set -euo pipefail
SCRATCH=$(mktemp -d)
restic -r s3:.../backup restore latest --target "$SCRATCH"
sha256sum -c expected_checksums.sha256 --strict
echo "drill ok: $(date -Iseconds)" | tee -a /var/log/restore-drill.log
rm -rf "$SCRATCH"

ZFS snapshot + send

# 매 instant CoW snapshot
zfs snapshot tank/data@$(date +%Y%m%d-%H%M)
# 매 incremental send to remote
zfs send -i tank/data@yesterday tank/data@today | ssh backup-host zfs recv tank/data

매 결정 기준

상황	Approach
Files, small-mid	restic / borg
Postgres prod	pg_basebackup + WAL archive (PITR)
MySQL prod	xtrabackup + binlog
VM	snapshot + offsite replica
Multi-cloud	S3-compatible + CRR
Compliance (WORM)	S3 Object Lock COMPLIANCE mode

기본값: 매 restic to S3 with Object Lock + nightly restore drill.

🔗 Graph

부모: SRE
변형: CI_CD_Pipeline
응용: 카오스 몽키(Chaos Monkey)
Adjacent: Secret_Management · Logging_and_Error_Handling

🤖 LLM 활용

언제: backup script generation, restore runbook drafting, log anomaly summarization. 언제 X: 매 actual restore execution — manual gate 필요.

❌ 안티패턴

No restore test: 매 가장 흔한 실패 — backup 은 되는데 restore 가 안 됨.
Single copy: 매 disk fail 한 방에 잃음.
No encryption: 매 backup 이 attack vector — at-rest encrypt 필수.
No immutability: 매 ransomware 가 backup 까지 암호화.
Forever retention: 매 비용 폭발 + GDPR 위반 가능.

🧪 검증 / 중복

Verified: restic docs; AWS Backup whitepaper; Veeam 3-2-1-1-0 guide; PostgreSQL PITR docs.
신뢰도 A.

🕓 Changelog

날짜	변경
2026-05-08	Phase 1
2026-05-10	Manual cleanup — 3-2-1-1-0 + restic/PG PITR/S3 Object Lock

4.7 KiB Raw Blame History