Posts

EMC VNXe BUG WHEN CHANGING REPLICATION IP ADDRESSES

I worked with EMC support recently to identify and work around an apparent bug in the VNXe operating environment. One of our customers purchased two VNXe 3100’s with the intention of using them to replicate CIFS data between two sites. Because the data exceeds a terabyte we placed both VNXe’s in the customer’s primary datacenter to perform the initial data migration and synchronization. Once the initial sync between the VNXe arrays completed we relocated the secondary VNXe to one of the customer’s offices a couple of hours away.

Changing the management IP address of the VNXe that had moved to match the subnet at the new location was no problem, but there seemed to be no way to successfully change the IP address used by the replication interface and reestablish the replication session.

We opened a support case with EMC, who after some digging acknowledged that we had encountered an issue that will be corrected in the next VNXe OE release.

If you find yourself unable to change the IP address of a replication interface on a VNXe storage array the work-around is to contact EMC support and let them reconfigure the replication for you.

VEEAM Error – Freezing guest operating system CreateSnapshot failed, vmRef “*”, timeout “1800000”, snName “VEEAM BACKUP TEMPORARY SNAPSHOT”, snDescription “Please do not delete this snapshot. It is being used by Veeam Backup.”, memory “False”, quiesce “False” File is larger than the maximum size supported by datastore ‘

Sorry for the extremely long blog title, but this is an error that I have come across recently, and wanted to share the solution.

Freezing guest operating system
CreateSnapshot failed, vmRef “*”, timeout “1800000”, snName “VEEAM BACKUP TEMPORARY SNAPSHOT”, snDescription “Please do not delete this snapshot. It is being used by Veeam Backup.”, memory “False”, quiesce “False”
File <unspecified filename> is larger than the maximum size supported by datastore ‘<unspecified datastore>

The solution is actually to move the configuration files from from a datastore that has a lower block size (2MB or 4MB) to a datastore with a larger block size.  This is due to the fact that the expansion of the data during the backup process.

GROUP POLICY MANAGEMENT ERROR & HOW TO FIX IT

If you ever run across the following error in Group Policy Management:

An error occurred while generating report:
An unknown error occurred while the HTML report was being created.

The follow these steps to fix it.

1. Open the Group Policy Management
2. Go to the Group Policy Object in question, and confirm you have the issue by selecting the “Settings” tab
3. At this point, if you have the issue, the left hand side should read the above mention error
4. Edit the GPO, and browse to User Configuration > Windows Settings > Internet Explorer Maintenance > Security > Security Zones and Content Ratings
5. Change the setting from “Import the current security zones and privacy settings” to “Do not customize security zones and privacy”, then exit out of the GPO editor
6. Close Group Policy Management MMC, then reopen it
7. Go back to the GPO in question and click the “Settings” tab

This time your GPO Settings Report should run properly.

Error when setting up Outlook 2007: “The name could not be resolved. The action could not be completed.”

If you ever run into issue while attempting to setup Outlook for a user but you run into the following error: “The name could not be resolved. The action could not be completed”

Be sure to check Active Directory replication (Sites and Services). If you notice that you are unsuccessful when manually replicating you more than likely have found your issue. Rebooting the Domain Controller experiencing the replication issues was the fix for me.

Replication Error 2108

Replication Error 2108

You might find it helpful for you as well.