Arq Backup on Twitter: "@mjtsai It should just go back and upload the changed files and then complete the backup record. Sorry about that. I’ll try to reproduce."

Country	Code	For customers of
United States	40404	(any)
Canada	21212	(any)
United Kingdom	86444	Vodafone, Orange, 3, O2
Brazil	40404	Nextel, TIM
Haiti	40404	Digicel, Voila
Ireland	51210	Vodafone, O2
India	53000	Bharti Airtel, Videocon, Reliance
Indonesia	89887	AXIS, 3, Telkomsel, Indosat, XL Axiata
Italy	4880804	Wind
3424486444	Vodafone
» See SMS short codes for other countries

Michael Tsai ‏@mjtsai Jul 19

Restoring from CrashPlan. Mac client has been stuck loading the file list for an hour. Took about 30 seconds to get file from Web interface.
Peter Steinberger ‏@steipete Jul 19

@mjtsai big fan of @arqbackup here with Google Nearline Storage. I own the encryption keys and there’s a command line tool.
Michael Tsai ‏@mjtsai Jul 19

@steipete @arqbackup I use Arq as well. Second choice for restores due to Glacier delay. Great overall, but tons of issues with 5.x.
1 like
Arq Backup ‏@arqbackup Jul 19

@mjtsai Still tons of issues?
Michael Tsai ‏@mjtsai Jul 19

@arqbackup Most are fixed as of 5.1.8. Still problems with validation/enforcement and large files that change during upload.
Arq Backup ‏@arqbackup Jul 19

@mjtsai Working on validation performance. What’s the problem with large files changing?
Michael Tsai ‏@mjtsai Jul 19

@arqbackup I have e-mailed about that. Basically, the backup never completes. It keeps going back and uploading new changed pieces.
Arq Backup ‏@arqbackup Jul 19

@mjtsai OK. If a file changes between scan and upload, it goes around and scans/uploads the file afterward.
Michael Tsai ‏@mjtsai Jul 19

@arqbackup Right. Since the file keeps changing it goes around and around. Backup never completes and also blocks other backups.

‏@arqbackup

@mjtsai It should just go back and upload the changed files and then complete the backup record. Sorry about that. I’ll try to reproduce.

7:19 AM - 20 Jul 2016

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.