What the heck is a FLYbaby?
Ok, I will finally admit it outloud. . I am not organized, and organization does not come to me naturally. Not only I am not natively organized, I have almost no routines and usually avoid them at all cost. So, it comes as no suprise to most that I don't exactly have a perfectly clean home that my family can't wait to get home to. I was not taught how to clean by habit and routine, and therefore, when company is coming, it is usually a several day ordeal that contains much hollering and lots of stress.
Last week, I realized that not only was my house disorganized and not clean, but my house really was only a reflection of the chaos I had accepted in all areas of my life. I was also at a loss as to how I was going to encourage my ds (dear son) to care about school and get himself together. So I did what I always do when I am in a crisis and need advice, I used google.
The first sites I happened across were reform schools and places for troubled teens. Knowing that things were bad, but not quite that bad yet, I kept going. I somehow ended up on a funny little page with a woman in purple wings and blue hair at www.flylady.net. I won't bore you with all the details, but I highly recommmend this site for any woman who may be a perfectionist, works at home or outside somewhere, and is feeling like perhaps things in your life are out of control and you can't organize yourself.
Once I decided to become a FLYbaby, the only natural next step was to organize the second most important thing in my family's life (the house being the first), dinner! I have only begun to use some of the tools posted on the Saving Dinner site.
I can't tell you what to do, and I am sure this system is not for everyone, but I think it is no coincidence that I had my first really good idea for a story today. . .one week into the new lifestyle!
Friday, September 21, 2007
Thursday, September 20, 2007
Backup Exec, Mac Troubles, and Exchange Size Limit
Backup Exec
I have spent a couple of pretty darn frustrating days trying to figure out what in the world happened to one of my servers to make my backups stop working. I am using Backup Exec 9 with an internal tape drive on one server to backup files on another server. Suddenly, and without warning, my backups started failing. I tried everything I could think of, including Symantec's advice of redoing the login admin account. Nothing. So what had changed? Well, I had installed IIS to beging testing VMWare on that box, so ok, I figured uninstalling IIS couldn't hurt. Reboot. . .Nothing. I tried every iteration of backup, incrementals, differentials, copies. . .Nothing. Noticed VMWare had added some network adapters, so I figured what the heck, may as well disable them while I am thinking of it and at that moment happened to realize that the windows firewall was turned on for my main nic. . .odd. . .I don't remember that being on. I decided to look at my other nics on my other servers, and sure enough, it wasn't turned on anywhere else. Of course. . .rebooted. . wallah. . backups working!! ARRRGGGGHHHH!!!
Macs too
In addition to backup fun, I have been helping one of the graphics guys get his new Mac Pro up and running. I don't think that there is too much I want or need to say about that. We also did some Webway work/tweeking while we were at it, and I do want to note that we had some minor issues with viewing proofs that seem to have something to do with login accounts and permissions. ALSO TO NOTE: As the admin down south suggested, I have removed the oldes mac from the network and will now monitor the switch in the Graphics room.
Exchange Note
I did notice yesterday, while I was checking all the server logs to see what had changed, that we were getting a warning on the Exchange Server that we were running into out 18 GB size limit for our DB. A quick note the admin down south confirmed that this needed to be fixed. He said he changed a registry setting to give us 70 GB and that the MS limit was actually 75 GB, so we had some wiggle room if we do get close to the edge. Another registry fix would allow us to continue working long enough to have folks delete much and be operational once again.
I have spent a couple of pretty darn frustrating days trying to figure out what in the world happened to one of my servers to make my backups stop working. I am using Backup Exec 9 with an internal tape drive on one server to backup files on another server. Suddenly, and without warning, my backups started failing. I tried everything I could think of, including Symantec's advice of redoing the login admin account. Nothing. So what had changed? Well, I had installed IIS to beging testing VMWare on that box, so ok, I figured uninstalling IIS couldn't hurt. Reboot. . .Nothing. I tried every iteration of backup, incrementals, differentials, copies. . .Nothing. Noticed VMWare had added some network adapters, so I figured what the heck, may as well disable them while I am thinking of it and at that moment happened to realize that the windows firewall was turned on for my main nic. . .odd. . .I don't remember that being on. I decided to look at my other nics on my other servers, and sure enough, it wasn't turned on anywhere else. Of course. . .rebooted. . wallah. . backups working!! ARRRGGGGHHHH!!!
Macs too
In addition to backup fun, I have been helping one of the graphics guys get his new Mac Pro up and running. I don't think that there is too much I want or need to say about that. We also did some Webway work/tweeking while we were at it, and I do want to note that we had some minor issues with viewing proofs that seem to have something to do with login accounts and permissions. ALSO TO NOTE: As the admin down south suggested, I have removed the oldes mac from the network and will now monitor the switch in the Graphics room.
Exchange Note
I did notice yesterday, while I was checking all the server logs to see what had changed, that we were getting a warning on the Exchange Server that we were running into out 18 GB size limit for our DB. A quick note the admin down south confirmed that this needed to be fixed. He said he changed a registry setting to give us 70 GB and that the MS limit was actually 75 GB, so we had some wiggle room if we do get close to the edge. Another registry fix would allow us to continue working long enough to have folks delete much and be operational once again.
Subscribe to:
Posts (Atom)
