Home / user-22840

rvf's questions

Martin Hope
rvf
Asked: 2014-03-12 07:45:08 +0800 CST
  • 1

I am trying to migrate individual users, one at a time, from an Exim based mail system to an Exchange 2010 system. I'm hoping to do this by leaving the Exim based system as the MX for the time being, and as a user mailbox is created on the Exchange system, then a manualroute rule is created for that user on the exim system, so that any mail addressed to them from both local and remote senders is delivered to the Exchange mailbox instead.

My experience with Exim is limited, but it appears that the manual routing rules I've seen thus far are domain based, but these addresses (on the Exchange and Exim systems) will have the same domains, so I'm hoping that I can route based on specific email addresses. What would be the best way to go about this?

email
Martin Hope
rvf
Asked: 2012-03-20 11:17:06 +0800 CST
  • 1

I recently had an LPAR on a Power7 system seemingly run out of memory. While it was up, I was unable to run any commands, so I was forced to perform an OS restart. It's minimum, desired, and maximum memory allocations are 8GB, 16GB, and 32GB, respectively. Is there some record of of the full 32GB (or whatever was available) being allocated to this LPAR after it exhausted the available 16GB?

Aside from merely wanting the reassurance that indeed did happen, knowing an exact time this happened would be useful in troubleshooting.

memory aix
Martin Hope
rvf
Asked: 2011-07-28 07:20:59 +0800 CST
  • 1

I have a small SRM recovery plan for a few "core services" VMs on an EqualLogic unit replicating between two data centers. I'd like to perform some planned, temporary failovers to keep these VMs available in the case of power outages, switch upgrades, etc.

One idea I had was to change my Network mappings in my recovery plan to go to actual networks, rather than the test bubble switch that's the default. I would manuall shut down the production VMs, run a test failover for the period of the outage, then end the test and power back up the production VMs. This seems a little messy, but I believe it would work.

The above idea seems a little messy, so I also considered running the actual recovery plan. Since I have never had to run the actual recovery plan, I am a little wary of what will change when I do. Is failing back as simple as shutting down the VMs on the recovery side and powering up the VMs on the protected side? This would be for a short period, so I'm not really concerned about any data changes on the VM during the failover.

Apologies if my question isn't really clear. I essentially want to failover for a brief period (one hour), and then simply power down the failover VMs and resume things as they were before the failover - I don't care about failback in terms of storage changes, etc.

vmware-esx failover vmware-srm
Martin Hope
rvf
Asked: 2010-08-31 13:55:00 +0800 CST
  • 2

I added three new drives to a Dell 2950 (running RHEL 5) with a PERC 6/i storage controller. The machine was previously running RAID 1 on two drives + hotswap. Rather than create an identical RAID 1 array with the new drives, I opted to gain additional storage by using OpenManage to convert the original Virtual Drive to a RAID 5 array that incorporated the new drives.

All of the above went off without a problem, but when I try to create a new partition with the additional space, fdisk informs me that there are "No free sectors available", even though it seems to recognize the additional space.

My current filesystem usage:

[root@local ~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/sda2             9.7G  2.1G  7.1G  23% /
/dev/sda1             487M   35M  427M   8% /boot
none                  4.0G     0  4.0G   0% /dev/shm
/dev/sda3             487M   11M  451M   3% /tmp
/dev/sda5             4.9G  1.2G  3.5G  25% /usr
/dev/mapper/VarGroup-var
                      50G  757M   47G   2% /var

fdisk output, showing additional disk space:

[root@local ~]# fdisk -l

Disk /dev/sda: 290.9 GB, 290984034304 bytes
255 heads, 63 sectors/track, 35376 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          64      514048+  83  Linux
/dev/sda2              65        1339    10241437+  83  Linux
/dev/sda3            1340        1403      514080   83  Linux
/dev/sda4            1404        8844    59769832+   5  Extended
/dev/sda5            1404        2040     5116671   83  Linux
/dev/sda6            2041        2301     2096451   82  Linux swap
/dev/sda7            2302        8844    52556616   8e  Linux LVM

Is there any way to incorporate the additional disk space without destructive repartitioning?

linux raid fdisk