You might check that the username for the backup has write
permission to the backup directory.
I recently got MM to send an FTP backup to a Windows 2008 R2
To make it work, I had to set the box's FTP site to the exact
directory where the backup was going to go. This is found at Start
--> IIS Manger. In the left pane, expand the server name, and
then expand Sites. Right-click the FTP site, choose Manage FTP
Site, then choose Advanced Settings. Under Physical Path put the
full pathname of the backup directory.
Once this is done, go to Start --> IIS Manger. In the left pane,
expand the server name, and then expand Sites. Right-click the FTP
site, choose Manage FTP Site and choose Restart.
Now go to the MSS. Pull up the Remote Storage Configuration and in
Directory put only a forward slash: /
I don't know exactly why - maybe it was a permissions thing that I
missed - but doing it this way was the *only* way I could make it
work. If the backup directory is blah/blah/blah/username/backupdir
and I made the FTP site's home blah/blah/blah/username and set the
Directory on the Remote Storage Config form in the MSS to
/backupdir, it would not work. This was different than on the older
Windows server that I used to send the FTP backups to.
This is only a temporary measure, I have been trying to get an SFTP
backup working, but have had no success. Another frustrating thing
is that I can't get our Message Networking 3.1 server to have a
successful FTP backup to this Windows 2008 server - I get the
'Failed to create file tes_conn_dummy1' error you describe. For
some reason the MN 3.1 server will *not* accept just a single
forward slash as the path name. It won't take ../backupdir or any
other thing I tried to clever my way around it either. That is
annoying, as the MN and MSS backups are identical in all other
respects. I have been reading up on the Read Me files for the
various MN patches, to see if this was a known issue that was
adressed, but haven't seen it.