I have Visual Cron Server currently installed on the C:\ drive. I am continually having to up the size of the volume due to Visual Cron logs filling up the volume. I would like to move the logs for Visual Cron the the E:\ drive so I do not have to keep increasing the system drive. This might be as easy as changing the path but I want to make sure because I am working in a production environment.

Hi and Welcome,

3 Things for you to have a look at straight away.

1) Are you doing extended logging ? - We do but that puts extra data in the logs.
Have a Look Under Server Tab, Settings, Log Settings, Settings Tab


2) There is a delivered Job that will Delete Old Log Files - If you deleted this do a fresh server install *somewhere* and have a look at that for a start.

We use the 14 days for Retention (Set on the Delete Log Files Task in this Job).

3) We run <D>ata Drives on all our servers, Physical and Virtual.

In VisualCron Client
Turn the Server Off (Temporarily)

In VisualCron Client
On the Server Tab Click Settings
in the Folders Tab Change the Paths you wish to:

in the Log Settings / Database Settings Tab Change the Log Database Location:

For the Database you will need to determine what retention works best for you based on Job volume.

In Windows Explorer with the VisualCron Server Still OFF
Move the relevant folder contents from the Old Location to the new location (Including the Database File if you moved it)

In VisualCron Client
Turn the Server On

You will note we have a Standard Directory Structure we use on any server running visualcron:

D:\VisualCron
D:\VisualCron\Backup
D:\VisualCron\Log
D:\VisualCron\Output
D:\VisualCron\Settings
D:\VisualCron\Temp

You may want to hit the Website and Help also, and from the client there are some Tutorials available from the help menu.

'Client' Logging also goes onto C: but we leave it there, as we generally do not use the <local>client on the server so we were not concerned with this.

Good Luck !

Thank you for that reply, I will be setting a scheduled maintenance window to do the operations that you outlined in your post. Thank you again KJDavie

Hello,
I'm trying to move the log database (VisualCron4.SDF). I try this procedure but I cannot adapt the location field in Database Settings tab. I also remarked that the file stay in use. I confirm that the Server was OFF in the client and the Windows service was running.
Is it something changed since you made the procedure? Now I'm with the version 8.2.4.
Thanks in advance
Jonathan

Hello,
I'm trying to move the log database (VisualCron4.SDF). I try this procedure but I cannot adapt the location field in Database Settings tab. I also remarked that the file stay in use. I confirm that the Server was OFF in the client and the Windows service was running.
Is it something changed since you made the procedure? Now I'm with the version 8.2.4.
Thanks in advance
Jonathan

Yes, currently a restart of service is required after changing folder.

---

Hi,
My problem is I cannot change the database path in : "in the Log Settings / Database Settings Tab Change the Log Database Location". The text field is locked.
Jonathan

Hi,
My problem is I cannot change the database path in : "in the Log Settings / Database Settings Tab Change the Log Database Location". The text field is locked.
Jonathan

Go to Server settings->Folders->Change Output cache folder. Then it requires that you restart the VisualCron service.

---

Indeed from this tab we can adapt it. Thanks

Hello,
I'm come back to this.

I'm installing a new server with version 9.9.8.

When I adapt folders (output cache + temp), that set back to default.

I tried this procedure:
1. enable extended logging
2. stop server
3. change folders in settings/folders
4. move files from c:\programdata\visualcron\output
5. restart visualcron service
6. start server

Any idea?

Thanks in advance

Hi serverteam,

Have you tried to do it via C:\Program Files (x86)\VisualCron\settings\settings_server.xml ?

Use the procedure but instead of changing it via the GUI, try it the via xml file

YEah, when updating directly the XML, it's working. Thanks