Description

By default, the vxisis.log will reach a maximum file size of 14 MB. When this occurs, the vxisis.log is renamed vxisis.log.0, a new vxisis.log file is created, and logging continues to that file. These files are located in the ...\Veritas\Veritas Object Bus\Logs directory

If debug logging is enabled, or the server is very active, there is a possibility that the log data capturing an issue is overwritten by the time the logs are collected. This may result in the inability to determine the cause of the issue.

The logging functionality will always create 2 files with the process explained above; however, the Max File Size of 14 MB can be increased to allow more log data in each of the files. The steps for increasing the size are provided below.

Steps:

1. Open the Registry Editor (start > run > regedit)

2. Browse to: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\VxSvc\CurrentVersion\Tracing\vxisis

3. Locate the MAXLOGFILESIZE value entry in the right-pane, and modify accordingly:

The size provided in hexadecimal will match the size in MB's of the files (14 by default).

For example, to set the MAXLOGFILESIZE to 25 MB, set the hexadecimal value to 25. This would provide a total of 50 MB of log data to be captured before data is overwritten.

Once the value data is set, it is necessary to restart the vxsvc service.

NOTE:
If this is a Windows Failover Cluster, it is recommended to perform this on a passive node, or wait for downtime to implement this as a restart of this service could cause a Volume Manager Diskgroup (VMDg) resource to fault in the cluster. The registry change can be made at any time, but it won't take effect until the vxsvc service is restarted.

If this is a Standalone server or it belongs to a Veritas Cluster (VCS), then these steps can be performed without causing any downtime:

4. Open a command prompt and run the following commands to restart the vxsvc service:

- net stop vxsvc
- net start vxsvc

Once complete, the new Max File Size will be implemented.