Group: Awaiting Activation
I have Reflect V6 running on a VM Hypervisor with SQL Server and Server 2008R2. I will also note that I have the SQL extension with my Reflect software. I have my backups from within the VM going to a mapped drive that is attached via USB to the Host machine which has its own backup (Reflect V7). Recently, I have observed that the backups are failing. Just this evening after repairing some network issues with the guest OS on this machine, I attempted to run a full backup. The backup goes through the motions okay until the very end when it is about to wrap up and then it quits with the message that the backup failed. I am getting the message (within the log) each time this happens, and I will note that it is happening every time as of the last few days.
Backup aborted! - Write operation failed - The device is not ready. Note that this comes up only within the final moments of being connected just fine for over an hour in the process of writing to the drive. Just below this notice is this "I/O Performance: Read 246.1 Mb/s - Write 480.7 Mb/s"
I have dug through the event viewer everywhere and can find no more information about why exactly it stops at this stage. It seems to me that I ran across one log awhile back that said "Backup aborted - Write operation failed - Permission denied, no access to folder" Note this last one is from my memory not a copy and paste from the logs. Any ideas?
I am also having an ongoing issue trying to get email messages upon failure of backups. All of this used to work fine. Lately, I am getting very well acquainted with the need for backups so needless to say I am very troubled about this. The upside is that I am also becoming much more familiar with the Reflect software. So far, it has saved my bacon several times. Still, minus email notifications of failure I have lost a days work more than once in restoring the databases. I forgot to mention that I also do daily backups of the SQL databases at the end of each day. These have not been a problem since correcting the network issues with the VM.