General discussion

Locked

Forcing a 3.2 server to "down"?

By jim.walker ·
Is there a way to force a Novell 3.2 server to down? I try and reboot the server after every backup session, so I regain some of the memory. Netware won't go down by itself (without user intervention) if either of these two conditions are present:

1. Open files
2. Print Queue files that have data (usually caused by a printer running out of paper).

Does anyone know how to get around this limitation?

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Forcing a 3.2 server to "down"?

by jpt In reply to Forcing a 3.2 server to " ...

Yes !
You can execute a NCF file in the end of your backup. Be sure to start with the command :
CLEAR STATION ALL ( to disconnect all user and printers )
A NCF file can look like this:

CLEAR STATION ALL
REMOVE DOS
DOWN
EXIT

Or like this

CLEAR STATION ALL
DOWN
RESTART

The first one is for rebooting the server and the second one is for restarting SERVER.EXE.

Remember to hit Return on the keyboard in the end of both files if not it wont work.

John

Collapse -

Forcing a 3.2 server to "down"?

by jim.walker In reply to Forcing a 3.2 server to " ...

Poster rated this answer

Collapse -

Forcing a 3.2 server to "down"?

by rogerndgreen In reply to Forcing a 3.2 server to " ...

The first answer will work, but another option is to use the management software for your UPS (you do HAVE a UPS?)
Most of my experience has been with APC kit & Powerchute. You can use this to schedule a shutdown/reboot whenever you want.
For what it's worth though, why do you need to reboot your server after every backup? Netware fine-tunes itself and is a lot happier being left alone (unlike NT!)to sort itself out. You will find this is even more relevant if you ever upgrade from the bindery-based 3.x and move into an NDS environment, as regular shutdown/restarts will cause unnecessary synchronization traffic.
I would look closely at your backup software & server config.
The last time I used a NW 3.x server, it was being backed up everyday, 200+ users through most of the day, kit was an old 486/33 base unit with add-in SCSI cards for disks & tapes, and it ran like a dream for 6 months plus, until I had to power it down because of building work (and I bet there are guys out there who can easily bost uptimes of more than a year).

Collapse -

Forcing a 3.2 server to "down"?

by jim.walker In reply to Forcing a 3.2 server to " ...

Poster rated this answer

Collapse -

Forcing a 3.2 server to "down"?

by jim.walker In reply to Forcing a 3.2 server to " ...

This question was closed by the author

Back to Networks Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums