|
|
I have found information on this issue on several sites, but no fix yet.
Problem is as follows:
After installation of WSUS 3.0 on server, Backup Exec 10.0 can no longer
back up the server. If the SQL Server VSS Writer service is stopped, Backup
Exec can then back the server up. Obviously this is not a suitable solution.
Anyone have any thoughts or suggestions on this one?
Thanks in advance.
|
|
"cjbeckwith" <cjbeckwith[ at ]discussions.microsoft.com> wrote in message
news:33286B30-0950-4A58-B5E1-6B08B9F12308[ at ]microsoft.com...
[Quoted Text] >I have found information on this issue on several sites, but no fix yet.
> Problem is as follows:
>
> After installation of WSUS 3.0 on server, Backup Exec 10.0 can no longer
> back up the server. If the SQL Server VSS Writer service is stopped,
> Backup
> Exec can then back the server up. Obviously this is not a suitable
> solution.
First question: Does Backup Exec 10.0 support SQL Server 2005 SP1 database
servers?
Second question: Does Symantec have any documentation as to how to deal with
the SQL Server (2005) VSS Writer if it is a supported platform?
Note: If you're using Backup Exec, and not NTBackup, and not using VSS, then
you probably don't need the VSS Writer service running anyway.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
I am curious if I need the VSS service running as well. As noted in the
following article from Symantecs website:
https://forums.symantec.com/syment/board/message?board.id=103&message.id=55051
It appears that disabling the SQL VSS service does in fact correct the
issue. I would assume that 10.0 does not in fact utilize the VSS service. I
will disable the service for backups for the next few evenings and have my
customer verify that all other database instances are functioning properly.
Thank you for your assistance.
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "cjbeckwith" <cjbeckwith[ at ]discussions.microsoft.com> wrote in message > news:33286B30-0950-4A58-B5E1-6B08B9F12308[ at ]microsoft.com... > >I have found information on this issue on several sites, but no fix yet. > > Problem is as follows: > > > > After installation of WSUS 3.0 on server, Backup Exec 10.0 can no longer > > back up the server. If the SQL Server VSS Writer service is stopped, > > Backup > > Exec can then back the server up. Obviously this is not a suitable > > solution. > > First question: Does Backup Exec 10.0 support SQL Server 2005 SP1 database > servers? > > Second question: Does Symantec have any documentation as to how to deal with > the SQL Server (2005) VSS Writer if it is a supported platform? > > Note: If you're using Backup Exec, and not NTBackup, and not using VSS, then > you probably don't need the VSS Writer service running anyway. > > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > |
|
"cjbeckwith" <cjbeckwith[ at ]discussions.microsoft.com> wrote in message
news:EADCF98C-8339-46EA-8D26-C42D734732F2[ at ]microsoft.com...
[Quoted Text] >I am curious if I need the VSS service running as well.
My take on the deal is that you'd only need the SQL Server VSS Writer
service running *if* you want to do backups of the WID using NTBackup (which
is VSS aware), using Volume Shadow copies.
Frankly, for the WSUS database, which doesn't have the level of activities
that many databases do, I doubt it's a big deal to forego the VSS Writer
service, use Backup Exec 10 (if that's what you've got), and take the hit
for the database being inaccessible for a couple of minutes. Unless you've
got more than a few hundred clients on the WID-based WSUS3 server, it's
highly unlikely your clients will even notice the WSUS database being
'offline' for a few minutes.
For more than a few hundred clients on a WSUS3/WID server, it might be
better to stick either with NTBackup and the VSS Writer service, or use
SqlCmd scripts to use the internal SQL Server backup commands.
Then again... if you're only doing this once a week (I'm not even sure more
than once a month to maintain metadata and approvals is necessary), then
even a weekly few minutes of downtime is likely to be a non-issue.
> It appears that disabling the SQL VSS service does in fact correct the
> issue. I would assume that 10.0 does not in fact utilize the VSS service.
I would assume that all Backup Exec v10 products are totally unaware of the
Windows Volume Shadow services, and it's probably more a function of
=interference=. For those that aren't going to upgrade to v11 (on Win2003
systems), it's probably time to switch back to NTBackup (where at least
you'll be performing backups with a *supported* tool!)
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
On 13 jun, 02:29, cjbeckwith <cjbeckw...[ at ]discussions.microsoft.com>
wrote:
[Quoted Text] > I have found information on this issue on several sites, but no fix yet.
> Problem is as follows:
>
> After installation of WSUS 3.0 on server, Backup Exec 10.0 can no longer
> back up the server. If the SQL Server VSS Writer service is stopped, Backup
> Exec can then back the server up. Obviously this is not a suitable solution.
>
> Anyone have any thoughts or suggestions on this one?
>
> Thanks in advance.
I also ran into this problem at several customers,
solution was a (free) upgrade from 10.0 to 10d
|
|
Does the VSS service need to run at all if I am not using ntbackup? The
description of the service states "Provides the interface to backup/restore
Windows Internal Database through the Windows VSS". In this instance, I am
talking about 60 stations at most. If I had to do a fresh installation of
WSUS for a recovery, I could deal with that.
Once again, the information you have provided has been great.
"Lawrence Garvin (MVP)" wrote:
[Quoted Text] > "cjbeckwith" <cjbeckwith[ at ]discussions.microsoft.com> wrote in message > news:EADCF98C-8339-46EA-8D26-C42D734732F2[ at ]microsoft.com... > >I am curious if I need the VSS service running as well. > > My take on the deal is that you'd only need the SQL Server VSS Writer > service running *if* you want to do backups of the WID using NTBackup (which > is VSS aware), using Volume Shadow copies. > > Frankly, for the WSUS database, which doesn't have the level of activities > that many databases do, I doubt it's a big deal to forego the VSS Writer > service, use Backup Exec 10 (if that's what you've got), and take the hit > for the database being inaccessible for a couple of minutes. Unless you've > got more than a few hundred clients on the WID-based WSUS3 server, it's > highly unlikely your clients will even notice the WSUS database being > 'offline' for a few minutes. > > For more than a few hundred clients on a WSUS3/WID server, it might be > better to stick either with NTBackup and the VSS Writer service, or use > SqlCmd scripts to use the internal SQL Server backup commands. > > Then again... if you're only doing this once a week (I'm not even sure more > than once a month to maintain metadata and approvals is necessary), then > even a weekly few minutes of downtime is likely to be a non-issue. > > > It appears that disabling the SQL VSS service does in fact correct the > > issue. I would assume that 10.0 does not in fact utilize the VSS service. > > I would assume that all Backup Exec v10 products are totally unaware of the > Windows Volume Shadow services, and it's probably more a function of > =interference=. For those that aren't going to upgrade to v11 (on Win2003 > systems), it's probably time to switch back to NTBackup (where at least > you'll be performing backups with a *supported* tool!) > > -- > Lawrence Garvin, M.S., MCTS, MCP > Independent WSUS Evangelist > MVP-Software Distribution (2005-2007) > https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E> > Everything you need for WSUS is at > http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx> > And, almost everything else is at > http://wsusinfo.onsitechsolutions.com> ..... > > > |
|
<larsbakker[ at ]gmail.com> wrote in message
news:1181728670.226588.293620[ at ]x35g2000prf.googlegroups.com...
[Quoted Text] > On 13 jun, 02:29, cjbeckwith <cjbeckw...[ at ]discussions.microsoft.com>
> wrote:
>> I have found information on this issue on several sites, but no fix yet.
>> Problem is as follows:
>>
>> After installation of WSUS 3.0 on server, Backup Exec 10.0 can no longer
>> back up the server. If the SQL Server VSS Writer service is stopped,
>> Backup
>> Exec can then back the server up. Obviously this is not a suitable
>> solution.
>>
>> Anyone have any thoughts or suggestions on this one?
>>
>> Thanks in advance.
>
> I also ran into this problem at several customers,
> solution was a (free) upgrade from 10.0 to 10d
From what I read on the Symantec website last night, '10d' still requires
that the SQL Server VSS Writer service be stopped.
The supported upgrade would be to Backup Exec v11, which is SQL 2005
supportable.
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
"cjbeckwith" <cjbeckwith[ at ]discussions.microsoft.com> wrote in message
news:3A3E6481-C49E-468A-821E-BA614E606E49[ at ]microsoft.com...
[Quoted Text] > Does the VSS service need to run at all if I am not using ntbackup? The
> description of the service states "Provides the interface to
> backup/restore
> Windows Internal Database through the Windows VSS". In this instance, I
> am
> talking about 60 stations at most. If I had to do a fresh installation of
> WSUS for a recovery, I could deal with that.
I don't think it's so much a function of which backup utility you're using,
but whether that backup utility is VSS aware and can use the VSS service.
It just happens that I know that NTBackup is VSS aware. There are likely
others, like, perhaps, Backup Exec v11. <g>
--
Lawrence Garvin, M.S., MCTS, MCP
Independent WSUS Evangelist
MVP-Software Distribution (2005-2007)
https://mvp.support.microsoft.com/profile=30E00990-8F1D-4774-BD62-D095EB07B36E
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, almost everything else is at
http://wsusinfo.onsitechsolutions.com
.....
|
|
Hi,
I also have similar problem with 10d, SBS2003 SP1, after upgrading WSUS 3.
I did not understand what is the final solution. Is it stopping SQL Server
VSS Writer?
If yes, is it going to effect WSUS or somthing else working properly?
Thanks,
Faruk
PS: For info my error is:
0xe000848c - Unable to attach to a resource. Make sure that all selected
resources exist and are online, and then try again.
Unable to attach to <myserver>\WSUS
"Lawrence Garvin (MVP)" wrote:
[Quoted Text]
|
|
|
|
Hi, thanks for your suggestions.
I've stopped "SQL Server VSS Writer", and tried 2 days, but backup failed.
Do you have any other suggestions?
(0xe000848c - Unable to attach to a resource. Make sure that all selected
resources exist and are online, and then try again.
Unable to attach to <myserver>\WSUS)
FA
"Lawrence Garvin (MVP)" wrote:
[Quoted Text]
|
|
|
|
Have you tried BackupExec 11 with the SQL agent? If the database is
online with BackupExec you should use the SQL agent for backups or
schedule dump files and just do normal file system backups.
|
|
|