AOFO error on BE server but AOFO not selected! iSCSI Snapshots mounted
Hi,
My backup records the following in the log immediately under the server name before any data is backed up:
- AOFO: Initialization failure on: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot provider that you selected cannot snap this volume. Select the default snapshot provider, and then run the job again.
The following volumes are dependent on resource: "C:" "C:\MNT\ZSNAPSHOT-1-FILE1-F-\" "C:\MNT\ZSNAPSHOT-1-FILE1-G-\" "C:\MNT\ZSNAPSHOT-1-SQL1-E-V\" .
The server in question is the Backup Exec server itself (12.5, Windows Server 2008), and I think the cause may well be those volumes mounted under C:\MNT.
Interestingly however, I deselected the AOFO option in the log.
I read in one post that someone had to enable AOFO and select the Microsoft Volume Shadow Copy option to make it work, however I am not sure that this will work given that I have iSCSI LUNs mounted as directories on the volume. The files are closed - I don't need a snapshot for these.
http://www.symantec.com/connect/forums/aofo-initialization-failure-windows-2008-server-not-using-aofo
Any thoughts before I just give it a whirl?
Thx,
Simon.
Comments
For backup of shadow copy
For backup of shadow copy components, VSS is always used, even if AOFO is unselected. The reason for these being, the writers presented by Microsoft for these services. Could you expand shadow copy components of this server in the selection list, highligh service state and provide the screenshot of what you see on the right hand side.
Also, could you provide more information on which service is using these mounted iscsi volumes? In shadow copy components, the writer of that particular service must be present, whcih also tries to create snapshot of these iscsi volumes, which is not happening. If you would like, you may uncheck that particular service from shadow copy components -> service state.
Thanks
Thanks, interesting. This
Thanks, interesting.
This backup only backs up C:\mnt and a single log file on D:\.
There is a pre-command script which mounts the snapshots to directories under C:\mnt, and a post-command script that removes them.
I have attached a pic of the Service State in case it is still relevant...
use AOFO in backup options
If the services are running on the target machine and the vss writer status seems fine:
I would recommend to try the backup with selected AOFO for MS provider, too.
Just give it a try, I do not believe that this could damage anything.
best regards
Dominik
If this answers your question or solves your problem, I would appreciate if you mark my post as the solution. Thank you!
Consultant
PMCS.helpLine Software Gruppe
www.pmcs.de
follow us on Twitter: PMCS_NBU ; PMCS_BE ; PMCS_EV
Thanks Dominik - I'll give it
Thanks Dominik - I'll give it a whirl and let you know how it goes.
Unfortunately it still does
Unfortunately it still does not work with AOFO enabled and Microsoft Volume Shadow Copy Service selected with the Automatic provider option.
Any other ideas?
I don't understand why it needs to do any AOFO at all... the only items selected are standard files and directories, which I *know* are not open anywhere.
I have a related problem whereby the incrementals are not working correctly. I have opened a new thread here:
http://www.symantec.com/connect/forums/incremental...
Thanks.
Same problem for me with
Same problem for me with VMware VCB
@xadox
Open a new Thread for it, with a descripton of the problem and the exact error message from the job log.
I do not believe, that your problem has the same source.
best regards
Dominik
Consultant
PMCS.helpLine Software Gruppe
www.pmcs.de
follow us on Twitter: PMCS_NBU ; PMCS_BE ; PMCS_EV
I already have a open thread
I already have a open thread for it.
https://www-secure.symantec.com/connect/forums/bac...
Still fighting with the AOFO
Still fighting with the AOFO issue. Any new ideas?
Still fighting with the AOFO
Still fighting with the AOFO issue. Any new ideas?
Would you like to reply?
Login or Register to post your comment.