Caution: Long Posting. Ok, here's my report from some afternoon testing:
As stated in my previous posting, I turned off the change journal on each of my Domino servers, cleared the UCJ files, and restarted the services.
I decided to do a test of back-to-back backups on one of my Domino servers. This server only has about 10 GB of Notes data, so it doesn't take too long to test a backup. I ran the backup on this server manually and it took about 30 minutes to do a full backup and verify and was successful. However, I've always gotten a good backup the first time the remote service is restarted.
So I decided to run the backup again. Well, it failed. The job stayed on Backup Scan for 15 minutes before I finally gave up. I tried to cancel the job but of course you can't cancel a job doing a backup scan. So after 15 more minutes waiting for the job to cancel (knowing that it wouldn't), I finally just stopped the service on the remote server and the backup job canceled immediately.
Now here is something I noticed: Even though I had deleted the UCJ files and disabled the change journal on the remote server, I noticed that there was still a UCJ file that got created and was actually updated several times throughout the backup.
Is the change journal actually disabled if a UCJ file is getting created? Is the existing UCJ file the cause of the backup job to get stuck scanning on the second backup?
Finally, I have another Domino server that only has 1.3 GB of data. This server has backed up flawlessly since the very first day of the upgrade...er..reinstall. The backup jobs on all Domino servers are set up the exact same way. The only difference is this server has very little Notes data and is very fast. Also, the UCJ files did get created on this server as well even though the change journal was disabled.
Maybe this information will help someone figure out this problem we Domino users are having.
That's my story and I'm sticking to it.
Follow-up: I restarted the remote service on the failed backup server without deleting UCJ files. I ran the backup and as expected, it was successful. Now here's the kink: I immediately started the second backup of the same server and this time it started just fine. Arrggghhhh!
Mike