Saturday, April 25, 2009

BESR cloning not exact.

I've been bit a couple times thinking that cloning a machine using Backup Exec System Recovery would give me an exact copy. This is probably the case if you do a straight recovery on the same hardware but when you recover checking off the option that this is different hardware, you get a minisetup from microsoft on first boot so that it can find and load the new device drivers.

I couple of things different on these clones that I've found:

1. If you had any secondary IP addresses on the network card, you need to re-add them

2. If you Data Execution Protection settings, they appeared to be changed. I had to re-add the applications that were listed before cloning.

Tuesday, April 21, 2009

Dell PowerEdge Perc 6 Alerts

Ok. What is it with Dell Perc controllers? The Perc 5 came with the Audible Alert disabled and unusable. Why would we not want to have all possible means of knowing if a drive goes down in the RAID? With Perc 6, still no audible alerts. Not only this, but it has been a hassle to get some sort of notification...especially email.

In the DRAC cards, we can get email for all sorts of alerts. For one of the most common failure in servers - hard drive failure - NO.

Version 5.5.0 of the Dell Server Administrator program, we can finally get alerts easily for virtual drive warnings and failures..Can we get an email alert....still NO. You can get a broadcast message sent out (this only goes to local network), a console alert?.(I'm hardly ever at the console since my servers are over 2K miles away from me..I'm usually in an RDP session), or execute an application.

SO I used bmail.exe which is a simple command line app that will send SMTP email to our SMTP server. Here's my cmd file with the names and IPs changed to protect the innocent.


REM This is called via the Dell System Administrator in case of storage alerts
REM using bmail to send logs via email to the recipients listed in toaddress
REM when calling email.cmd, use first parameter "%1" as subject
REM use second paramater as full path to log file then alter command line to include -m "%2".

SET SMTP="10.2.2.33"
SET toaddress="jrd@ntwc.com,alert@mj.com"
SET fromaddress="MJWDM@mj.com"

c:\bmail\bmail -s %SMTP% -t %toaddress% -f %fromaddress% -h -a "%1"


SMTP is the IP of the SMTP server that will allow you to relay.. ..so this is of course a local SMTP server. toaddress is a comma-delimited text with the email recipients. Fromaddress I usually create bogus email address with the domain name of the client and the name of the server sending the alert.

So I store this as email.cmd in C:\bmail folder along with the bmail.exe. Then under Server administrator under Alert Management, I set each to Execute Application. For example for a Virtual Disk Warning, the command line would be

c:\bmail\email.cmd "VirtualDiskWarning"


The email will now have the subject of "VirtualDiskWarning" I can't use spaces for some reason..not interested in troubleshooting that.

Be aware if you are interested in creating a vbs script, you have to encapsulate it in a cmd.exe command line...see Dell's manual for details.

DocsOpen 4.0 adding Parent doc type

We added a parent document type table and made Document Type table the child. The client is reorganizing there 100+ document types in a heirarchy in preparation to move to DM 5 and to use the Designer Folder views feature of that product. They don't want to see 100+ folders under their matter folder when they switch.

Created the parent doc type table and altered all the profile search screens and maintenance screens.

Need to put the old doc types under a parent doc type so created an 1_OLD parent document type (the "1_" so it will be listed first in a lookup). Looked up the SYSTEM_ID of the 1_OLD parent document type and used this SQL command in SQL analyzer

update docsadm.documenttypes set PAR_DOC_LINK = '295778' WHERE PAR_DOC_LINK is null

to change all the old document types so they will be children of this parent document type.