thinkdreams's questions

We are planning to move our Exchange DB to an EMC SAN (NS-120) with plenty of drive space from our 2007 Exchange server native storage which is getting low on space but not critically low on space (yet).

From what I can find online, a 79Gb Exchange DB is estimated to take roughly 6 to 7 hours. Does anyone concur with this estimate?

I'm prepared to be offline for the time since the DB is dismounted, but I wanted to a rough idea of what to shoot for since I'll be doing it on a weekend between backup windows.

I have a development ERP server here in my office that I assist with support on, and originally the DBA requested a single drive setup for some of the drives on the server. Thus the hardware RAID controller (an HP embedded controller) looks like:

• c0d0 (2 drive) RAID-1
• c0d1 (2 drive) RAID-1
• c0d2 (1 drive) No RAID <-- Failed
• c0d3 (1 drive) No RAID
• c0d4 (1 drive) No RAID
• c0d5 (1 drive) No RAID

c0d2 has failed. I replaced the drive immediately with a spare using the hot-swap, but the c0d2 continues to mark itself as failed, even when I umount the partition. I'm loathe to reboot the server since I'm concerned about the server coming back up in rescue mode but I'm afraid that's the only way to get the system to re-read the drive. I assumed there was some sort of auto-detection routine for this, but I haven't been able to figure out the proper procedure.

I have installed the HP ACU CLI utilties, so I can see the hardware RAID setup.

I'd really like to find out what the proper procedure should have been, where I went wrong, and how to correct it now.

Obviously this goes without saying I should NOT have listened to the DBA and set the drives up as RAID-1 throughout as was my first instinct. He wasn't worried about data loss, but it sure would have been easier to replace the failed drive. :)

I'm having a "lively" debate with a work associate about the reasons for or against using DHCP on servers in a network environment. The network environment in particular is a relatively small network, but in my experience it's always better to have servers on static addresses, especially for things like remote management, etc.

I looked, and could find any specific reasons for or against dynamic addresses assigned on servers so I figured I'd ask the crowd here.

My work associate argues for DHCP assigned server addresses for ease of management, and states if the addresses ever change you don't have to change the server IP manually. I'm dubious about this response.

For management purposes, this network being small, it's no big deal to change the IP of static devices since there's so few.

Any suggestions, ideas or comments?

I am setting up a set of scan folders from a scanning copier device, and would like to know the best way to protect the folders (for each department) from moving or deletion, but yet still allow access for the users to modify (i.e. create/add/delete) the scanned files within the folder.

Structure is: Share Name > Departmental Folder > User files

The writing of the files initially is taken care of by a service account which has full control. We'd just like to ensure the users cannot accidentally delete the folder (which has already happened) containing all the files, etc.

This is for a Windows 2003 server, NTFS permissions.

Suggestions would be most appreciated.

OK, one would think this would be an easy question to answer. But searching online yields no results to our particular issue. We have Cisco WAPs that require configuration to broadcast the SSID of our private network. We already have a guest SSID, which is being broadcasted, and we have VLANs all set up on these devices. They are all working currently, we just need to broadcast the private SSID as well as the Guest SSID.

Why can't I find the commands or configuration options to turn broadcasting on? It's not obvious in the GUI, and the command line configuration is not obvious either. I know it's something simple.

Anyone got any ideas? If you need more information, please let me know.