I'm not sure but i think it is a known issue that windows backup will fail if you use a schedule. the first scheduled backup will work but after that they will all fail instantly with no error. The real issue is Exchange 2013 on server 2012, windows backup. I recieve the following error. I'm not sure if this is supported yet. Writer Failures Writer Id: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7} Instance Id: {4FF80F37-194D-4453-A777-8D70BAB8F406} Writer Name: Microsoft Exchange Writer Writer State: 1 Failure Result: 800423F3 Application Result: 1 Application Message: (null) Component: 59ba8022-52fb-43b7-bd19-a9c1c8bee4cf Logical Path: Microsoft Exchange Server\Microsoft Information Store\EMAIL Component Result: 800423F3 Component Message: (null) File Spec: C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 1690277260\Mailbox Database 1690277260.edb Recursive: 0 File Spec: C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 1690277260\\E00*.log Recursive: 0 File Spec: C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 1690277260\E00.chk Recursive: 0 http://WrinkleFreeIT.com

Hello, Does this issue occur when backing up a single file? Whats the type of the disk, is it dynamic? Try restarting Windows to bring all writers into a stable state. Thanks,Simon Wu TechNet Community Support

this does not occure first time when backing up all the virtual machines for the first time, or anything time. Some of the VMs are dynamic diskshttp://WrinkleFreeIT.com

Just ran into this... make sure your database is mounted!