Monthly Archives: June 2013

DeltaCopy, Rsync, Cygwin and Windows to Linux backups

I wrote a while back regarding Rsync backups from Windows servers to Linux using DeltaCopy.

It’s all been working ok but I’ve had some files failing with a “file has vanished’ message.

At first I tried searching for a solution based on the failures being any file with a special accent character.

The log email that I get sent by DeltaCopy contained something like this:

Profile datafiles failed to execute.
Execution log
sending incremental file list
file has vanished: "/cygdrive/D/datfiles/A standard Windows type file?.jpg"
file has vanished: "/cygdrive/D/datfiles/Another file with two questionmarks ??.docx

Investigating the Windows server the files did exist and they were not “in use” during the backup. However, some (note: not all)  some, files had special non-standard English characters in the file names. So characters with umlauts etc, like È, É, Ê  were giving issues alongside some punctuation characters that appeared normal but I suspect have been prepared from a non-English keyboard or system with a different character set.

So assuming that the character set was the issue I went searching.

I had narrowed it to the Cygwin toolkit rather than Rsync itself and came across this old message thread that included a link to a modified cygwin1.dll as  except that the link was broken. So I chased a modified cygwin1.dll and found what appears to be the updated link at

Downloading the compiled library file cygwin1-dll-20-11-18.tar.bz2 and extracting it to my Windows server using 7-Zip I renamed the old dll as cygwin1.dll.orig and copied the modified cygwin1.dll into the DeltaCopy directory.

Then I re-ran a data file backup that had given me “file vanished” errors and it seemed to work. But the next time it ran, it gave errors again.

So I delved deeper and found that the version of Rsync that is distributed with DeltaCopy is quite old, replacing the Rsync toolkit that supports DeltaCopy was the next thing to try and it worked a treat. I will document that process shortly.



Turning off WordPress redirects index.php to index.html on Cpanel Apache

I spent a bit of time today trying to research why Apache on Cpanel insisted on redirecting from index.php when it was entered as an explicit URL to the default index.html page in the website home directory.

As it turned out, while I am searching for “cpanel apache redirects” I should have been asking “Why does WordPress redirect…” and that change of question led me to this WordPress forum thread that addressed the actual issue.

Now normally I would not repeat the information here, but just in case that link disappears, I do want to be able to get to it again, so here it is.

The issue actually is not Apache or Cpanel driven, but is an issue with WordPress and the way that it redirects all requests to the home page for the site. Hence despite me trying to access index.php, WordPress was redirecting to index.html, and that prevented me from seeing the new WP site.

Ultimately the purpose of this was to allow for WordPress to be installed alongside an existing page based site and deploy for final user acceptance before switching off the old site and moving to WordPress as the new site.

The trick is simply a manually installed plugin that can be removed after final commissioning to production.

1. Open your site with an FTP program or SSH depending on you preference

2. Navigate to yoursite_folder/wp-content/plugins/

3. Create a new folder for the plugin – call it disable-canonical-redirects – or dcr for short

4. Change to that folder

5. Create a new index.php file and include (copy and paste or re-type) this PHP code into that file:

Plugin Name: Disable Canonical URL Redirection
Description: Disables the "Canonical URL Redirect" features of WordPress 2.3 and above.
Version: 1.0
Author: Mark Jaquith
Author URI:

remove_filter(‘template_redirect’, ‘redirect_canonical’);

5. Visit your WordPress Admin backend and activate this new plugin

6. All is now good to go and access index.html by default or index.php for WordPress explicitly.

Many thanks to Mark and others in that discussion thread.


Windows SBS 2008 and WSUS 3.0 Wizard Object Moved Error

I have done battle with an SBS Server in recent weeks. Some of it was simple fixes, while getting WSUS working and updates generally has been challenging.

The server had not been patched for almost 18 months and the reason was that WSUS was not working and there were some group policies that apparently were disabling connections even for the server.

I have not fully resolved this but one of the key items was this Microsoft TechNet Thread on WSUS Configuration Wizard where I learn that there is a mandated update KB2734608 which resolved the connection issue.

Now that the server is patched and updated, I’ll delve into what the workstations need to get their dose of Windows medicine.

SME Server 8.0 Outlook email external connection imaps

I had the need to setup Outlook to connect to an SME Server 8.0 recently and at first glance it seemed easy enough but it did not work as expected.

The primary issue appears to be that Outlook does not like to play with the SME Server SSL or Ports without being shown the way.

The end result is a step by step guide that I have published over at the WrenMaxwell Knowledgebase complete with screenshots of each step.

I suspect that this may well apply to other self-hosted servers beyond SME Server and kept the text generic for that purpose, but if you are trying to get your SME Server to work then the first thing to do is make sure that the imaps and smtps ports are open on the firewall and on the SME server.

The only other thing that needs doing is aligning the server name with the external hostname and the self-issued SSL certificate.

It was interesting that setting up a couple of portable devices, an iPhone, iPad, and Android all worked with the SME Server connection without any specific settings being required, the server was just accepted and worked from the get-go.  Microsoft Outlook, however, seems to raise barriers.

I did reference this Microsoft article KB286197 as a preliminary to this process and found it lacking for the options of secure SSL connections and certainly it has the basics but insufficient detail to guide an appropriate outcome for an SME Server connection.

The SME documentation over at is also lacking a bit of input and I might try to help out there if I can make some time.