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

File-level SAFE/SYSTEM/USER backup/restore #50

Open
igniscitrinus opened this issue Jul 22, 2018 · 5 comments
Open

File-level SAFE/SYSTEM/USER backup/restore #50

igniscitrinus opened this issue Jul 22, 2018 · 5 comments
Labels
enhancement New feature or request

Comments

@igniscitrinus
Copy link

Given the Switch's propensity to utilizing the microSD over the eMMC for storage purposes, it's common to find that the on-board storage is largely unused.
Having the option to perform backups on a file level would significantly cut down the time required to perform a backup over block-level backups (Especially so for SAFE and USER).

@CTCaer
Copy link
Owner

CTCaer commented Jul 22, 2018

This was feature that a lot of thought went into it.

It requires the utilization of BIS keys and needs a greater code complexity.
Also a restore will utilize the formatting and directory traversing of FatFs, which will increase the binary size to great lengths.
This cannot fit, in hekate.

But a smart backup/restore option is nice to have.
So maybe this can be added as a payload module (now that payload launching was materialized internally).

So, I'll keep it open.

@CTCaer CTCaer added the enhancement New feature or request label Jul 22, 2018
@Serfrost
Copy link

Serfrost commented Apr 6, 2019

I've been wondering about this for awhile and would like to say I think this would be greatly appreciated by anyone who keeps multiple backups, either for redundancy or being able to restore a rawnand.bin from previous firmware versions.

As it stands, the very first backup made on a fresh Nintendo Switch is indeed 29GB, but you can use an archive manager to ZIP the rawnand.bin with Normal compression and it will reduce the size of this backup to give or take 756MB.

When the sectors of the NAND have been used at any point in time, say, by installing a game, this makes compressing the rawnand.bin image impossible, at least up to the point of what was already written to; even if you System Format.

29GB backups add up, so I'd love to see an option to be able to make these smaller.

nand_backup_size

@giorgi1324
Copy link

Here with the same feedback as @Serfrost

OLED full nand backups are pretty much uncompressable and take a lot of space.

Is there any chance we could get an intermediate solution for this where we can skip the USER partition from the backup? My very limited understanding is that there's nothing critical in it for the recovery of Switch.

@CTCaer
Copy link
Owner

CTCaer commented Jun 9, 2023

@giorgi1324 that's already a thing.
Just run the eMMC SYS option instead of GPP.

@giorgi1324
Copy link

Oh amazing! I wish the guides out there mentioned this. Thanks for your fast response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants