Hello!

I read all entries about the storage of PRTG and it sounds for me that it should work, but still it does not!

I want my PRTG Monitor (WinXP, 13.1.2.1462) to store its data and logs on a remote network share/drive (NAS) because the local host is working with CF as HDD. I do not want PRTG writing more then necessary on the local device.

I just played several scenarios, nothing works. I tested network mapping also as nfs. Either PRTG changes the directories by itself back to default or not and still writes on the local drive.

Is there any chance to get this managed? What could be the reason why it does not work?

Kind regards, pah

Article Comments

Dear pah

This article provides a step-by-step instruction list to change the data path https://helpdesk.paessler.com/en/support/solutions/articles/543

Please make sure that according to the article to stop the PRTG core service before you change the path.


Nov, 2014 - Permalink

Hello!

Thanks for your answer. I know this article very well and I tried any possibility to change the drive for logging but it will not work. I also tried to change it via registry, no chance.

Could it be a permission problem? Which user uses the Monitor/Probe to write the data? Maybe because the share is not writable for it? I think about his because "C:\Documents and Settings\All Users\Application Data\Paessler\PRTG Network Monitor" is the default location. Permissions there are:

Administrators (WORKGROUP/Administrators) CREATOR OWNER Power Users (WORKGROUP/Power Users) SYSTEM Users (WORKGROUP/Users)

On the share:

Everyone Lunix User (LINUX-WORKGROUP/User)

Why does it change back to default although an other path is defined? Feels like a routine which gets active if the location is not writable for example.

Kind regards, pah


Nov, 2014 - Permalink

Dear pah

Which Windows version are you using on the PRTG Server?


Nov, 2014 - Permalink

Hello!

It´s WIN microXP and the solution is to start the services in the user-context which also is permitted to write on the nas / network share. PRTG will only use the credentials from the context in which it was started.

Therefor it is recommended to change the Log On User from "Local System account" to "This account": .\user and in the Paesslers Admin-Tools for the Server & Probe to change the Logs-Directories to the new UNC-Path like:


<Servername>\<share>\<directory>\

Restart the services.

Under the "Local System Account" the credentials could never be correct to write on a share. That´s the simple reason!

Works fine now! Hope some one can use this information too.

Regards, pah


Nov, 2014 - Permalink