SHIFT-WIKI - Sjoerd Hooft's InFormation Technology
This WIKI is my personal documentation blog. Please enjoy it and feel free to reach out through blue sky if you have a question, remark, improvement or observation. See below for the latest additions, or use the search or tags to browse for content.
SRM Alarms
Summary: How to configure alarms in VMware Site Recovery Manager 5.1.
Date: Around 2010
Refactor: 21 April 2025: Checked links and formatting.
Site Recovery Manager has the option to enable alarms, and have the alarms send to an email inbox. This is very fortunate because if something goes wrong you really want to be aware of what is happening. There are a lot of alarms that can be triggered, including and not limited to:
- Licensing issues
- Recovery Plans
- Permissions
- VM Protection status
- Protection Groups
And many more. I tried to count them and came up to 90 alarms (SRM 5.1). As far as I know it's not possible to create custom alarms, but I can't think of any alarm that is not available.
Alarms at my company are configured to send an email (although other options are available) and for email configuration the SMTP settings from vCenter are used. To check or configure these settings start the vSphere Client → Go to Administration → vCenter Server Settings → Mail.
Also note:
- that alarms are disabled by default, so after configuring do not forget to enable them.
- that alarms are configured per site, in bidirectional configurations you'll have to configure alarms on both sites.
Site Recovery Manager 5.1
Summary: How to install, configure and test VMware Site Recovery Manager 5.1.
Date: Around 2010
Refactor: 21 April 2025: Checked links and formatting.
This page is about VMware Site Recovery Manager (SRM) 5.1. Installation, configuration and testing will be discussed. This implementation will use Array Based Replication on a IBM N-Series 6060, which actually is a NetApp FAS3160, so we'll use the N-Series Storage Replication Adapter (SRA). We already have a replication between our sites but this uses an old naming convention and is also not compliant with our performance policies. Therefore these will also change. We already prepared our environment for implementing Site Recovery Manager so both of our sites have a vCenter, and they are in Linked Mode (which is not a requirement but is a nice to have). The database is a Microsoft MSSQL 2008 R2 Server which is already installed by my DBA on a separate server.
The preparations are discussed in:
VMware preparations:
Note: The vCenter 5.1 report is based on vCenter 5.1 GA. The installed version is upgraded to 5.1.0b (release date 2012-12-20).
NetApp preparations:
Note: The terms IBM N-Series and NetApp will probably both be used in this page. I'm used of talking about NetApps, but the software I'm using is the rebranded one from IBM. This is obviously for support reasons.
Squid
Summary: How to install a squid proxy server.
Date: Around 2014
Refactor: 22 March 2025: Checked links and formatting.
This is the article on installing and configuring squid on SLES11. The SLES 11 server is installed like this. Squid is in the support channel for SLES 11, so you'll also need to add the update repository to the server. See SLES Installation Update Server 11 on how to do that. The end situation will be two networks (private and public), with squid in the middle and protected by the firewall for the public network.
Use PowerShell with SharePoint Online Lists and Office DocProperties
Summary: The script below retrieves information from sharepoint online lists and puts that in prepared office files using docproperties.
Date: Around 2019
Refactor: 4 January 2025: Checked links and formatting.