BACKBLAZE SUPPORT NUMBER ARCHIVE
BACKBLAZE SUPPORT NUMBER ZIP

I opened a Backblaze support ticket to find out the archives had a checksum I could use to verify the download (none is displayed on the download page). (please check that you have transferred or created the zipfile in theĪppropriate BINARY mode and that you have compiled UnZip properly ) Warning : 122632979645 extra bytes at beginning or within zipfileĮrror : start of central directory not found

BACKBLAZE SUPPORT NUMBER ARCHIVE

It was only when I tried to extract the archive that things started going wrong. By Monday evening the download was finished. The download ran at 65 - 70Mbps for most of Sunday and Monday (except when it was paused so I could watch Netflix).

BACKBLAZE SUPPORT NUMBER ZIP

Once the first file was downloaded and the zip extracted (to a new drive) I felt confident that this was going to be a piece of cake, and kicked off the second download. The result was pretty impressive, maintaining over 70Mbps on my 100Mbps connection. I installed the Backblaze Downloader, and set it to restore the smaller file using 10 threads. Once Backblaze was done zipping up my restores, the downloads were listed at 250GB and 500GB. I decided to split my restore into two downloads. That still left plenty of time to download the files, but I didn’t want to cut it too fine. Of greater concern for me was that I’d now wasted half of Backblaze’s 4 week retention period. This wasn’t a concern for me in this case, but it’s worth being aware of.

When a drive is disconnected, it seems Backblaze treats the files as deleted, and since the notification of the disconnected drive took 2 weeks, the granularity available for restore was reduced considerably. The first issue I ran into was the interface for restoring files from external drives that are no longer attached. I have the server backed up to Backblaze, and since we have a pretty decent fiber connection I assumed it wouldn’t be too much of an issue to just download the backup.

If I’d been watching more TV I might have noticed the issue earlier. The drive actually appeared ok in Finder - the way I found out was actually a warning email from Backblaze explaining that the drive hadn’t been connected for 14 days. I was recently unlucky enough to discover one of the external drives attached to my Plex server had failed. Restoring a Failed Hard Drive from Backblaze

Backblaze support number