How to manually make vertica to fail

Document ID:  TEC1091418
Last Modified Date:  07/04/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Performance Management

Releases

  • CA Performance Management:Release:2.8
  • CA Performance Management:Release:3.0
  • CA Performance Management:Release:3.1
  • CA Performance Management:Release:2.7.0

Components

  • CA PERFORMANCE CENTER:CAPRFC
Introduction:

It may be needed to check the database backup and restore if something goes wrong with vertica.

Question:

How to manually corrupt vertica database so that client can test if a restore is working good.

Environment:
CAPC 2.6 through 3.1
Answer:

Deleting data and catalog folder would almost always mean that a full/scratch recovery would occur. If you just want to see recovery work, there are easier ways - like deleting only some of the ROS containers in data folder or even a single .gt file in a container.

You also have a high chance of corrupting data on some nodes if you manually kill a node (simulate hardware/OS crash) while there is data loading in progress.

P.S. Making suggestions how to corrupt Vertica DB is contrary to what we usually advise, so please test on a TEST/QA DB that does not contain important data and always have a full backup handy!

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >