Exchange backup to tape stays in updating catalog status for long time and may cause remsrv64.exe process to use high memory on Exchange server
Problem
In some environments, it's observed that while job is in updating catalog status, the process remsrv64.exe (Process name is "Backup Exec Remote Server") is utilizing high memory on the server.
While backup to tape, cloud or OST storage, high memory usage is on Exchange server. For backup to disk/dedupe or duplicate job, memory of the Backup Exec server is utilized highly.
Solution
This issue has been resolved in a newer version of Backup Exec. To resolve this issue and receive the new Backup Exec improvements, please upgrade to the current version of Backup Exec.
The memory cache size can be configured in the latest version of Backup Exec using a registry key.
Set the following registry on ;
- The Backup Exec server, if backups are to Backup to disk, dedupe storage or are duplicates to tape or
- The Exchange Server, if backups are to tape, cloud or OST storage
KEY_LOCAL_MACHINE\Software\Symantec\Backup Exec For Windows\Backup Exec\Engine\Exchange
create new value; dbCacheMaxPages (DWORD)
Description of the registry:
Configure the number of pages Exchange ESE.dll will use as a cache. 0 indicates all available memory.
Each page of an Exchange 2016 database is 32k, therefore setting this key to 16384 (decimal, hex is 4000) will force a cache of 512MB.
The bigger the cache can be used likely the better the performance will be.
References
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.