I'm seeing a repeated problem with several clients using iBackup for both cloud and local backups. The cloud backup seems to work ok, but the local backups - backing up to a share on a server as a mapped drive, seems to repeatedly and utterly fail. I've worked with support to try to identify why this seems to be happening so often at so many different accounts and the fix in the past has been "install the latest update of client software" and sometimes it will run and then eventually will fail again with the error "Unable to continue the scheduled Backup. Reason: Drive X:\ is not connected." although drive X is indeed connected and available to the user under which the program is running. I'm posting this here to see if anyone else is experiencing this issue and what they have been able to learn about what's causing it and ideally how we can fix it. I really like the iBackup product performance in general and certainly the costs for my clients, but this single irritating recurring problem and my difficulty in obtaining the level of support to resolve it is really starting to get to me. Anyone else seeing this issue with local backups using iBackup when the destination is a local network location that is a mapped drive?
↧