Gordon_McKee
Level 3
Joined 17 years ago
User Profile
User Widgets
Contributions
Re: "Microsoft Information Store" is not snappable
Just looked again through the event logs and came across this error: Adamm Mover Error: MoverDeviceIo::Write - m_wrapper.WriteData failed! Error = ERROR_END_OF_MEDIA Drive = "HP 3" {C9925D5A-1CDC-4AD8-B8BA-342D218FC048} Media = "4MM000008" {6D53F866-AB0B-4687-B69E-EA87B396B908} Read Mode: SingleBlock(0), ScsiPass(0) Write Mode: SingleBlock(0), ScsiPass(0) Looks like the tape is full. It is not asking for a second tape though!! AH!!1.5KViews0likes0CommentsRe: "Microsoft Information Store" is not snappable
Also, just looked at the Job Log and the First Storage Group backs up fine - it is the Second Storage Group that comes back with the error. Set type : Backup Set status : Completed Set description : Resource name : \\SERVER\Microsoft Information Store\Second Storage Group Logon account : System Logon Account Encryption used : None Error : e0008507 - The volume cannot be snapped because the logical volume name cannot be found. Check the backup selection list and make sure that this selection is valid. Agent used : Yes Advanced Open File Option used : Yes1.5KViews0likes0CommentsRe: "Microsoft Information Store" is not snappable
Tried all of the above now. Even defraged both Exchange DBs as well to see if corruption was causing the error. Here is last nights error: Backup- \\SERVER\Microsoft Information Store\First Storage Group V-79-57344-34055 - AOFO: Initialization failure on: "Microsoft Information Store". Advanced Open File Option used: Yes. Snapshot provider error (0xE0008507): The volume cannot be snapped because the logical volume name cannot be found. Check the backup selection list and make sure that this selection is valid. Check the Windows Event Viewer for details. Backup- System?State Media mount failed. User canceled a Physical Volume Library operation. V-79-57344-33861 - The media operation was terminated by the user. Does anyone have any ideas how to fix the error please?1.6KViews0likes0CommentsRe: "Microsoft Information Store" is not snappable
OK - I was just trying to get the exchange backup working first but I get this as the whole error message: Backup- \\SERVER\Microsoft Information Store\First Storage Group V-79-57344-34055 - Note: Resource: "Microsoft Information Store" is not snappable. Attempting to back up directly from the source volume. Snapshot provider error (0xE0008507): The volume cannot be snapped because the logical volume name cannot be found. Check the backup selection list and make sure that this selection is valid. Check the Windows Event Viewer for details. Backup- SERVER V-79-57344-65233 - AOFO: Initialization failure on: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Active Directory, Writer ID: {B2014C9E-8711-4C5C-A5A9-3CF384484757}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Automated System Recovery, Writer ID: {BE000CBE-11FE-4426-9C58-531AA6355FC4}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Certificate Services, Writer ID: {6F5B15B5-DA24-4D88-B737-63063E3A1F86}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: COM+ Class Registration Database, Writer ID: {542DA469-D3E1-473C-9F4F-7847F01FC64F}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {2A40FD15-DFCA-4AA8-A654-1F8C654603F6}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {59B1F0CF-90EF-465F-9609-6CA8B2938366}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: System Files, Writer ID: {E8132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: SYSVOL, Writer ID: {D76F5A28-3092-4589-BA48-2958FB88CE29}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). I have restarted the server and got the VSSadmin to say no error and it still does the same thing. Not tried just backing up the IS - going to run just an IS backup now.. It is odd that none of the system state errors came Friday's backup - I just got the IS error. Then, Monday, I get the IS and System State errors.1.5KViews0likes0Comments"Microsoft Information Store" is not snappable
Hi I have a client that keeps getting the same error when backing up. There is nothing for the error "No Exact Matches found for: V-79-57344-34055". The full error is below. V-79-57344-34055 - Note: Resource: "Microsoft Information Store" is not snappable. Attempting to back up directly from the source volume. Snapshot provider error (0xE0008507): The volume cannot be snapped because the logical volume name cannot be found. Check the backup selection list and make sure that this selection is valid. Check the Windows Event Viewer for details. Any clues anyone? Running Win2008 SBS x64, Backupexec 12.5A failure occurred reading an object
Hi Every time I backup the System State I get the following error. NT Backup backs up all the System State no problems. There seems to be a few people with similar errors. V-79-57344-65247 - A failure occurred reading an object.WARNING: "System?State\System Files\System Files" is a corrupt file. This file cannot verify. Running SBS Std 2003 R2 with Symantec SBE 11d Std. Many thanks Gordon68Views0likes0Comments