Hi,

I'm a big fan of VisualCron but one of the annoying limitation of VC, is the remote execute that does not have the flexibility that local jobs have on the VC server.

It would be nice to be able to run multiple VisualCron servers and have them talk to each other so that you have a master server that can run jobs with chained tasks on multiple servers without the limitation of remote execute.
It would them make sense for me to buy the site license.

Right now you would have to setup jobs on each server and create some custom trigger / file for them to know the jobs on the second server has to start. This is quite tedious!
And for me one the the advantage of VisualCron is that I can monitor/run all the jobs I have to run in one central place.

Let me know if there is any plan to release such feature in the coming

Fabien

Hi Fabien,

thanks for your post.

Yes, we have such plans. Please post here everything you expect from cross server Execution etc. and we will have it as a base for future development.

---

Again the goal for me is to have a central place to monitor and control all jobs running in my company, and have them as reliable as possible.

I think there are two kinds of features for this that I'd like:

The main one, execute on any machine (with a VC server!):
- In the main settings on the "execute" in the execute context to have the possibility to choose the machine name/address on which the process is to be executed.
It would then just ask the server residing on that other machine to execute the tasks, thus working around the limitations inherent to "remote execute".
I'm not really thinking server should auto-discover or know each other, but rather if VisualCron is not available on that machine or not started the task should fail.

The failover functionalities (nice to have):
- The ability to configure server failover per task, if the machine on which a task is supposed to be running is not available then have the possibility to configure a failover machine.
- The ability to configure server failover (for instance if the master server were to fail, another one picks up the main tasks list)
- All VC servers read the same config file / tasks list, but because we can specify on which machine it runs there is no conflict.

We have added some new features, please check them out here:

http://www.visualcron.co....aspx?g=posts&t=1834 

---

Hi,

we are currently investigating best way of implementation of a master/slave relationship.

We have some thoughts in mind which we would like to have feedback on. We would also like to have detailed feedback of any other requirements you may have.

Here are our main ideas:

- a VisualCron Server can be configured to be either Master or Slave or Independent
- when a Server is Slave you can specify a Master IP together with a username and password
- the Slave will auto update Jobs, Tasks and other Server objects when the Master is updated
- optionally, the Master can execute Jobs locally
- optionally, the Slaves can be configured to Execute a Job when it is Executed on the Server (manually or by Trigger) - by default Triggers will be located on each Slave machine
- optionally, Settings from Master can be updated on Slaves when updated on Master
- optionally, Jobs can be created on Slaves that is outside of the Master-> sync

We welcome all your feedback regarding this.

---

Im very interested in setting up the above master and slave relationship in an effort to spread the load of running jobs across multiple servers. Is there walk through on how to accomplish this?

Thanks

Im very interested in setting up the above master and slave relationship in an effort to spread the load of running jobs across multiple servers. Is there walk through on how to accomplish this?

Thanks

We do not have any such feature yet. With this thread we started to investigate what customers needed. We are not 100% sure about the interest and possible usage for this. It is a lot of work to do this so we need to do some planning.

If you want us to prioritize this or do it in any special way I suggest you send an email to sales@visualcron.com and we can discuss it further.

---

I have submitted an email to the sales team. However, is there any way to do some of this now? I read, that it might be possible to chain visualcron jobs and have them run on multiple visualcron servers? Also is there a automated way to synchronize all the VC jobs onto a passive server?

I have submitted an email to the sales team. However, is there any way to do some of this now? I read, that it might be possible to chain visualcron jobs and have them run on multiple visualcron servers? Also is there a automated way to synchronize all the VC jobs onto a passive server?

No, there is no good way of doing this now.

---

Still on the radar I hope?

Here, the Visualcron implementation is important enough to have a backup server standby.
Is there any update about this request?

Is there an other topic I should look at for this, or is this the one?

Regards,
Erik

---

Still on the radar I hope?

Here, the Visualcron implementation is important enough to have a backup server standby.
Is there any update about this request?

Is there an other topic I should look at for this, or is this the one?

Regards,
Erik

We have some ideas how to implement it this but it is a lot of work compared to other requests.

---

I would also like to request that this functionality become a higher priority. The ability to manage job execution on multiple machines from a central server, as well as having a passive standby server with automatic failover would make this product invaluable to my company.

We recently purchased the Country License for our multiple data centers. We have plans to leverage it for our business processes as well as routine server and database maintenance. We are also planning on building out an in-house orchestration application that uses the VisualCron API. As it stands right now, this is set to be a tedious task fraught with potential implementation and administration issues due to the decentralized nature of VisualCron's architecture.

I'm certain that with the VisualCron task configured for Remote Job Execution and Remote Triggers, we could pull off something close, but the ideal scenario here is a Server/Agent architecture with automatic failover to a standby server and agent autonomy (agents know their jobs and run them regardless of network connectivity). I believe that if you made these features a priority and offered them as a paid add-on or moderately increased the license price, it would still be a more than reasonable investment for us.