The Exchange team again deliver more goodness with rollup 2 for SP1, if you use a CAS array and move a mailbox from one Database to another Outlook clients will no longer get the message
“The Exchange administrator has made a change that requires you quit and restart Outlook.”
more info on the Exchange Team blog.
Updated to reflect Duncan’s comments below…
VMware HA Clusters that have hosts spanning sites or where more than one node can be isolated from the other nodes, may not trigger an HA isolation event when nodes still receive a heartbeat from at leastone only node in the same Cluster.
Primaries nodes send heartbeats to primaries and secondaries, secondary nodes send heartbeats only to primaries. (quote from Duncan’s HA Deepdive book)
An isolation response will only be triggered if and when the following two requirements are met:
– Heartbeats have not been received from ANY host in the cluster, whether primary or secondary
– The Isolation Address cannot be pinged
Only in this case will a Host (primary or secondary node is irrelevant) trigger the isolation response.
When hosts are split like this, they do not attempt to make contact with the isolation address and do not shut down or power off VM’s, as they aren’t isolated. The Failover Coordinator, a randomly selected Primary node will attempt to power on the VM’s but this will fail as the files will be locked as those VM’s will still be running on the other Hosts split from the Failover Coordinator.
Therefore it’s better for ESX Clusters not to span sites to avoid this issue occurring.
Thanks to Michael Francis and Duncan Epping in confirming this information for me.
During an upgrade of a Cluster to vSphere 4.1 I have noticed the “Host hardware power status” alarm was not being triggered but the Hardware Status showed the sensor is was alerted. I was having this issue with Dell PowerEdge R710 and ESXi 4.1hosts and found this support article:
This is different Hardware and a different version of ESX than the kb artical but the issue is identical.
I resolved this issue by modifying the default alarm, adding new trigger conditions and using the trigger ‘objectName’ Starts with “Power”. I created warning, alert and normal triggers but left the default triggers alone. Once I did this and restored the power and waited 5 mins then triggering the power loss the alarm works.
I assume the default alarm trigger using the argument ‘group’ start with ‘power’ is not working correclty but the trigger ‘objectname’ does. This means it’s possible for other Hardware sensors starting with power to be trigger this alarm but currently there are no such sensors.
The Role Recipient Management is often given to Helpdesk and Support staff who need to be able to create, modify and disable recipients in Exchange 2010. One permission which this role does not grant and may be needed is the ability to modify the “Send as” attribute on recipients.
The Active Directory Permission Role allows this access and by default is part of the Role Group Organisation Management. This Role Group grants the member complete access to Exchange and it’s likely you don’t want to grant complete access to allow them to modify the “Send as” attribute.
Instead you can create a custom Role Group that includes the Roles from Recipient Management and the Active Directory Permission group (you can also define the OU to restrict the access to only recipients within that OU).
This is the process you can use to failover EMC MirrorView/S LUN’s presented to VMware ESX (3.0.2 old skool!)
1. Pick one a LUN/Datastore to perform cutover on.
2. Shutdown all the VM’s on that Datastore.
3. Remove all the VM’s on that Datastore from Virtual Centre inventory, right-click and remove.
4. Switch to Navisphere, Check mirror sync state = synchronized (right click on mirror, properties, secondary tab)
5. Expand Storage Groups, select Prod ESX host group, right click and properties, LUNs, note LUN ID, select LUNs and remove LUN from Storage Group.
6. Switch to VI Client, Select a DR Host, configuration, Storage adapters, Rescan Datastores.
7. Switch to Navisphere, expand Remote Mirrors, right click on secondary image and promote.
8. Switch to VI Client, select DR ESX host, Configuration tab, advanced, Set LVM.EnableResignature to 1 (required for ESX 3.0).
9. Switch to Navisphere, Add LUN to DR ESX host groups on DR CX, ensure the same host LUN ID is used
10. Switch to VI Client, Rescan ESX in DR with Enable resignature setting enabled, check LUN is found, if not rescan again and reboot if necessary.
11. Refresh storage on all hosts in cluster, ensuring old Datastore appears (without this you can do the next step and rename the snapshot).
12. Ensure Datastore appears on host where rescan was run, rename Datastore snap-000000X-datastore name to the old Datastore name(may not need to be renamed).
13. Browse Datastore and Add VM’s to inventory by right clicking on vmx files.
14. Power on VM, select to create new identifier (safest option but copies works too).
15. Turn off resignature on DR ESX host, Configuration, advanced, Set LVM.EnableResignature to 0.
These are a collect of pictures of the Flooding on Brisbane from the 11th to the 14th of Jan 2011
Pictures at 9:30am, 11/01/2011 on the end of Kurilpa Road, the park slowly going under.
Pictures an hour later, about 11am, 11/01/2011, the river is creeping up.
Pictures at 11:45am, 11/01/2011, still slowly rising
Pictures at 1:15pm, 11/01/2011
Pictures taken around 4pm, 11/01/2011
Pictures taken approx 7:00am, 12/01/2011
Bailey Street off Kurilpa Road
Top end of Kurilpa Road near the Montague Road corner
Pictures 11am, 12/01/2011, Top of Kurilpa Road near the Montague Road corner
Pictures 11.30am, 12/01/2011, Top of Kurilpa Road near the Montague Road corner
Pictures 5.30am, 13/01/2011, Top of Kurilpa Road, Corpnet office 365 Montague Road
Corner of Harriet Street and Monatgue Road
This afternoon a customer contacted me, they were not receiving inbound emails but Outlook and outbound emails were working. I happened to be across the road so I went over to have a look. The Mailbox Databases were still mounted, the Hub Transport Server queues had errors and the inbound emails were waiting delivery.
It seems that once disk space for logs and/or databases gets below 1Gb Exchange cuts off all transport delivery to that database using logs on that volmues, this is to try to prevent running out of space.
In previous versions of Exchange administrators could tell when Exchange ran out of space as the Database would go offline and the logs or database drive would be full. Now with Exchange 2010 if you stop receiving email and the free space is below 1GB, Exchange willl have stopped transport delivery, this allows users to continue to access their mailbox and send outbound email by leaving the Databases mounted.
Once the free space is increased to over 1.5GB email transport will resume.