FileZilla is one of the best FTP clients ever, however while they’re perfect everybody else isn’t
What this means is that if an FTP site isn’t configured correctly then trying to download files that have special characters or accents in them using the FileZilla client will fail, the FileZilla team don’t want to support it because they’re doing the correct thing standards wise (UTF-8 settings on the server) and it’s other people’s failings that are causing the problem but other clients DO support this kind of behaviour eg. firefox which is a shame…
This means that we do need to find a way around the problem with FileZilla, the first sign that something has gone wrong will be in your failed downloads tab
A quick glance at the file usually shows you that there is a special character or accent in it, in this case a “À”
To get round this I found easiest way is merely to select all of the items that have failed right click and export them
This will give you an XML file, open it up and look for the “File” sections and then find and replace the special charaters in the “localFile” section to a none special charater, save the file then import it into fileZilla (file —> Import), you will find that it will download all missing files.
It would be nice if there was an automated version of this but as far as I can tell the FileZilla guys are sticking to standards. :(
This is an old tip that I never thought I would use again but has come back to life with the advent of the cloud:
We are migrating multiple servers from onsite to the cloud, the bandwidth of this copy means that it won’t happen within 24 hours and it definitely won’t happen within the maintenance window we have, normally with Lotus Notes migrations from one server to another this wouldn’t be an issue as Domino replication has been a model of stability and ease of use for well over 10 years HOWEVER there are tons and I do mean tons of complex replication settings in this clients setup a lot of them unknown or unremembered to the client, so they have found that using replication means they will miss some of these and after having a look at them I tend to agree so file copy it is..
NSF files tend to be a bit bulky and zip up really rather well so zipping them up before moving them over them makes sense but we don’t want to do one large zip, because 1) The target file system doesn’t have a lot of extra space on it, and 2) The actual copy will take several days so we want to do it one chunk at a time
First let’s get a list of all of the NSF’s files we want to copy over, this will have a double advantage of giving us an indication of numbers and size etc as well as giving us something that we can actually work through so that we can do one group at a time,
Once we have the list then the following little script popped in a batch file and with WinRAR installed on the system will give you an exact mimic of your notes folder structure but with each NSF zipped up and in the correct place
You can then copy them over in whatever method you prefer and unzip as suits you, this method may seem a little Noddy but this is the third time I’ve used it and every time the notes movement has been the easiest part of a migration.