-
1. Re: Scratch Location
The scratch location on the ESXi is totally unrelated to loginsight. The scratch location is still required by the ESXi host
-
2. Re: Scratch Location
What I'm struggling with is to understand why then is the non-persistent storage log alarm going away after vRLI is registered to the hosts?
-
3. Re: Scratch Location
Because it detects that logs are being off-loaded to *some* place other than residing solely on a host which stores them in RAM. The alarm is just designed to let you know that those logs are ephemeral in nature. Once they're off-loaded to another location, that's no longer true.
-
4. Re: Scratch Location
So then that means scratch is being sent to Log Insight then and does not need to be updated on the host?
-
5. Re: Scratch Location
Logs are still being stored locally on scratch (which, in your case, is RAM disk), but they're also being sent to vRLI. If you want them saved to a persistent location on ESXi in addition, you'll need to direct those logs to some other scratch location than a RAM disk. The choice is yours.
-
6. Re: Scratch Location
Ahh ok, see I thought I had read that before. Since at least one copy is being sent to vRLI then there may or may not be a need to store them locally as well. thanks!