> From: [email protected] [mailto:[email protected]] On
>
> Document procedures, passwords, settings and details which a competent
I'd like to go into more detail on that:
procedures/backup-and-restore/laptops
procedures/backup-and-restore/servers
procedures/backup-and-restore/etc
procedures/install-and-configure/compute servers
(so somebody can build another compute server like these)
procedures/install-and-configure/AD servers
(so somebody can build another AD server like this)
procedures/install-and-configure/file servers
procedures/install-and-configure/switches
procedures/install-and-configure/etc
procedures/users-add
procedures/users-remove
procedures/order-of-startup
procedures/order-of-shutdown
passwords-and-contacts/internal/root
passwords-and-contacts/internal/administrator
passwords-and-contacts/internal/db admin
passwords-and-contacts/internal/cisco enable
passwords-and-contacts/internal/etc
passwords-and-contacts/dell
passwords-and-contacts/apple
passwords-and-contacts/oracle
passwords-and-contacts/etc
inventory/expirations
(dates of licenses, support contracts, etc)
inventory/equipment list and serial numbers
inventory/software licenses
architecture/network diagrams
architecture/server docs, etc.
architecture/power requirements
(details below)
About power requirements: I'm probably the only person who does this, but I
find it enormously valuable. Every new piece of hardware (or at least every
new *type* of hardware) while building it, I measure the power draw with
kill-a-watt. It's typically around 25% of what the mfgr says. Having all
this information allows you to right-size your UPS and AC. Most people
simply overprovision. Or, I've certainly seen places that underprovisioned
and ended up with outages because of it.
_______________________________________________
Discuss mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
