-
Notifications
You must be signed in to change notification settings - Fork 27
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
feat: support full backup #166
Open
ChanYiLin
wants to merge
1
commit into
longhorn:master
Choose a base branch
from
ChanYiLin:LH7070_support_full_backup
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
4 times, most recently
from
March 26, 2024 06:23
ab6fa5e
to
33878b2
Compare
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
6 times, most recently
from
April 2, 2024 08:17
cefced1
to
0f58353
Compare
This was referenced Apr 2, 2024
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
from
April 15, 2024 07:52
0f58353
to
c9a780d
Compare
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
from
May 20, 2024 07:24
c9a780d
to
fe47e94
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #166 +/- ##
=======================================
Coverage 18.24% 18.24%
=======================================
Files 3 3
Lines 433 433
=======================================
Hits 79 79
Misses 347 347
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
from
May 31, 2024 06:55
fe47e94
to
c788549
Compare
This was referenced May 31, 2024
ref: longhorn/longhorn 7070 Signed-off-by: Jack Lin <jack.lin@suse.com>
ChanYiLin
force-pushed
the
LH7070_support_full_backup
branch
from
May 31, 2024 08:54
c788549
to
251a4c2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref: longhorn/longhorn#7070
BackupCount
in BackupVolume, so we can calculate the interval to achieve periodically full backupNewlyUploadedDataSize
andReUploadedDataSize
to each Backup. So user can know the data transfer size for each Backup to trace the cost.Parameters
to the Backup Config.backup-mode: full
, it will pretend there is no last backup, and backup all the blocks of the current volume.