This issue is documented here http://support.microsoft.com/kb/817688Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:Exchange 2010 | Exchange 2007 | MCTS:OCS 2007 | Exchange 2010 | Exchange 2007 | MCSA:Messaging | Security | MCSE:Messaging | Security | MCP

Hi Jasjit, I am getting below error while taking exchange backup through ntbackup. Can you please help me. Backup Status Operation: Backup Active backup destination: File Media name: "new exchange_TUESDAY_10/11/2011 at 5:01 PM" Volume shadow copy creation: Attempt 1. Backup of "MSILEXVS02\Microsoft Information Store\First Storage Group" Backup set #1 on media #1 Backup description: "new exchange_TUESDAY_10/11/2011 at 5:01 PM" Media name: "new exchange_TUESDAY_10/11/2011 at 5:01 PM" Backup Type: Normal Backup started on 10/11/2011 at 5:02 PM. Backup completed on 10/11/2011 at 8:53 PM. Directories: 5 Files: 283 Bytes: 74,315,351,954 Time: 3 hours, 50 minutes, and 30 seconds Backup of "MSILEXVS02\Microsoft Information Store\Second Storage Group" Backup set #2 on media #1 Backup description: "new exchange_TUESDAY_10/11/2011 at 5:01 PM" Media name: "new exchange_TUESDAY_10/11/2011 at 5:01 PM" Backup Type: Normal Backup started on 10/11/2011 at 8:53 PM. Error: The device reported an error on a request to write data to media. Error reported: Invalid command. There may be a hardware or media problem. Please check the system event log for relevant failures. The operation was ended. Backup completed on 10/12/2011 at 9:25 AM. Directories: 5 Files: 9 Bytes: 143,320,509,920 Time: 7 hours, 39 minutes, and 46 seconds Error: MSILEXVS02\Microsoft Information Store\Second Storage Group is not a valid drive, or you do not have access. The operation was ended. Backup completed on 10/12/2011 at 9:25 AM. Directories: 5 Files: 9 Bytes: 143,320,509,920 Time: 7 hours, 39 minutes, and 48 seconds ---------------------- The operation did not successfully complete. ----------------------

This issue is documented here http://support.microsoft.com/kb/817688Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:Exchange 2010 | Exchange 2007 | MCTS:OCS 2007 | Exchange 2010 | Exchange 2007 | MCSA:Messaging | Security | MCSE:Messaging | Security | MCP

Hi Jasjit, Thanks for help.

Hi Jasjit, everyday i came with new probs, but i got help from you thanks.

Dear All, I am getting below warning in exchange 2k3 Please suggest.

Manjeet, As pointed out in the event you are about to run out the of the log file sequence. This is normal if this exchange is operational for years. So to work around this is to generate new log file sequence starting from 0x00000001. To do that follow the below steps. 1. Perform a full backup of this storage group (It would involve all the stores in this storage group) 2. Dismount all the stores in this storage group. 3. Move all the log files from this storage group location (if any, as the full backup should have purged all the logs so there would be very minimal log files) 4. Go ahead and mount all the stores in this storage group it will create new log file sequence. 5. Once done perform a full back up again. Thanks, Jasjit Singh Dhindsa Jasjit Singh Dhindsa Solution Architect Mahindra Satyam (Partner)

No worries Manjeet ...Keep them comming we are here to help ..But make sure to mark them as answered (if it really helped) as this will keep the motivation up :) Jasjit Singh Dhindsa | ITIL v3 | IASA Foundation Certified | MCITP:Exchange 2010 | Exchange 2007 | MCTS:OCS 2007 | Exchange 2010 | Exchange 2007 | MCSA:Messaging | Security | MCSE:Messaging | Security | MCP

Thanks Jasjit. one more query, once we will delete or move the logs file and mount the dbase, it will automatically create new logs file with new sequence numbers. M i right?

More details avaible on article http://technet.microsoft.com/en-us/library/aa998701(EXCHG.80).aspxJasjit Singh Dhindsa, Solution Architect, Mahindra Satyam (Partner)

Yes thats correct. It will start from log file sequence 0x0000001Jasjit Singh Dhindsa, Solution Architect, Mahindra Satyam (Partner)

Dear Jasjit, Thanks for support and gr8 artical.