Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

facilitate profile backup #1955

Closed
CouldBeThis opened this issue Mar 3, 2024 · 2 comments
Closed

facilitate profile backup #1955

CouldBeThis opened this issue Mar 3, 2024 · 2 comments
Labels
status:stale This item will be closed soon due to inactivity

Comments

@CouldBeThis
Copy link

The problem

  • It is difficult to discover the export profile feature
  • It is easy to avoid learning that you need to do this
  • Once you know why and how it's done, it is cumbersome especially for multiple profiles

Requested Solution

  • One-click to export entire configuration for all profiles

    • just this would be a big improvement; seems like it could be pretty straightforward? easy for me to say I'm no developer :D
  • Optionally, automatically create a backup to specified location at specified intervals (might only be a good idea if the backups themselves could be encrypted? unsure)

  • Vorta should remember and display information about when the last backup was made either for the application as a whole or on a per-profile basis

    • optionally, vorta should prompt the user to make a new backup when the most recently created one is missing information

The application should educate the user about what is required to restore backups and facilitate the required steps. Otherwise there is no benefit to the backups, they are only false reassurance.

Maybe even create a dedicated tab in the interface called "how to restore" or "assess restorability" or "restore kit" with a checklist, tools, info on when/where backups have been created, documentation etc.

Alternatives

  • individually and manually create per-profile backups --- possible but easy to miss or to do wrong

Additional context

Based on my new understanding of how recovery from backups actually works, in this discussion #1929 password when initializing new repo.

Overlapping but not identical: #1918 #1928

Copy link

github-actions bot commented Jun 2, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the status:stale This item will be closed soon due to inactivity label Jun 2, 2024
Copy link

github-actions bot commented Jun 9, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:stale This item will be closed soon due to inactivity
Projects
None yet
Development

No branches or pull requests

1 participant