Help! WSUS Replica server out of space
Lionel
My replica server is out of space, how to win space. Last week 23/30Gb used
and after a automatique synch this week end, i'm out of space!
1) The parent server use for corporate many language, I need only English
and French. Possible to remove unused language ?
2) I tried WSUSutil
C:\Program Files\Update Services\Tools>WSUSutil.exe deleteunneededrevisions
Database cleanup is in progress, please be patient
Database cleanup encountered an error, please check your server and try again
Fatal Error: The log file for database 'SUSDB' is full. Back up the
transaction
log for the database to free up some log space.
Thanks in advance
Lawrence Garvin (MVP)
news:4525317C-A093-4B16...@microsoft.com...
> Hi,
>
> My replica server is out of space, how to win space. Last week 23/30Gb
> used
> and after a automatique synch this week end, i'm out of space!
>
> 1) The parent server use for corporate many language, I need only English
> and French. Possible to remove unused language ?
No.
Replica servers are exact /replicas/ of their parent server. If you need
only English and French on this server, and you have all languages on the
parent server, then /replica/ servers are not the type of downstream servers
you need to configure.
Only option is to reinstall the downstream server as an autonomous
downstream server, configure it to synchronize only English and French, and
point it to the upstream server (or microsoft.com) to obtain metadata and
updates. You'll then need to approve updates at this downstream server.
--
Lawrence Garvin, M.S., MVP-Software Distribution
Everything you need for WSUS is at
http://technet2.microsoft.com/windowsserver/en/technologies/featured/wsus/default.mspx
And, everything else is at
http://wsusinfo.onsitechsolutions.com
....
Lionel
reinstall ?
In case of continue to be a replica and the parent server used all language,
what can be the recommend Hard disk size for the content folder ? (150 Gb ok?)
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
Lawrence Garvin (MVP)
> Thanks, but can I modif my server to be autonomous witout a complete
> reinstall ?
No. The only way to convert to/from replica mode operation is by
uninstalling/reinstalling the server.
> In case of continue to be a replica and the parent server used all
> language,
> what can be the recommend Hard disk size for the content folder ? (150 Gb
> ok?)
The recommended hard disk size for the replica is the same amount of disk
space being consumed by the parent server.
The disk space needed by the parent server with all languages and all
updates is probably approaching a couple hundred GB now. I don't know of any
installations that have all languages/all products/all classifications
selected, and if I did, I'd probably be recommending ways to split that
environment up into two parallel systems.
David Gibbons
also "clean up" the replicas?
Thanks
David.
"Lawrence Garvin (MVP)" <onsi...@news.postalias> wrote in message
news:e70xf1d4...@TK2MSFTNGP05.phx.gbl...
Lawrence Garvin (MVP)
news:ubhbduK6...@TK2MSFTNGP05.phx.gbl...
> If I decline the update and then run cleanup on the parent server will is
> also "clean up" the replicas?
No.
In addition, you need to be VERY careful with the procedure you use to do
disk maintenance on replica servers. This is an enhanced version of a
procedure I wrote and posted here last March. I've not received any negative
feedback on the procedure; but I've also not personally tested it, so use it
at your own risk.
(1) Set all servers to manual synchronization.
(2) Synchronize the master server with microsoft.com.
(3) When the master server has finished synchronizing, synchronize all
replica servers and ensure they have successfully synchronized and
downloaded any needed content from the master server.
(4) Run 'removeunneededrevisions' (if desired), and then mark updates to be
purged as "Declined".
(5) At each replica server, synchronize with the master server to pick up
the metadata modifications.
(6) When the replica server has finished synchronizing (which will include
the updates now marked as "Declined"), as well as synchronizing for
revisions to be removed, and have downloaded any needed content, then run
the PurgeUnneededFiles on the replica server. (You cannot run
'removeunneededrevisions' on the replica servers, as the metadata on a
replica server cannot be "managed".)
(7) After all replica servers have been synchronized, fully downloaded, and
purged, then you can run PurgeUnneededFiles on the master server.
(8) Reset the master server to automatic synchronization. (You might also
want to run a manual synchronization if you missed a scheduled
synchronization during this purge process.)
(9) Reset the replica servers to automatic synchronization.
Lionel
To solve the proble, I have now
- Uninstall the WSUS srv
- Reinstall WSUS in autonomous mode
- Select the only the two needed languages
- Point to the Parent server for the synch.
Lionel.
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
Lionel
To finaly solve the problem, I have:
- Unsinstall WSUS
- Reinstall WSUS in autonome mode
- Select the two needed language
- Point to the parent server for synch
Lionel.
"Lawrence Garvin (MVP)" wrote:
> .....
>
>
>
David Gibbons
I'm not too sure what kind of access you have with the WSUS team but this is
not a very easy thing for me to do. I have over 100 WSUS replicas. Yeah,
that's not a typo 100. And yeah, I need that may replicas because I manage
so many systems on low speed WAN links. So I have to hit all the servers
one at a time in order to manage the content data. I'm going to try and
script it but this is still kindof an issue.
Suggestion or wishlist - Add the purge functionality to the WSUS interface
and allow the replica systems to follow the parent.
*gets coffee, going to be here awhile*
Thanks for the info.
David.
"Lawrence Garvin (MVP)" <onsi...@news.postalias> wrote in message
news:%23dndJOP...@TK2MSFTNGP03.phx.gbl...
Lawrence Garvin (MVP)
"David Gibbons" <FreR...@nospam.postalias> wrote in message
> I'm not too sure what kind of access you have with the WSUS team but this
> is not a very easy thing for me to do. I have over 100 WSUS replicas.
Really!!??
> And yeah, I need that many replicas because I manage so many systems on
> low speed WAN links.
Maybe you do, maybe you don't! :-)
In reality, unless you have less than 5kb/sec of bandwidth per PC at your
remote sites, you probably do not need a remote WSUS replica server.
See this article for some insight on what you can actually do with remote
clients, a central WSUS server, and just a little bit of bandwidth:
How do I distribute XP SP2 to 1000+ clients using WSUS?
http://wsusinfo.onsitechsolutions.com/articles/036.htm
> So I have to hit all the servers one at a time in order to manage the
> content data.
You are not required to perform disk maintenance of any sort on any WSUS
server.
But /IF/ you wish to perform disk maintenance on a /replica/ server, it's
critically important that the replica server is fully updated from the
master server -and- the master server does not synchronize with
Microsoft.com before both systems have had disk maintenance performed.
More significantly, it is critical that ALL replica servers are fully
synchronized (including downloading content) with the master server, before
you begin a purge of any content from the master server.
> Suggestion or wishlist - Add the purge functionality to the WSUS interface
> and allow the replica systems to follow the parent.
See WSUS v3.0 beta for these type of enhanced features. :-)