Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Other
Backup
Implement reliable backup strategies avoiding data loss, failed restores, and security gaps.
skill openclawclawhub Free
Implement reliable backup strategies avoiding data loss, failed restores, and security gaps.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- ivangdavila
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
The Only Rule That Matters
Untested backups are not backups โ schedule regular restore tests, not just backup jobs Test restores to different hardware/location โ validates both backup and restore procedure Time the restore โ know how long recovery actually takes before disaster strikes
3-2-1 Rule Violations
Same disk as source data = not a backup โ disk failure loses both Same server as source = not a backup โ ransomware/fire/theft takes both Same cloud account = risky โ account compromise or provider issue loses both Cloud sync (Dropbox, Drive) is not backup โ syncs deletions and corruption too
Ransomware Protection
Backups accessible from production get encrypted too โ air gap or immutable storage required Append-only/immutable storage prevents deletion โ S3 Object Lock, Backblaze B2 with retention Offline rotation (USB drives, tapes) for critical data โ can't encrypt what's not connected Test restoring from immutable backup โ verify ransomware can't corrupt the restore process
Database Backup Traps
File copy of running database = corrupted backup โ use pg_dump, mysqldump, mongodump Point-in-time recovery needs WAL/binlog archiving โ dump alone loses recent transactions Large databases: pg_dump locks tables โ use pg_basebackup or logical replication for zero downtime Test restore to different server โ verifies backup is self-contained
Incremental Backup Pitfalls
Incrementals depend on chain โ one corrupted backup breaks all following Long chains slow restores โ schedule periodic full backups Deduplication saves space but adds complexity โ single repo corruption affects all backups Verify backup integrity regularly โ bit rot happens, checksums catch it
Retention Mistakes
No retention policy = storage fills up โ define and automate cleanup Too aggressive retention = can't recover old corruption โ keep monthlies for a year minimum Legal/compliance requirements may mandate retention โ check before setting policy Grandfather-father-son pattern: daily/weekly/monthly tiers
Filesystem Traps
Permissions and ownership often lost โ verify restore preserves them, or document expected state Symlinks may not backup correctly โ some tools follow, some copy link, test behavior Sparse files may inflate โ 1GB sparse file becomes 1GB actual in backup Extended attributes and ACLs โ not all tools preserve them
Cloud and Remote
Encrypt before upload โ cloud provider breach shouldn't expose your data Bandwidth costs add up โ initial seed via physical drive for large datasets Region matters for disaster recovery โ same region as production doesn't survive regional outage Egress fees can be brutal โ know restore costs before emergency
Tool-Specific
rsync --delete on wrong direction destroys source โ always double-check source/destination restic/borg need repository password โ lose it = lose all backups, no recovery Tarball without compression: faster, but larger โ choose based on CPU vs storage tradeoff Snapshots (LVM, ZFS, cloud) are not backups โ same storage system, same failure domain
Documentation
Document restore procedure โ you won't remember under pressure Store procedure outside the backup โ printed, different system, password manager Include credentials, paths, expected time โ everything needed to restore at 3am
Category context
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
1 Docs
- SKILL.md