Re: Backup Failure Volsnap errors
- From: v-stwang@xxxxxxxxxxxxxxxxxxxx (Steven Wang [MSFT])
- Date: Mon, 26 Sep 2005 11:56:25 GMT
Hi Mike,
Thanks for your reply, and sorry for my delayed response due to the weekend.
If the issue reoccurs or there is anything I can do for you on this issue,
please do not hesitate to contact us. It is always our pleasure to be of
assistance.
Thank you for using Microsoft public newsgroup!
Have a great week!
Steven Wang
Microsoft CSS Online Newsgroup Support
--------------------
>X-Tomcat-ID: 182359663
>References: <9A074D72-4775-4AD1-AE4E-B70D569F363A@xxxxxxxxxxxxx>
<1127309978.983981.59480@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: v-stwang@xxxxxxxxxxxxxxxxxxxx (Steven Wang [MSFT])
>Organization: Microsoft
>Date: Thu, 22 Sep 2005 10:37:09 GMT
>Subject: Re: Backup Failure Volsnap errors
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>Message-ID: <q3WwWG2vFHA.780@xxxxxxxxxxxxxxxxxxxxx>
>Newsgroups: microsoft.public.windows.server.sbs
>Lines: 153
>Path: TK2MSFTNGXA01.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:155519
>NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
>
>Hello Mike,
>
>Thank you for posting.
>
>>From your post, my understanding of this issue is: The backup of SBS 2003
>using Veritas Backup Exec 9.1 has failed with the error message: "The
>shadow copy of volume C: has been deleted because the shadow copy storage
>could not grow in time." If this is not correct, please feel free to let
>me know.
>
>Based on my experience, I would suggest we perform the following steps to
>narrow down the root cause of this issue:
>
>1. Temporarily disable the Veritas Backup Exec 9.1, and use the SBS 2003
>build-in Backup to test this issue. If this issue disappears when using
>SBS 2003 Backup, please contact Veritas support to see whether they have
>more information about this issue.
>
>2. If the SBS 2003 Service Pack 1 has not been installed, please install
>the SBS 2003 SP1, and go to the Windows Updates web site to make the
server
>up to date.
>
>3. Please refer to the following steps to adjust the size of the Volume
>Shadow copy area:
>
>a. Click "Start", click "Run", type "regedit" (without the quotation
>marks), and then click "OK".
>b. Locate and then click the following key in the registry:
>HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VolSnap
>c. On the "Edit" menu, point to "New", and then click "DWORD value".
>d. Type "MinDiffAreaFileSize" (without the quotation marks), and then
press
>ENTER.
>e. On the "Edit" menu, click "Modify".
>f. Type the size that you want for the shadow copy storage area, and then
>click "OK".
>
>Let's type 3000 here, the maximum size of shadow copy storage area. The
>MinDiffAreaFileSize registry key specifies the minimum size of the shadow
>copy storage area; the default setting is 300 MB, and the maximum setting
>is 3 gigabytes (GB). For an accurate setting, specify a value that is a
>multiple of 300 MB; otherwise, the next multiple of 300 MB will be chosen.
>A value of 300 is equal to 300 MB, and a value of 3,000 is equal to 3 GB.
>
>4. If the issue persists, please save the System and Application Event
Logs
>to .evt files and send them to me at v-stwang@xxxxxxxxxxxxx, so that I can
>perform further research. Please also collect the backup log from
>C:\Documents and Settings\SBS Backup User\Local Settings\Application
>Data\Microsoft\Windows NT\NTBackup\data folder.
>
>More Information
>--------------------------
>Time-out errors occur in Volume Shadow Copy service writers
>http://support.microsoft.com/?id=826936
>
>Hope the above information helps. Should you have any question or
concern,
>please feel free to post back. I am glad to be of assistance.
>
>Have a nice day!
>
>Steven Wang (MSFT)
>Microsoft CSS Online Newsgroup Support
>
>Get Secure! - www.microsoft.com/security
>=====================================================
>This newsgroup only focuses on SBS technical issues. If you have issues
>regarding other Microsoft products, you'd better post in the corresponding
>newsgroups so that they can be resolved in an efficient and timely manner.
>You can locate the newsgroup here:
>http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
>
>When opening a new thread via the web interface, we recommend you check
the
>"Notify me of replies" box to receive e-mail notifications when there are
>any updates in your thread. When responding to posts via your newsreader,
>please "Reply to Group" so that others may learn and benefit from your
>issue.
>
>Microsoft engineers can only focus on one issue per thread. Although we
>provide other information for your reference, we recommend you post
>different incidents in different threads to keep the thread clean. In
doing
>so, it will ensure your issues are resolved in a timely manner.
>
>For urgent issues, you may want to contact Microsoft CSS directly. Please
>check http://support.microsoft.com for regional support phone numbers.
>
>Any input or comments in this thread are highly appreciated.
>=====================================================
>This posting is provided "AS IS" with no warranties, and confers no rights.
>
>--------------------
>>From: thrdgeek@xxxxxxxxx
>>Newsgroups: microsoft.public.windows.server.sbs
>>Subject: Re: Backup Failure Volsnap errors
>>Date: 21 Sep 2005 06:39:39 -0700
>>Organization: http://groups.google.com
>>Lines: 13
>>Message-ID: <1127309978.983981.59480@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
>>References: <9A074D72-4775-4AD1-AE4E-B70D569F363A@xxxxxxxxxxxxx>
>> <uoSL6GesFHA.2212@xxxxxxxxxxxxxxxxxxxx>
>> <CF00F438-1DD8-41D0-9E90-87998707C036@xxxxxxxxxxxxx>
>> <LK4sX8fsFHA.2732@xxxxxxxxxxxxxxxxxxxxx>
>> <LSCuhQ5sFHA.3604@xxxxxxxxxxxxxxxxxxxxx>
>> <jAe#jRJtFHA.3380@xxxxxxxxxxxxxxxxxxxxx>
>> <racgqBruFHA.768@xxxxxxxxxxxxxxxxxxxxx>
>>NNTP-Posting-Host: 67.149.186.16
>>Mime-Version: 1.0
>>Content-Type: text/plain; charset="iso-8859-1"
>>X-Trace: posting.google.com 1127309984 25866 127.0.0.1 (21 Sep 2005
>13:39:44 GMT)
>>X-Complaints-To: groups-abuse@xxxxxxxxxx
>>NNTP-Posting-Date: Wed, 21 Sep 2005 13:39:44 +0000 (UTC)
>>In-Reply-To: <racgqBruFHA.768@xxxxxxxxxxxxxxxxxxxxx>
>>User-Agent: G2/0.2
>>X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
>rv:1.7.10) Gecko/20050716 Firefox/1.0.6,gzip(gfe),gzip(gfe)
>>Complaints-To: groups-abuse@xxxxxxxxxx
>>Injection-Info: g14g2000cwa.googlegroups.com; posting-host=67.149.186.16;
>> posting-account=c8pE7Q0AAAB072ApTL437Qd4UlRQmFwF
>>Path:
>TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onl
i
>ne.de!news.glorb.com!postnews.google.com!g14g2000cwa.googlegroups.com!not-f
o
>r-mail
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:155228
>>X-Tomcat-NG: microsoft.public.windows.server.sbs
>>
>>The past two days, my backup of SBS 2003 has failed on the Shadow Copy
>>components using Veritas Backup Exec 9.1. The event log has two
>>entries saying "The shadow copy of volume C: has been deleted because
>>the shadow copy storage could not grow in time."
>>
>>I don't see that shadow copy is enabled on drive c:. Within Veritas,
>>shadow copy is selected to backup.
>>
>>Any ideas?
>>
>>Thanks,
>>Mike
>>
>>
>
>
.
- References:
- Backup Failure Volsnap errors
- From: Jaspar
- Re: Backup Failure Volsnap errors
- From: Steven Wang [MSFT]
- Backup Failure Volsnap errors
- Prev by Date: Re: Login - Using Tempoary Profile Problem
- Next by Date: Re: remote MAPI exchange access?
- Previous by thread: Re: Backup Failure Volsnap errors
- Next by thread: SBS migration
- Index(es):
Relevant Pages
|
Loading