klein-projects/infra
2
0
Code Issues 7 Packages Projects 1 Wiki

Create and implement data backup procedures #5

New Issue
Open
opened 2025-05-07 20:43:03 +02:00 by Rudi · 1 comment
Rudi commented 2025-05-07 20:43:03 +02:00
Owner
Copy Link
  1. Data to backup is identified.
  2. Define importance levels and frequency.
  3. Select backup tools (can be more than one depending on the use case).
  4. Implement tooling and procedures.
  5. Test backup environment including restore.
  6. Enable production status.
1. Data to backup is identified. 2. Define importance levels and frequency. 3. Select backup tools (can be more than one depending on the use case). 4. Implement tooling and procedures. 5. Test backup environment including restore. 6. Enable production status.
Rudi commented 2025-05-07 20:48:21 +02:00
Author
Owner
Copy Link

Current and potential tools.

  • SyncBack
    Pros: reliable
    Cons: server on Windows only. Agents on Linux.

  • TrueImage
    Pros: professional grade
    Cons: paid

  • BackRest
    Pros: runs on Linux server
    supports a wide variety of formats
    Cons: not found yet.

  • Rsync
    Pros: wide support and maturity
    Cons: user unfriendly

Current and potential tools. - SyncBack Pros: reliable Cons: server on Windows only. Agents on Linux. - TrueImage Pros: professional grade Cons: paid - BackRest Pros: runs on Linux server supports a wide variety of formats Cons: not found yet. - Rsync Pros: wide support and maturity Cons: user unfriendly
Rudi self-assigned this 2025-05-07 20:49:01 +02:00
DariusKlein was assigned by Rudi 2025-05-07 20:49:02 +02:00
Rudi added the due date 2025-05-31 2025-05-07 20:49:51 +02:00
Rudi added the
Priority
High
Kind/Enhancement
Kind/Security
 labels 2025-05-07 20:51:19 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Kind/Enhancement
Kind/Security
Priority
High
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
DariusKlein Rudi
No Assignees Rudi DariusKlein
1 Participants
Notifications
Due Date
2025-05-31
Dependencies

No dependencies set.

Reference: klein-projects/infra#5
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?