Hi there
Tried a bit around with the backup functions in hekate and get the following results :
Creating a filebased emummc results in 4 GB parted files, independent where the SD format is Fat32 or exFat.
Creating a backup from a RAW Partition results in 2 GB parted files on Fat32 and in one 29 GB file on exFat.
Migrating all those backups in a emummc shows no noticeable differences in performance or speed, wether using the 2 GB or 4 GB parts, nor the single file.
But why every function generates different file parts and sizes and sometimes consider the fileformat (backup the RAW partition) and sometimes not (creating a emummc from sysnand) ?
Also no noticeable differences between filebased and RAW partition based emummc. What‘s recommend for best performance and security ? It‘s still a RAW partition ? Is exFat still not save ?
Greetings, Snap.
Tried a bit around with the backup functions in hekate and get the following results :
Creating a filebased emummc results in 4 GB parted files, independent where the SD format is Fat32 or exFat.
Creating a backup from a RAW Partition results in 2 GB parted files on Fat32 and in one 29 GB file on exFat.
Migrating all those backups in a emummc shows no noticeable differences in performance or speed, wether using the 2 GB or 4 GB parts, nor the single file.
But why every function generates different file parts and sizes and sometimes consider the fileformat (backup the RAW partition) and sometimes not (creating a emummc from sysnand) ?
Also no noticeable differences between filebased and RAW partition based emummc. What‘s recommend for best performance and security ? It‘s still a RAW partition ? Is exFat still not save ?
Greetings, Snap.