Archive for August, 2007

GroupWise Quirks

August 24th, 2007

Hell week(s) are almost upon us. As part of my summer project list, I had to recreate post offices on newly created servers. Instead of moving existing post offices, I just removed the student post offices and the related domain. The domain name didn’t fit our naming convention, so in a fit of me being anal for once in my life, I decided to make the change. During the install(s), I ran into a few issues:

  • Post office and domain directories don’t like to be bigger than 8 characters. Guys, it’s 2007, let’s leave the 8×3 restrictions back in the 80s when they really mattered.
  • You can’t modify links for a secondary domain unless you’re connected to that secondary domain. Uh…
  • Speaking of link configuration, edit/save to save your changes? Who decided to go against 20 years of pseudo menu standards and do that one?
  • The domain install procedure kicked back an error from Console1. That error read “null”. Ok, I know exactly what that is.
  • The PO install procedure neglected to copy the *.dc files into the directory structure. Easy enough fix, but should I have to manually copy these files in?

Ok, that’s enough whining for right now. Bonsai has some admin tool updates apparently. Hopefully some of them address these strange and sometimes completely absurd quirks.

Edit save? I’m still shaking my head…

Backups == RAGE

August 9th, 2007

I finally took a leap of faith and rebuilt part of the backup system. When I set it the first time around, I carved the MSA20 drive arrary into two logical RAID devices and in turn two logical drives on the Windows 2003 box it is directly attached to.

We use Backupexec 10 and I set up 36 or so B2D devices for each backup job, per day, per server to be backed up, all full backup jobs. I did this for ease of restore over efficiency. Due to the more limited space restrictions, I had to move B2D devices all over the place to get proper backups. It wasn’t working for me.

I blew the entire drive array away and made one big RAID5 logical drive just to build a bit of fault tolerance into the setup. I also created three B2D policies per server. Every other Friday, a full backup will run. The other Fridays, a separate full backup will run. Monday through Thursday, incremental backups will span the gaps between fulls. This way, I’m hoping to have two full weeks of hot backups. I’m going to add automatic duplicate jobs to copy the full backups to tape so I can have off site backups. We’re not a 24×7 shop, so backups during the weekend are mostly redundant. If space ends up not being an issue, I’ll add incremental backups for Saturday and Sunday as well just to cover everything. If I have a flaw in this design, please feel free to leave a comment tell me what I’m off on and what you might do differently.

Finally, Backupexec for Windows is not NCS(Novell Cluster Services) aware. So because of this, I have to make sure that I know where my services are located. If I have a resource attached to a specific node, I need to keep it there when it comes time for the backup to run otherwise it will fail. This throws a small wrench into everything. I really wanted to keep the nodes and resources completely non dependent on each other, but that’s not going to work out.

Groupwise…

August 2nd, 2007

This is my third attempt at writing this. Wordpress keeps deciding to eat itself everytime I try to post this and I lose it. I figured I’d try to act smart and write this in OO.org writer before I try to save it here.

When GroupWise is running well, life is good, it’s a great product. When it goes bad, I curse its very existence. That’s a pretty generic comment that can be said for just about every piece of software short of the CD command.

GroupWise has some quirks that I’m slowly unearthing as I get deeper into my admin role with it. I just moved, after 2 hours of beating on it, a post office onto the cluster. My gripes come into play with the administration of the system. Console1 decided to continually crap itself while I was trying to edit the PO/POA objects. That’s obviously an isolated issue. However, when I tried to bring the PO online, something with the MTP settings was goofed, along with a message about restarting the agent for new settings to change. That didn’t work. I tried to rebuild the post office at that point.

I finally remembered that I need to be connected to the parent domain, which won’t necessarily be the primary domain depending on how your system is setup to run a rebuild. Once I finally sorted that out, I still couldn’t get the PO online. I finally commented everything out in the startup script aside from the home switch.

I guess my point to all this is, GroupWise has some strange quirks, held over from the “olden” days. It’s very modular, almost to a fault, but I guess that’s the price you have to pay for having an enterprise groupware package that you can span over multiple servers and multiple operating systems at the same time and have it work properly between all of them. There are a couple things I would like to see down the road. First, I’d like to see a proper management tool. Console1 is usable, but it leaves a lot to be desired. It can be crippled if your java virtual machine is having issues, which java Vms always seem to have. Also, I’d like to see better errors in the console/logs. “The post office must be restarted…” is a pretty vague phrase and only adds to what can be a needle in a haystack problem finding excursion. On the flip side though, I don’t have to deal with Exchange and Active Directory, so life’s not all bad!

Also, a bit off topic, but if you’ve tried OpenSuse and it’s been painfully slow you might want to try a different package manager. Run top from a bash prompt and see if updater-helper or something along those lines is eating CPU cycles. If it is chances are it’s the default package manager in OpenSuse, ZMD, spinning its wheels and seemingly doing nothing. OpenSuse is supposed to dump ZMD in version 10.3, but why wait for the rush. Dumping ZMD has turned my laptop from almost unusable to almost zippy. Not too bad for a laptop that has been my trusty workhorse for 4+ years.

Wordpress problems

August 2nd, 2007

I’m having a ton of issues trying to post anything longer than a couple small paragraphs. For some reason, wordpress decides to take a dive every time I post something of any length. It decides I no longer have access to /wp-admin/post.php, which is incorrect.

I hate blog software.

Edit: For some reason, I’ve tracked down that wordpress doesn’t like this text string:

But wait, system maintenance wasn’t an option I could select.

Thank god for annoying web 2.0 java script that shouldn’t even care what I’m typing in a text box. Moreover, thank god for a web 2.0 java script that lets me post the string in one article and not another.