![]() Check again to make sure you are back up.Ĥ. To fix that you need to restart the Microsoft Exchange information store service.ģ. Information Store (2544) Shadow copy instance 1 aborted.Ģ. If you look in the Event Log you will probably also see Event ID 2007. Log onto the Exchange server, drop to command line and issue the following command OK that’s a huge error, but essentially it’s complaining about the VSS writer on the Exchange server. I connected to the Veeam backup server and this was the error. Without a good backup to flush the logs things had steadily got worse. Also he had added 1500 iPad clients to the network in the last few weeks, and the transaction logs were going up by about 20 GB a day. ![]() I rang the client who told me the drive in question was the transaction log volume for Exchange, (which with failing backups would make sense). I know this client well enough to know if it was something simple he would have fixed it himself, so while my laptop booted I armed myself with a coffee.īy the time I got on remotely, Ben on the help desk had also got online and was giving me the heads up on what the NAble proactive system had flagged up during the night, one drive was practically full, and it had filled up quickly. Yesterday morning, I walked into the office, the boss told me a client’s Exchange was running slowly and they had had a Veeam backup fail.
0 Comments
Leave a Reply. |