Here’s a great tip for newbie Systems Administrators:

Check regularly for updated drivers and firmware

You’ll never know when things start breaking on you.

No related posts.

We were getting failed backups of our Exchange 2007 server on Symantec’s Backup Exec 12d. The error Backup Exec 12d gave us was:

V-79-32772-8928
- AOFO: Initialization failure on: “Microsoft Information Store”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11233 – VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time.  Try running the job later.

- AOFO: Initialization failure on: “Microsoft Information Store”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11233 – VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time.  Try running the job later.

- AOFO: Initialization failure on: “Microsoft Information Store”. Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11233 – VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time.  Try running the job later.

Info:

Check to make sure there are no errors with VSS by opening the command prompt on your mail server and typing in:

vssadmin list writers

Doing so will list all the writers registered with VSS. If you see the Exchange writer in an error or failed state then the overall solution would be to restart the information store and the Exchange server.

In our case, everything was stable.

Solution:

From the command prompt on Exchange Server enter:

1. net stop vss
2. net stop swprv
3. regsvr32 ole32.dll
4. regsvr32 vss_ps.dll
5. Vssvc /Register
6. regsvr32 /i swprv.dll
7. regsvr32 /i eventcls.dll
8. regsvr32 es.dll
9. regsvr stdprov.dll
10. regsvr32 vssui.dll
11. regsvr32 msxml.dll
12. regsvr32 msxml4.dll
13. net start swprv
14. net start vss

Re-run your job in Backup Exec 12d and the job should run successful

Related posts:

1. Insufficient Disk Space – e000848f – Backup Exec Restore
2. Exchange 2007 Not Receiving Emails From a Domain
3. Windows Server 2003 Event ID 1030 & 1058

I was performing a granular restore of a user’s mailbox on Microsoft Exchange 2007 using Symantec Backup Exec 11d on the Exchange Server 2007 but received an “e000848f – Insufficient disk space” error which links to V-79-57344-33935. Our free space was down to just under 1 GB. We have TreeSize installed on the server and it looked like a Temp folder was holding too much data.

Looking into it even more I found that Backup Exec 11d will use a default folder located in C:\Temp as a staging area for restores. That default location is stored on a smaller partition that we had initially set for just programs so I had to move it to a larger partition on the same server. To resolve this we had to change the staging area to a new path, specifically – enough space to cover the information store.

To do this:

1. Open Backup Exec
2. Select ‘Tools’
3. Select ‘Options’
4. On the left side under ‘Job Defaults’ select ‘Restore’
5. On the right side, on the bottom where it says “Path on media server for staging temporary restore data when restoring individual items from tape” – Change the default path to another partition with larger disk space.
6. Then Click on ‘Microsoft Exchange’ under Job Defaults  on the left
7. In the right, under ‘Microsoft Exchange 2000 and later’ change the temporary location for log and patch files to your new temp location.
8. Click OK

This update will not apply to existing actions that had the default path.

If you are doing a stand-alone restore of a user’s mailbox or individual folder there is one other action you must select. On the restore job properties window:

• Click on ‘Microsoft Exchange’ on the left side under “Settings”
  On the right side near the bottom under “Path on Exchange Server for temporary storage of log and patch files” – change the default path to the new path (a partition with extra storage space)

**Important**

The way that Backup Exec 11d does granular restores is that it will stage the entire information store on the path you have set. You will need to have that much free hard drive space in order to do a granular restore for just one or a few users. My organization is fairly small (under 200 users) but our information store is larger than 30GB. Just a heads up for all of you.

If you have any questions please feel free to leave a comment

Related posts:

1. Exchange 2007 & Backup Exec 12d Failed Backups
2. Exchange 2007 Not Receiving Emails From a Domain
3. Windows Server 2003 Event ID 1030 & 1058