This IBM® blueprint describes the SingleStoreDB that is running on Red Hat OpenShift in a containerized environment. The SingleStoreDB deployment uses the IBM Spectrum® Scale container native access storage class to create persistent volumes (PVs) for the SingleStoreDB pods deployment. This document also describes the process that is used to expand a SingleStoreDB volume on IBM Spectrum Scale and an IBM Spectrum Scale PV on a Red Hat OpenShift cluster for IBM Spectrum Scale to verify that the SingleStoreDB remained intact after the volume is expanded. The procedure to create a sample database that is named stockDB, and the data analytical stats for reading and writing the data also are included. The sample data was captured for comparison statistics for SingleStoreDB that is deployed on the IBM Spectrum Scale Cluster File System and local storage. These comparison statistics emphasize the notable difference between the sample data sets. Finally, this document also explains the procedure that is used to create the same sample database with the unlimited storage feature in SingleStore by using IBM Cloud® Object Storage.
This IBM® blueprint describes the SingleStoreDB that is running on Red Hat OpenShift in a containerized environment. The SingleStoreDB deployment uses the IBM Spectrum® Scale container native access storage class to create persistent volumes (PVs) for the SingleStoreDB pods deployment. This document also describes the process that is used to expand a SingleStoreDB volume on IBM Spectrum Scale and an IBM Spectrum Scale PV on a Red Hat OpenShift cluster for IBM Spectrum Scale to verify that the SingleStoreDB remained intact after the volume is expanded. The procedure to create a sample database that is named stockDB, and the data analytical stats for reading and writing the data also are included. The sample data was captured for comparison statistics for SingleStoreDB that is deployed on the IBM Spectrum Scale Cluster File System and local storage. These comparison statistics emphasize the notable difference between the sample data sets. Finally, this document also explains the procedure that is used to create the same sample database with the unlimited storage feature in SingleStore by using IBM Cloud® Object Storage.
The focus of this document is to highlight early threat detection by using Splunk Enterprise and proactively start a cyber resilience workflow in response to a cyberattack or malicious user action. The workflow uses IBM® Copy Services Manager (CSM) as orchestration software to invoke the IBM FlashSystem® storage Safeguarded Copy function, which creates an immutable copy of the data in an air-gapped form on the same IBM FlashSystem Storage for isolation and eventual quick recovery. This document explains the steps that are required to enable and forward IBM FlashSystem audit logs and set a Splunk forwarder configuration to forward local event logs to Splunk Enterprise. This document also describes how to create various alerts in Splunk Enterprise to determine a threat, and configure and invoke an appropriate response to the detected threat in Splunk Enterprise. This document explains the lab setup configuration steps that are involved in configuring various components like Splunk Enterprise, Splunk Enterprise config files for custom apps, IBM CSM, and IBM FlashSystem Storage. The last steps in the lab setup section demonstrate the automated Safeguarded Copy creation and validation steps. This document also describes brief steps for configuring various components and integrating them. This document demonstrates a use case for protecting a Microsoft SQL database (DB) volume that is created on IBM FlashSystem Storage. When a threat is detected on the Microsoft SQL DB volume, Safeguarded Copy starts on an IBM FlashSystem Storage volume. The Safeguarded Copy creates an immutable copy of the data, and the same data volume can be recovered or restored by using IBM CSM. This publication does not describe the installation procedures for Splunk Enterprise, Splunk Forwarder for IBM CSM, th Microsoft SQL server, or the IBM FlashSystem Storage setup. It is assumed that the reader of the book has a basic understanding of system, Windows, and DB administration; storage administration; and has access to the required software and documentation that is used in this document.
Thank you for visiting our website. Would you like to provide feedback on how we could improve your experience?
This site does not use any third party cookies with one exception — it uses cookies from Google to deliver its services and to analyze traffic.Learn More.