Exchange Backup Failed

I changed the volume of my log files from L to M.

So I changed the information in database properties and moved the log files to the new location using EMC.  Since then the backup as completed with warnings.  The error says "System cannot find the path specified". I even deleted the backup files on the network share and started fresh but the backup still failed on the same F drive, which is where one of my mailbox databases are located.

But in events manager there is a an event id: 9782 saying that VSS has completed a backup of the database (including the database in the F drive). And the log files for this database will not be truncated.

I did a VMware vmotion just before the first backup started.

Any ideas?.
Treadstone21Asked:
Who is Participating?
 
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Changed Volume of Logs without changing Backup.

Never a good idea, to vMotion or Storage vMotion, when you are running a backup.
0
 
Treadstone21Author Commented:
I forgot to add that I did a VMware vMotion just before this.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Repeat and test again, not a good idea, to vMotion before a Backup it's about to start, because the Snapshot process will quicse the machine using VSS also, if you got two processes trying to use VSS, it's likely to fail.

Check Backup again, and see if you can generate the same fault, without vMotioning! (this time)
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Treadstone21Author Commented:
Well the vMotion was not running at the time.  The vMotion was completed a 4pm yesterday and the backup started at 6pm.  I ran it gain today and it failed again.

I must add that the first vMotion failed due to insufficient disk space.  So it created a separate folder. with an "_1" at the end.
0
 
Treadstone21Author Commented:
And the wired thing is it that it only failed on 1 volume twice?  Cannot find specified file path?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
do you still have an F: drive attached to this VM?
0
 
Treadstone21Author Commented:
Yep and after the vMotion completed I increased the vmdk file and migrated some users over to it?
And a user that is in this databased located on the F drive emailed me today.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
vMotion failing due to insuffucient is odd, because unless you did a storage vmotion, in a vmotion the data doesn't move, although it would create a snapshot. But for it to fail, you must have been very low on space, less than 15%?
0
 
Treadstone21Author Commented:
It was a storage vmotion actually, sorry to a new datastore.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
ah okay! that explains alot!

Are you still having issues backup up now?
0
 
Treadstone21Author Commented:
No, I re-created the scheduled backup and I am ok now. What do you think was the issue?
0
 
Treadstone21Author Commented:
I did change it, but I didn't remove it completely and start fresh, which is what I did last and it worked.

Seems to be ok now, thank a lot, expert!!
0
 
Treadstone21Author Commented:
I did change it, but I didn't remove it completely and start fresh, which is what I did last and it worked.

Seems to be ok now, thank a lot!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.