APFS-levyn kloonaus
Lähetetty: 15.11.2017 klo 11.02
Olen hankkimassa uuden iMacin SSD-levyllä. Nykyisin teen varmuuskopion päivittäin SuperDuperilla.
Uusi APFS tiedostojärjestelmä on ongelmallinen kloonauksen kannalta, koska se paisuttaa varmuuskopiota.
Olisin kiinnostunut kuulemaan kokemuksia siitä kuinka paljon SuperDuperin (versio 3) tai CCC:n kloonatut varmuuskopiot ovat paisuneet. Ongelmaksi saattaa muodostua se, että varmuuskopio ei ehkä enää mahdukaan kopioidulle levylle, kun sitä tarvittaisiin.
t. HV
Lisää tietoa asiasta:
http://www.shirt-pocket.com/blog/index. ... nal_twins/
Carbon Copy Clonerin kehittäjä varoittaa samasta asiasta:
https://bombich.com/kb/ccc5/everything- ... r-and-apfs
Why doesn't the disk usage on my backup disk match the disk usage on the source disk?
CCC's global exclusions as well as the SafetyNet feature have traditionally led to legitimate differences in disk usage in the past. The aforementioned APFS file cloning feature, however, adds a new dimension to this concern. While APFS file cloning saves space on your source volume, those space savings can't be consistently applied when copying your files to another volume (because Apple doesn't offer a way for us to determine that one file is a clone of another). Making matters worse, Finder does not accurately represent the true disk usage of your files. Finder doesn't take into consideration whether one file is a clone of another (again, because Apple doesn't provide a way to make that assessment), so it sums up the total size of each file and folder, presenting a total value that is possibly astronomically higher than the capacity of the disk.
If you convert your Mac's disk to APFS, understand that the disk usage on your source and destination may never add up, and therefore may not be a reliable measure for comparing the source and destination.
Uusi APFS tiedostojärjestelmä on ongelmallinen kloonauksen kannalta, koska se paisuttaa varmuuskopiota.
Olisin kiinnostunut kuulemaan kokemuksia siitä kuinka paljon SuperDuperin (versio 3) tai CCC:n kloonatut varmuuskopiot ovat paisuneet. Ongelmaksi saattaa muodostua se, että varmuuskopio ei ehkä enää mahdukaan kopioidulle levylle, kun sitä tarvittaisiin.
t. HV
Lisää tietoa asiasta:
http://www.shirt-pocket.com/blog/index. ... nal_twins/
Carbon Copy Clonerin kehittäjä varoittaa samasta asiasta:
https://bombich.com/kb/ccc5/everything- ... r-and-apfs
Why doesn't the disk usage on my backup disk match the disk usage on the source disk?
CCC's global exclusions as well as the SafetyNet feature have traditionally led to legitimate differences in disk usage in the past. The aforementioned APFS file cloning feature, however, adds a new dimension to this concern. While APFS file cloning saves space on your source volume, those space savings can't be consistently applied when copying your files to another volume (because Apple doesn't offer a way for us to determine that one file is a clone of another). Making matters worse, Finder does not accurately represent the true disk usage of your files. Finder doesn't take into consideration whether one file is a clone of another (again, because Apple doesn't provide a way to make that assessment), so it sums up the total size of each file and folder, presenting a total value that is possibly astronomically higher than the capacity of the disk.
If you convert your Mac's disk to APFS, understand that the disk usage on your source and destination may never add up, and therefore may not be a reliable measure for comparing the source and destination.