Deprecated: Funksjonen jetpack_form_register_pattern er foreldet siden versjon jetpack-13.4! Bruk Automattic\Jetpack\Forms\ContactForm\Util::register_pattern i stedet. in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php on line 6078 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 Warning: Cannot modify header information - headers already sent by (output started at /customers/8/5/b/vedaa.net/httpd.www/wp-includes/functions.php:6078) in /customers/8/5/b/vedaa.net/httpd.www/wp-includes/rest-api/class-wp-rest-server.php on line 1831 {"id":1029,"date":"2022-02-16T17:56:57","date_gmt":"2022-02-16T16:56:57","guid":{"rendered":"https:\/\/vedaa.net\/?p=1029"},"modified":"2022-02-16T22:41:54","modified_gmt":"2022-02-16T21:41:54","slug":"how-to-deploy-vrealize-log-insight-with-reduced-disk-size","status":"publish","type":"post","link":"https:\/\/vedaa.net\/vmware\/how-to-deploy-vrealize-log-insight-with-reduced-disk-size\/","title":{"rendered":"How to deploy vRealize Log Insight with reduced disk size"},"content":{"rendered":"\n
\"\"<\/a><\/figure><\/div>\n\n\n\n

This blog post is a result of me ranting to a colleague about vRealize Suite Lifecycle Manager (vRSLCM) not supporting deployment of the extra small vRealize Log Insight node. I do not know the official reason for this, but I guess it is because the extra small node is only meant for proof-of-concept and test deployments. <\/p>\n\n\n\n

The reason for reducing the storage footprint on Log Insight is because it will eventually fill all its available storage space with log data. And using 500 GB of storage space in a lab environment is probably never desirable.<\/em><\/p>\n\n\n\n

Use the <\/em>Extra Small<\/strong> version of the appliance in a proof-of-concept or test environment, but not in a production environment. This configuration supports up to 20 ESXi hosts (~200 events\/second or ~3GB\/day) .<\/em><\/p>From the Log Insight documentation Sizing the vRealize Log Insight Virtual Appliance<\/a><\/cite><\/blockquote>\n\n\n\n

During this spontaneous brainstorming session where I wanted to deploy Log Insight with a smaller storage footprint than default. We did a few tests and found that it was easy to achieve this as long as we don\u2019t use vRSLCM. Or could we?<\/p>\n\n\n\n

\n
\n
RESOURCES<\/strong><\/th>MINIMUM REQUIREMENT <\/strong><\/th><\/tr><\/thead>
Memory<\/td>4 GB <\/td><\/tr>
vCPU<\/td>2<\/td><\/tr>
Storage Space<\/td>530 GB<\/td><\/tr><\/tbody><\/table>
Extra Small Log Insight Deployment Requirements<\/figcaption><\/figure>\n<\/div>\n\n\n\n
\n

This table shows default setup for the extra small node. In the next section I have listed the steps on how to choose your own storage size.<\/p>\n<\/div>\n<\/div>\n\n\n\n

Deploying vRealize Log Insight with smaller disk size.<\/h2>\n\n\n\n
\"\"<\/a>
vRealize Log Insight Live Storage after replacing default 500 GB disk with a 100 GB disk<\/figcaption><\/figure><\/div>\n\n\n\n

Deploying Log Insight appliance with a smaller disk size is supprisingly easy. Just follow these few steps.<\/p>\n\n\n\n