That moving (not copying) a VMDK to a different folder on the same datastore actually takes time. And here I was thinking it would just relink the file to a new folder, but maybe I'm think too much about the filesystem?

I'm happy though, I get to consolidate a bunch of management software onto one server. Less VMs to deal with woo!

...that on the old, buggy release of DDOS in the 4.7.x range, the device may ignore FQDNs in the administrative station listing. IP will work just fine, just not the FQDN.

I figured that out, trying to get the durn /ddvar folder to mount so I could dump the updated release.

The updated release is necessary, because the durn clean wasn't working, so the file system filled up and wouldn't clear itself, after the data aging was run on the Commvault Simpana v8 setup, which apparently never had the data aging scheduled

So, I get the first upgrade done, have a good 70GB free and the upgrader says "not enough free space", which I take actually means not enough CONTIGUOUS free space or that it wants the clean to finish.

At least now the cleaning appears to actually be working. I should be able to recover a good 90% of the used space.

Then I can upgrade to the DDOS 5.x stream and allow for more web GUI based management (for my coworkers).

Then I can upgrade to the DDOS 5.x stream and allow for more web GUI based management (for my coworkers).

Have you upgraded a box to DDOS 5.x yet?

If not, I will save you from a heart attack.. During the upgrade, it is perfectly normal and expected (although not well documented) that the filesystem will be listed as "DESTROYED" in giant red bad letters during parts of the upgrade.

No one warned us.. When we called and asked if our box was toast (before it finished and went back to happy) the EMC tech actually laughed at us.

Also if you run tight on space normally, there is some sort of snapshot that is made/kept as part of the upgrade. If you start running out of space support can get rid of it for you, I think it auto expires after a week or so but we needed to get rid of it early.

Uhh, did we break this topic? I can see the replies, when I click post reply, but I don't see the thread in the main forum anymore, and when I go to the thread(through my history) I only get the first page.

Halon or FE-13/FM200? Because if it's actually Halon that's an OLD system, new Halon systems weren't allowed past 12/31/1993 and no new Halon 1301 production was allowed past that date so almost everyone has converted as it's been extremely expensive to get.

One of our "facilities" guys was working on an air handler in our "datacenter". Tripped the halon, then decided to take a break.

The timer counted off, the alarm was muffled coming out of the room, so nobody paid attention. I walked around the corner to see what the hell was going on, only to see the room.......and then NOT see the room, through the windows. It went full whiteout in about 4 seconds. Then the main building fire alarm was pulled and we evacuated the building.

Brightside: Our production stuff is offsite. Looks like we'll be moving dev offsite too. New gear is cool.

Not so brightside: They were close to reclaiming half the floor space for desks and cubicles. This would have been a goddamn tragedy.

Halon or FE-13/FM200? Because if it's actually Halon that's an OLD system, new Halon systems weren't allowed past 12/31/1993 and no new Halon 1301 production was allowed past that date so almost everyone has converted as it's been extremely expensive to get.

Halon 1301. The tanks are empty. We will probably not replace the suppression system and "move*" all the gear offsite.

Someone tripping a full DC system where people are sitting... yikes. Would have been extremely bad.

As part of our SOX controls, you can't even get access to our DCs without undergoing fire suppression training. It largely consists of "Here is the gear...don't fucking touch it. Ever. If you hear a loud whooshing noise, run for the door. Also, don't stay in here any longer than absolutely necessary."