00:02
Ransomware is a threat to every organization every size in every vertical across the globe. Welcome to my new video on ransomware protection with flash or s powered by coal. The city one of the most common attack vectors we see today is the destruction of backups, which makes it impossible to restore from a backup and makes it more likely that a ransom will be paid. Pure storage.
00:25
And Coe City have joined forces to protect your backup data from ransomware destruction. Flash cover? S powered by coal. The city offers differentiated multilayered immutable protection for your backup data. Flash recover powered bike obesity is an integrated more than all flash data protection solution for rapid recovery at scale with storage innovation from pure and modern backup
00:50
software from kuwait City. The integrated Flash s solution delivers simplicity performance through scale out with the disaggregated storage and compute architecture by providing ransomware protection, Flash recover lets you focus less on managing backup and recovery systems and more on delivering results for your organization. Today. Flash recover is found in fortune 500 companies
01:14
and in vertical industries like healthcare, financial services, state and local government protecting terabytes of data. Flash recover runs on the power of flash blade with performance that meets the most demanding recovery sls that legacy air gap solutions cannot meet the recovery sls that customers need. When a ransomware attack happens, what is the
01:38
same old snapshot in flash played safe mode, snapshots are designed to secure the backup data from ransomware attacks. Flash plate safe mode for file systems does two things enables the automatic creation of snapshot and it also prevents the user from eradicating the snapshots from the system. If a malicious attack causes problem with the new backup data there is a part of recovery
02:00
from older cleaner snapshot. Flash blade protects backup data, meta data and configuration data with read only mode snapshots that cannot be eradicated if the file backup data is compromised, you can recover the backup and confirmation data from the read only snapshots Using a rollover snapshot feature here is an architecture overview.
02:23
Flash cover is powered by coal. The city can be deployed with just few clicks. A brand new flash recover deployment creates flash recover file systems for data, metadata and configuration data on the flash plate and it comes with the ransomware protection feature enabled an existing flash Our deployments require an upgrade to flash cover as and after the cluster upgrades successfully it will start to migrate the media
02:50
data and contribution data on the local note to the flash recover file systems created on flash plate. Once the migration is complete, you can perform the safe mode, snapshots on demand. Eventually a four note flashy cover cluster will create a total of 36 Flash cover file systems on the flash plate.
03:08
For detailed information of this integration, please refer to the white paper on ransomware protection with flash recover s to successfully implement the solution. You need to install or upgrade the flash cluster with flash. Whereas software version to gain access to the snapshot feature, you need to contact to the pure support team to enable the safe mode on the flash plate.
03:32
Performing the safe mode snapshots to create a useful and consistent safe mode snapshot of the backup copies, metadata and contribution data. It is important requires the services on the cohesive cluster. For now, a manual intervention is required to perform the safe mode snapshot this is the eight notes flashing. Our cluster where I will be performing the same mood snapshot and recovery test logging to the
03:57
assets console to one of the flash recover nodes using support user access and to create the snapshot issue, the cluster create snapshot command. The cluster validates the create snapshot command and process it. The create snapshot operation stops the background cluster services and performs an internal backup of the local node data to the appropriate flashback file system.
04:20
The cluster will create the safe mode snapshot on the flash plate automatically. During this process. The cluster services are shut off and hence the rs Cli command land will be paused. A standard on snapshot helper tool is available to check on the status of the snapshot creation and probe for errors.
04:39
Once the snapshot creation on the flash bread is successful. The cluster services will start again upon successful completion of the safe mode snapshot creation process and info alert is generated on the coast city alert section. This is how simple it is to protect your backup data in point in time. Safe mode snapshots which can be recovered to the original file system.
05:03
In case of ransomware attacks, save more recovery process When faced with the ransomware attack or any other data loss events. Safe mode snapshot simplifies the restore process safe more recovery can be executed in the following two scenarios. One data recovery on an existing cluster that is in case of accidental deletes or natural
05:25
disaster. Second in case of ransomware attack, that compromises the cluster configuration and backup data and it needs full recovery of the cluster. First and foremost step is to contact the pure storage support and co history support. When an attack is identified, the authorized administrator must contact cohesively support
05:44
and pure support right away cohesively support will administer the recovery process on the cohesive cluster and pure story support can change the retention on snapshot settings to ensure your data remains available during recovery and will assist in restoring the snapshot on flash blade. This is especially important if you need to recover from all the snapshots.
06:06
Safe mode recovery on existing cluster, identify the snapshot rajan that needs to be restored and work with co history support to assist and restore process. The restore needs to be executed while logging to the ssh console on one of the nodes of the cluster. The rs cli cluster snapshot restore command initiates the snapshot recovery This example shows the restore snapshot command executed on
06:30
one of the test clusters on a previously created snapshot. The cluster validate the restore snapshot commands and start the pre restore operations on the cluster. It stops the cluster services and then wait for the snapshots to be restored on flash blade. During the restore process, the cluster services are stopped and the command line is
06:49
paused. The standalone snapshot helper tool can be used to check the restore snapshot progress after the status becomes waiting for the filesystem snapshot for restore on flash plate. The Pure storage support rep will restore the snapshot of the affected flash recover file systems on flash blade.
07:07
The restore snapshot operation monitors the file systems. Once it detects that all the file systems are restored from the specified version on flash blade. The operation will continue. That is restoring the local node conflagration data from the restored file systems and automatically restoring the cluster services.
07:28
Once the operation companies, the user will receive a restore snapshot succeeded alert from the cluster. A complete disaster recovery in order to perform a complete disaster recovery from safe mode snapshots on a new cluster. You need to rebuild the original flash recover cluster with the same version with applicable patches and the hardware configuration on which the snapshots were performed.
07:50
To rebuild the cluster, please reach out to the cohesive support team, record the cluster ID information for older cluster as this will be required to perform the recovery after the cohesive cluster is built. Do not register the flash played to the cluster that is. Do not perform the flash our storage deployment identify which snapshot version needs to be restored to and work with the call history
08:14
support team. To assist in the restore process. The Cody city support team will lead an access to one of the notes I P M A console to initiate the recovery process. The restore process is initiated using the rs Cli cluster, restore snapshot command which requires the flash plate management I.
08:33
P address and the token I. D. Once the cluster validates the restore command, it starts processing the restore operation on the cluster that is stopping the cluster services and waiting for the snapshots to be restored on the flash blade. During the restore process, the cluster services are stopped and the rs cli command
08:53
line is paused. A snapshot helper tool can be used to check the restore snapshot progress after the restore status becomes waiting for the file systems. For restore the pure storage support rep restores the snapshot of the affected file system on flash blade. The restore snapshot operation, monitors of file systems and once it detects that all the
09:16
file systems are restored, the operation will continue. There is restoring them not local data from the restored file systems on the flash blade and then automatically restarting the cluster services, this is how you can successfully recover the cluster backup data from point in time. Clean safe mode snapshots to conclude this demonstration, I would like to highlight a few
09:40
key business value values of implementing flash recover as a backup solution for data protection needs A flash. Our cluster can be deployed under 30 minutes. You can achieve a linear scale in performance, going from four notes, 2/8 notes and to 12 notes. Flash cover is easy to set up, manage and upgrade a full recovery of the cluster and data
10:02
in case of ransom, er, attack can take just a few minutes. Thanks for watching this video.