I have humyo backup premium account which is
working just great.
Then I installed avast home and then suddenly
I could not upload big files anymore to humyo
(above 4gb)
I disabled all the online scanners but still same problem.
Then i emailed humyo support and they told me
that avast was blocking the uploading of all files
of 4gb or more to humyo .
So i tried to uninstall avast and suddenly it worked.
So does this mean that i can not use humyo while i use avast?
Is there some kind of setting or exclusion i can
setup in avast home that tell it to not
scan and block humyo `?
Or do i simply have to uninstall it in order for it to work
with the big files?
I have some big backup files that i have made with
acronis true image and acronis does not have a file size
setting so they have to be big and i like acronis and
it has always helped me out during system crash and so on.
I have a client for uploading files.
It works perfect with smaller files
and can upload them with
my full uploadrate from my isp.
It works like a virtual drive.
I drag n drop files down to the
virtual humyo drive and it starts uploading the
files . It also support resume for all files
if windows goes crashing down i can just resume
my file from the same place as i left it.
The humyo z drive is placed
here:
My computer / network drives/z humyo smartdrive
The drive is installed like any software and is not
a one file cleint.
Firstly, avast has no blocking function, it scans and alerts to infection but doesn’t block and that goes for large or small files. So the assumption by Humyo support is incorrect.
avast doesn’t scan outbound traffic other than email traffic, it isn’t a firewall.
Having disabled all the on-line scanners, tends to support what I said above.
The client you use to upload, does it use ftp Protocol (which isn’t monitored by avast) as the only thing I can think of is that for large files whilst they are being scanned, the connection could time out. So if there are any connection settings in the client, I would try increasing them. I’m not even sure if they are, depending on how they are sent, hence the previous question by nmb.
Try this to see what is actually being scanned (as I don’t recommend excluding a whole drive):
Standard Shield - Left click on the avast ‘a’ icon, click the Details… >> button if shown, select the Standard Shield provider > Customize > Advanced - ‘Show detailed info on performed actions’ this option is off by default
What errors are being displayed when this upload fails ?
Have (or did) you another AV installed in this system, if so what was it and how did you get rid of it ?
Not just that you don’t have another AV, if you had another before avast remnants could have an impact, though I would have expected that would be the same regardless of file size.
I have never used huymo, so I’m not familiar with its settings or workings. Edit: just seen the second picture, you could try setting it to Don’t use a proxy, assuming that your ISP doesn’t require you to use one.
Unless the huymo log files give an explicit reason for the failure, that wouldn’t help as I have no experience of huymo.
If by details you are getting, you mean the on-access scanner messages, then you are looking to see if at the time of the back-up the files being transferred/uploaded are actually being scanned by avast. Also if the upload fails, there would presumable be a (big) file sat there being scanned.
error code 423: The resource is currently locked on the storage, sourcePath=‘acronis_backup/MyBackup4561.tib’, description=’ Locked
I don’t know what there error codes are, presumably gave them the error code and they blamed the AV ?
Is the acronis_backup/MyBackup4561.tib (or similar) file name in the avast on-access scanner messages when this fails ?
Presumably you drag & drop this file acronis_backup/MyBackup4561.tib into the humyo.store ?
If so the act of doing that may be considered the creation of a new file, in which case avast’s standard shield could scan it and that should show in the on-access scanner message/s ?
If so then scanning a 4GB file would take a little time in which time the connection might fail (whilst the file is technically locked until it is scanned).
However, I would have thought that the file being locked would be in the humyo.store sub-folder.
So I don’t know if excluding the C:\Documents and Settings\R\humyo.store (is this a file or folder) might help, but that folder isn’t what is being reported as the one in error code 423.