Re: R2 VSS backup issue
Interestingly enough, I ran a successful backup this morning after unloading Trend Office Scan and also waiting until Backup Exec was finished. I have another one scheduled for 10 AM with Trend loaded but BUExec idle. - Original Message - From: Michael B. Smith michael @ smithcons .com To: MS-Exchange Admin Issues exchangelist @ lyris .sunbelt-software.com Sent: Thursday, March 25, 2010 6:07:46 PM GMT -05:00 US/Canada Eastern Subject: RE: R2 VSS backup issue You need to be looking at: A] are you releasing and deleting snapshots after you copy them to the backup drive? B] how much VSS storage space you allow and whether the current backup now exceeds it. Check out the vssadmin command. Regards, Michael B. Smith Consultant and Exchange MVP http :// TheEssentialExchange .com From: Chipshead @comcast.net [ mailto : Chipshead @comcast.net] Sent: Thursday, March 25, 2010 6:00 PM To: MS-Exchange Admin Issues Cc: exchangelist @ lyris .sunbelt-software.com Subject: R2 VSS backup issue 2008 R2 server using VSS to backup Exchange 2010 to a network shared folder. Backups ran fine until this past Monday. They now fail consistently with The backup operation that started at '2010-03-25T20:37:30.509267500Z' has failed with following error code '2147943530' (Not enough server storage is available to process this command.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. Size of backup set is @ 100 GB. Target shared network backup folder resides on a drive with 1 TB free. Sever hosting shared backup folder is also a media server for Backup Exec 2010. 2008 VSS backup has been running fine while network backups run. 2008 R2 server has @ 100 GB free on C:\. Event log, Google and technet seems useless. Tried creating an differnt folder to backup to with no sucess. I'm thinking it may be some sort of a conflict with BU Exec but I question why iot started happening this past Monday when previously it was backin up fine. Any input appreciated. Thanks. Steve
R2 VSS backup issue
2008 R2 server using VSS to backup Exchange 2010 to a network shared folder. Backups ran fine until this past Monday. They now fail consistently with The backup operation that started at '2010-03-25T20:37:30.509267500Z' has failed with following error code '2147943530' (Not enough server storage is available to process this command.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. Size of backup set is @ 100 GB. Target shared network backup folder resides on a drive with 1 TB free. Sever hosting shared backup folder is also a media server for Backup Exec 2010. 2008 VSS backup has been running fine while network backups run. 2008 R2 server has @ 100 GB free on C:\. Event log, Google and technet seems useless. Tried creating an differnt folder to backup to with no sucess. I'm thinking it may be some sort of a conflict with BU Exec but I question why iot started happening this past Monday when previously it was backin up fine. Any input appreciated. Thanks. Steve
RE: R2 VSS backup issue
Steve: Make sure that quota management is not involved . . . Clyde W. Bennett, President Clyde Bennett Associates 1011A S. Congress Ave. Austin, Texas 78704-1126 (512) 442-3744 fax (512) 442-4014 www.cwbserv.com http://www.cwbserv.com/ cbenn...@cwbserv.com mailto:cbenn...@cwbserv.com From: chipsh...@comcast.net [mailto:chipsh...@comcast.net] Sent: Thursday, March 25, 2010 5:00 PM To: MS-Exchange Admin Issues Cc: exchangelist@lyris.sunbelt-software.com Subject: R2 VSS backup issue 2008 R2 server using VSS to backup Exchange 2010 to a network shared folder. Backups ran fine until this past Monday. They now fail consistently with The backup operation that started at '2010-03-25T20:37:30.509267500Z' has failed with following error code '2147943530' (Not enough server storage is available to process this command.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. Size of backup set is @ 100 GB. Target shared network backup folder resides on a drive with 1 TB free. Sever hosting shared backup folder is also a media server for Backup Exec 2010. 2008 VSS backup has been running fine while network backups run. 2008 R2 server has @ 100 GB free on C:\. Event log, Google and technet seems useless. Tried creating an differnt folder to backup to with no sucess. I'm thinking it may be some sort of a conflict with BU Exec but I question why iot started happening this past Monday when previously it was backin up fine. Any input appreciated. Thanks. Steve image001.gifimage002.jpg
RE: R2 VSS backup issue
You need to be looking at: A] are you releasing and deleting snapshots after you copy them to the backup drive? B] how much VSS storage space you allow and whether the current backup now exceeds it. Check out the vssadmin command. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: chipsh...@comcast.net [mailto:chipsh...@comcast.net] Sent: Thursday, March 25, 2010 6:00 PM To: MS-Exchange Admin Issues Cc: exchangelist@lyris.sunbelt-software.com Subject: R2 VSS backup issue 2008 R2 server using VSS to backup Exchange 2010 to a network shared folder. Backups ran fine until this past Monday. They now fail consistently with The backup operation that started at '2010-03-25T20:37:30.509267500Z' has failed with following error code '2147943530' (Not enough server storage is available to process this command.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved. Size of backup set is @ 100 GB. Target shared network backup folder resides on a drive with 1 TB free. Sever hosting shared backup folder is also a media server for Backup Exec 2010. 2008 VSS backup has been running fine while network backups run. 2008 R2 server has @ 100 GB free on C:\. Event log, Google and technet seems useless. Tried creating an differnt folder to backup to with no sucess. I'm thinking it may be some sort of a conflict with BU Exec but I question why iot started happening this past Monday when previously it was backin up fine. Any input appreciated. Thanks. Steve
