Re: windows 2003 server run out of space

See below.

"Juliana" <Juliana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EF4D7082-96CF-484F-A14E-4FB62001588E@xxxxxxxxxxxxxxxx
Thank you so much for your response.

You are right, it was not a clean installation. On the server was
installed
windows 2K server before installed win2K3. And the folder "winNT" was
created for windows 2K. But the system seems is using the folder because I
can see the "system32" was unders "winnt" for example, and see some latest
updated files as well. Any suggestion that if winnt is useless at this
point?

Type set system at the Command Prompt. Does the response
include the c:\WinNT\System32 folder? If it does not, rename
c:\WinNT to WinNT.obsolete and see what happens. The action is
easily reversible. If all is well then delete the folder after a week.

It seems like I have to re-parition and re-install this server.

If you enjoy re-installing the server, go ahead. If your operation
is stable then use one of the methods I recommended in the
other thread to repartition the disk.

I'd like to know if I re-partition the hard drive and re-install the
win2K3
on the remote site server, DO I NEED TO backup the server? There is no
user
data yet on the server except system folders and Active Drectory acting a
backup domain controller at remote site for log-in service only. I assume
that the main AD keeps the copy of everything of user accounts and
workstation accounts and groups, etc. Once the new installed server
connect
to the main domain controll, it will replicate the AD copy on the newlly
installed server.

Sorry, I'm not an expert on this one.

Would you please let me know that if I can re-install the server without
restory from a backup?

You can but I urge you to try this on a spare disk BEFORE
repartitioning. Many people religiously back up their installation
but they fail to take ALL the necessery steps, i.e.
1. Create & run an appropriate backup job.
2. Perform a full restoration to a different disk.
3. Test this different disk.
4. Run the backup job daily or weekly.
5. Check the backup logs on a weekly basis.
6. Repeat Steps 2 and 3 twice a year.

Thanks again,

Juliana


"Pegasus (MVP)" wrote:


"Juliana" <Juliana@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3F7F3FB2-5861-4B67-9493-1AFF96673C15@xxxxxxxxxxxxxxxx
Help!!

I just find that one of server(win2k3 r2) run out of space. There are
two
subnets that each one with a domain controllers. The backup AD has two
folders (in the system partition) called "windows" and "winnt", with
1.8G
and
1.3G. The system partition has only 5G space was setup at
installation(I
did
not know so much space is going to be needed for file replication at
backup
AD), it's runing out space due to these two big folders.

The main domain controller is a win2k3 SP1. The AD holds about 60 user
accounts and 60 workstation accounts for both locations.

question 1--I do not know how the file replication serice works, is it
possible to reduce the amount of space taken at backup AD?

question 2--is there any way I can expanding system partition to big
size
without re-install in order to take these two big folders I mentioned
before?

Thank you in advanced.

The recommendation for WinXP Workstations is at least 10 GBytes
for the system partition, and 20 GBytes for a server, assuming that
user data is kept on a different partition. Since your system partition
is only 5 GBytes, no amount of tuning will get you back to a
sustainable operation. You must resize your partitions.

Have a look at the thread "Partitions out of Space", posted in
this newsgroup a little over 24 hours ago.

What is this WinNT folder? Some left-over from a failed
installation? Is it in use? Rename it and see what happens.





.

Relevant Pages

  • Re: Another disaster recovery exercise (but not yet)...
    ... and without a functional server for you customer. ... with a partition level backup and restore to different media. ... You are 100% sure that the previous installation of SBS 2000 was done by ...
    (microsoft.public.backoffice.smallbiz2000)
  • RE: Backup Problems
    ... follow the guide to implement the SBS integrated components installation. ... please run the CEICW wizard (server ... Then please run Backup Configuration Wizard to configure backup tasks ...
    (microsoft.public.windows.server.sbs)
  • Re: sbs 2003 disaster recovery best software
    ... to different hd, raid 1 to system partition C:, and so on, but I want to ... I want to this when the server is on and working, ... Please only tested solutions for SBS. ... replacements for backup, an image does speed system recovery ...
    (microsoft.public.windows.server.sbs)
  • Connection with server failed. Hit to retry. (Symantec Backup Exec SB 11d)
    ... I'm experiencing some issues with my installation of Symantec Backup ... Exec 11d, the Small Business edition. ... This has been newly installed on a new Dell server running Windows ...
    (microsoft.public.windows.server.sbs)
  • RE: Move initial Portal to new hardware
    ... You can use the SharePoint backup and restore tool that gets installed during ... the application installation. ... What you may have to do is backup the DB's ... What we did was backup the DB's in SQL; Restore them to the new SQL Server; ...
    (microsoft.public.sharepoint.portalserver)