I have seen changing the priority of the Scheduled Task speed up a probkup considerably (3 0r 4 times faster in some cases), so certainly worth trying in this case.
Essentially you just add a second agent to you source.repl.properties file and set up as normal, form the documentation (OpenEdge Replication User Guide):
# OpenEdge Replication properties file for a database that will be used
# as a source database for OpenEdge Replication. This is a two agent...
In Windows the uninstaller initiates another process that does most of the work. Just looked back at the AutoIt script i wrote a while ago and i wait for the initial process then look for a process beginning with "_is" and then wait for that to finish.
I have seen this occur when another process tries to access the backup file whilst you are backing up. For example a backup job that is pushing it out to tape or and anti virus scan.
I've done some testing with this and you don't need to change your wrx files you just have to have the 64 bit version (assuming one exists) of the OCX registered.
There was a bug relating to online backups causing a memory leak on Windows 2008, if this is your problem upgrading to the latest version of Progress will solve it.
I agree Rob and have recommended the solutions you have mentioned.
They use Hyper-V Replica for the rest of there infrastructure and I said I would do some digging to see if anyone has successfully used it with Progress.
Hello,
Has anyone successfully used this to replicate a VM with a Progress database running on it and maintained the integrity of the database?
I have a client who wishes to uses this, i have informed them it is not supported by Progress and they would need to extensively test the solution...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.