Platform Best Practices The Platform is the technical portion of the product. The best practices applied here are to help provide the most optimal options for the platform to provide a stable running environment for daily operational use. Before deployment of vRealize Operations Manager, the first step is to size the environment. This section will cover sizing and backup& restore or disaster recovery. These best practices will help ensure that the platform, v Realize OperalonsRp deploying the product. Additional best practices are included for administration tasks such Manager, is properly sized, running and able to handle the monitored load efficiently Sizing Storage Approach Size the deployment with twelve to eighteen months of infrastructure growth When an environment outgrows the original deployment size, performance degradation and usability problems may become present. Planning for infrastructure growth of twelve to eighteen months will allow the system to continue functioning without the need to immediately resize or scale out the deployment. For example, if you nticipate a 10%annual growth, increase the initial size by 15% to obtain an eighteen-month sizing Review the sizing guidelines frequently and often during the growth of the environment(resizing To keep the environment running with optimal parameters, it is important to review the sizing guidelines and resize the deployment if necessary. Even with expected growth, reviewing the sizing guidelines regularly will proactively prevent performance and usability problems typically associated with undersized environments General Guidelin Validate the sizing guidelines with your actual environment The sizing guidelines provide general estimates and requires confirmation with the actual environment. For example, the data entered into the sizing calculator may yield additional objects not captured in the actual Calculate only the components which will be monitored It is possible that some components do not need to be monitored; therefore, exclude those components in the sizing calculations Size the cluster There are multiple sizes for analytics nodes, extra small, small, medium, large and extra-large. It is best to use the least number of nodes when possible. For example, if the recommendation is to have 10 large nodes or 4 ex large nodes, use the lesser extra-large nodes to minimize communication across more nodes Size the remote collectors There are two sizes for default remote collectors, standard and large. Use the correct size remote collector based nvironment The default setting for data retention is six months. If three months is all that is needed, lower the default value. nderstand what you gain when using long data retention periods. It may not necessarily help having longer tention periods. Depending on your deployments needs, configure the retention period to suit your requirements vRealize Operations Manager Best Practices /6vRealize Operations Manager Best Practices /6 Platform Best Practices The Platform is the technical portion of the product. The best practices applied here are to help provide the most optimal options for the platform to provide a stable running environment for daily operational use. Before deployment of vRealize Operations Manager, the first step is to size the environment. This section will cover sizing and recommendations after deploying the product. Additional best practices are included for administration tasks such as backup & restore or disaster recovery. These best practices will help ensure that the platform, vRealize Operations Manager, is properly sized, running and able to handle the monitored load efficiently. Sizing Storage Approach • Size the deployment with twelve to eighteen months of infrastructure growth When an environment outgrows the original deployment size, performance degradation and usability problems may become present. Planning for infrastructure growth of twelve to eighteen months will allow the system to continue functioning without the need to immediately resize or scale out the deployment. For example, if you anticipate a 10% annual growth, increase the initial size by 15% to obtain an eighteen-month sizing recommendation. • Review the sizing guidelines frequently and often during the growth of the environment (resizing) To keep the environment running with optimal parameters, it is important to review the sizing guidelines and resize the deployment if necessary. Even with expected growth, reviewing the sizing guidelines regularly will proactively prevent performance and usability problems typically associated with undersized environments. General Guidelines • Validate the sizing guidelines with your actual environment The sizing guidelines provide general estimates and requires confirmation with the actual environment. For example, the data entered into the sizing calculator may yield additional objects not captured in the actual environment or vice versa. • Calculate only the components which will be monitored It is possible that some components do not need to be monitored; therefore, exclude those components in the sizing calculations. • Size the Cluster There are multiple sizes for analytics nodes, extra small, small, medium, large and extra-large. It is best to use the least number of nodes when possible. For example, if the recommendation is to have 10 large nodes or 4 extra￾large nodes, use the lesser extra-large nodes to minimize communication across more nodes. • Size the Remote Collectors There are two sizes for default remote collectors, standard and large. Use the correct size remote collector based on collected data. If necessary, use multiple remote collectors to ensure proper sizing of remote collectors for the environment. • Adjust the time series data retention to keep data for a timeline which data is truly needed The default setting for data retention is six months. If three months is all that is needed, lower the default value. Understand what you gain when using long data retention periods. It may not necessarily help having longer retention periods. Depending on your deployments needs, configure the retention period to suit your requirements