INITIAL_MEMORY, MAX_MEMORY on Windows

Article:HOWTO68197  |  Created: 2012-02-06  |  Updated: 2013-07-18  |  Article URL http://www.symantec.com/docs/HOWTO68197
Article Type
How To


Environment

Subject


INITIAL_MEMORY, MAX_MEMORY on Windows

Both INITIAL_MEMORY and MAX_MEMORY allow configuration of memory usage for the Java Virtual Machine (JVM).

Symantec recommends that the NetBackup-Java Administration Console, the Java Windows Administration Console, or the NetBackup Backup, Archive, and Restore user interface run on a system that contains at least 1 gigabyte of physical memory. Make sure that 256 megabytes of memory are available to the application.

INITIAL_MEMORY specifies how much memory is allocated for the heap when the JVM starts. The value probably does not require changing. The default is sufficient for quickest initialization of jnbSA, the Java Windows Administration Console, or jbpSA on a system with the recommended amount of memory.

On UNIX systems, the initial memory allocation can also be specified as part of the jnbSA or jbpSA command. For example:

jnbSA -ms 36M

Default = 36M (megabytes).

MAX_MEMORY specifies the maximum heap size that the JVM uses for dynamically allocated objects and arrays. If the amount of data is large, consider specifying the maximum heap size. For example, a large number of jobs in the Activity Monitor.

On UNIX systems, the maximum memory allocation can also be specified as part of the jnbSA or jbpSA command. For example:

jnbSA -mx 512M

Default = 256M (megabytes).

See Runtime configuration options for NetBackup-Java and Java Windows Administration Console on Windows

See MEM_USE_WARNING on Windows


Legacy ID



v41641971_v71296339


Article URL http://www.symantec.com/docs/HOWTO68197


Terms of use for this information are found in Legal Notices