Knowing the fact that DXA expects all items including binaries to be published to the CD Broker database and it will cache binaries on file system of the web application server. But if we restart the server or do admin refresh, these cached binaries will get deleted.
Question:
Kindly suggest how to retain these cached binaries as it is, after a server restart or a admin refresh? So that we can reduce the DB hits.
Update:
Admin refresh, Server restart are just an example, if we do a new deployment too then those cached binaries will get deleted. So if anyone try to access these files, again application will hit the DB to fetch the binary and then it will get cached for next request. To avoid this DB hits only i am looking for a suggestion if any how we can prevent cached binaries to get deleted.

Knowing the fact that DXA expects all items including binaries to be published to the CD Broker database and it will cache binaries on file system of the web application server. But if we do a new EAR deployement, these cached binaries will get deleted.
Question:
Kindly suggest how to retain these cached binaries as it is, after a new deployment? So that we can reduce the DB hits.
Update:
If we do a new deployment too then those cached binaries will get deleted. So if anyone try to access these files, again application will hit the DB to fetch the binary and then it will get cached for next request. To avoid this DB hits only i am looking for a suggestion if any how we can prevent cached binaries to get deleted.

Knowing the fact that DXA expects all items including binaries to be published to the CD Broker database and it will cache binaries on file system of the web application server. But if we restart the server or do admin refresh, these cached binaries will get deleted.
Question:
Kindly suggest how to retain these cached binaries as it is, after a server restart or a admin refresh? So that we can reduce the DB hits.

Knowing the fact that DXA expects all items including binaries to be published to the CD Broker database and it will cache binaries on file system of the web application server. But if we restart the server or do admin refresh, these cached binaries will get deleted.
Question:
Kindly suggest how to retain these cached binaries as it is, after a server restart or a admin refresh? So that we can reduce the DB hits.
Update:
Admin refresh, Server restart are just an example, if we do a new deployment too then those cached binaries will get deleted. So if anyone try to access these files, again application will hit the DB to fetch the binary and then it will get cached for next request. To avoid this DB hits only i am looking for a suggestion if any how we can prevent cached binaries to get deleted.