VeeamAgent.exe - No Disk

[rizks_2000]

Performed my first test run on a replication and got the attached error.

VeeamAgent.exe - No Disk

There is no disk in the drive. Please insert a disk into Drive D:.

What is this error?

[Gostev]

Sounds like your replication job is set to perform initial sync over removable storage?

[rizks_2000]

No...don't have it checked. I hit Cancel on the dialogue box and it is now running.

[Gostev]

OK. If you want to get to the bottom of this, please send the log files from Help | Support information to our support email address. We will be able to see what exactly caused this disk access attempt.

[rizks_2000]

I'm using the trial version. They still going to support me? What is the address? I have the files ready.

[Gostev]

Yes, we provide assistance during evaluation period, just with lower priority than paying customers. The address is support@veeam.com, please also reference this thread in the email.

[cjnichol]

I am looking for a resolution for this issue... I have the same problem. During a scheduled replication I am prompted, "There is no disk in the drive. Please insert a disk into drive D:" Drive D: is the CD ROM drive. There is no reason it should be looking for this drive (at least that I can find.) If I manually select "Cancel" the job completes successfully, however it fails otherwise.... not an option for a scheduled task.

Thanks in advance.

[Vitaliy S.]

You need to contact our technical team, as It's hard to investigate what is causing this disk access attempt without seeing all log files or doing a webex session.

[Alexey D.]

While our support is investigating the logs, you may take a look at this topic with some suggestions: Windows - Drive Not Ready : Exception Processing

[KrisBoutilier]

I am experiencing the same issue running replication jobs in 'Virtual Appliance' mode with 5.0.2.230 (32 bit) on Windows 2003 R2 SP1 (32 bit).

The popup appears when each vmdk to be backed up is first attached to the guest where veeamagent.exe is running. The Veeam guest has one hard drive configured with one partition (C:) and one CDRom drive (D:).

Changing the drive letter assigned to the CDRom drive from D: to E: using Windows Disk Manager seems to work around the issue.