Tue Mar 08, 2016 12:39 pm
Using rpi-clone to make a master backup has the advantage that the backup will fit onto any microSD card large enough to hold the occupied file space of the original so, for example, a 32GB card can be cloned to an 8GB or 16GB card if the 32GB card has less than 8GB or 16GB occupied. It's then just a matter of expanding the filesystem back out again via raspi-config when it's cloned back to a larger target.
By contrast, Win32DiskImager is a PITA because the target card must be EXACTLY the same size or larger than the original. Check the capacity of any, let's say, 32GB cards you have to hand and the chances are high that their capacities will almost certainly be different unless they're all from the same batch and are all the same make and model, so there's a fair chance that a clone of one won't fit onto another.
If you want a quick-launch installation of Bill Wilson's rpi-clone on a master Pi, take a look at my guide here...
viewtopic.php?f=29&t=137693&p=914109#p914109
Pi2B Mini-PC/Media Centre: ARM=1GHz (+3), Core=500MHz, v3d=500MHz, h264=333MHz, RAM=DDR2-1200 (+6/+4/+4+schmoo). Sandisk Ultra HC-I 32GB microSD card on '50=100' OCed slot (42MB/s read) running Raspbian/KODI16, Seagate 3.5" 1.5TB HDD mass storage.