# Restoring Knowledge Articles with Vault

### What is Salesforce Knowledge and why do you need it? <a href="#what-is-salesforce-knowledge-and-why-do-you-need-it" id="what-is-salesforce-knowledge-and-why-do-you-need-it"></a>

Salesforce Knowledge allows you to build a Knowledge Base for storing and managing documentation to service your internal agents, website visitors, partners, and customers.

Users can create and manage a knowledge base with your company information and securely share it when and where it's needed. Salesforce Knowledge helps you establish a self-service model for your customers to solve their queries, leading to case deflection and increasing customer satisfaction.

Vault can restore/replicate knowledge data `Knowledge__kav` records with rich text and large image files.

### Point to Consider <a href="#point-to-consider" id="point-to-consider"></a>

* Knowledge Articles should exist in your Salesforce org.
* Restoring of the KAV (knowledge objects) to be always processed in a different job.
* To restore/replicate other metadata/data objects, run a different job, including all the required metadata and data objects.

### Process <a href="#process" id="process"></a>

To restore Knowledge data objects with Vault, follow the below steps:

> Similar steps are to be followed for **replicating** KAV objects in Vault. Replicate the KAV objects by navigating to the `Replicate` module.

1. Login to your **Vault** account and navigate to the **`Restore`** module.
2. In the **`Restore`** page, select your **`Salesforce org`** configured with KAV objects.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7ts5TjxC0bksHjXqkALH%2Fimage.png?alt=media&#x26;token=202deb22-840d-4dc3-ab3e-421fd2f15d43" alt=""><figcaption></figcaption></figure>

3. Select the **`Restore Source`** from the dropdown.
4. Click on **`Restore Now`**.
5. On the next screen, choose the **`backup configuration`** from the dropdown if not auto-selected.
6. Click on **`Get Details`**. Based on the **`restore source`** and **`configuration`** selection, the backup configured list will get displayed.
7. Select the **backups** from the list for restoration.
8. Click on **`Selective Restore`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FtfMHIbddLLih0Wg8EkQx%2Fimage.png?alt=media&#x26;token=bd9c4535-b8e6-447b-9d3e-38051562eef6" alt=""><figcaption></figcaption></figure>

9. Go to the **`Data`** tab and slide the toggle bar to the right side for **`KAV Object only`**. This will allow viewing the KAV-related objects only in the list.
10. Select the **KAV object**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FsirHXBf8gfTS1py8XZTg%2Fimage.png?alt=media&#x26;token=51b46d1f-f313-4b05-8b73-5045bc654618" alt=""><figcaption></figcaption></figure>

11. You also have multiple configurations to choose from under the **`Data`** tab:
    * **`Schema:`** This option will allow you to view all the child objects for your selected kav object.
    * **`Selected Records:`** This will allow you to choose the records for your object. By default, all the records available in the objects will be auto-selected.
    * **`Selected Fields:`** This will allow you to select the fields for your object. By default, all the fields available in the objects will be auto-selected.
12. Click on **`Trigger Restore`**.

{% hint style="info" %}
**Point to Note:**

If you choose to deploy KAV objects along with other metadata/data objects, the Vault application will not allow you to continue further. The message below pops up:&#x20;

`Ensure only KAV object is selected for this restore job. KAV is a special object and can be processed only in separate job. To restore other data objects/ metadata run another job including all the required metadata and data objects.`
{% endhint %}

13. On the **`Selected Data To Restore`** screen, enter the **label** of your choice or leave the auto-generated default label.
14. Specify the **batch size** for components to retrieve records.
15. Choose the recipients from the **`Email notification`** dropdown who should receive notifications whenever the action is performed. The currently logged-in recipient will automatically be checked by default.
16. Select the criteria for performing the restore and click on **`Restore Now`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FFfuxabOEX94xJJU5d2y6%2Fimage.png?alt=media&#x26;token=3a80268f-3732-4385-933e-1f955c2a5bb4" alt="" width="563"><figcaption></figcaption></figure>

17. You'll be taken to the **`Restore Summary`** screen, which will display the status of the recently triggered restore activity.
18. Once the restore operation is successfully triggered, the status changes to **`Ready to link kav to case`**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7tKK9hpL02x9uqCsISvN%2Fimage.png?alt=media&#x26;token=914f1d9f-5bf9-476e-a211-3ec104771279" alt=""><figcaption></figcaption></figure>

19. Under the **`Actions`** tab, you can perform additional operations:
    * For an ongoing restore operation, you can **abort** the process in between using the **`Abort`**![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7iI5zQczTVUxOdNoeNT6%2Fimage.png?alt=media\&token=edbc4ab0-286e-4ca6-8871-e9dcc1805dbc)icon.
    * View the **restore summary report** using![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FWh69mBtTku8ivij2NSiP%2Fimage.png?alt=media\&token=481aaac7-c699-49a6-bcc5-ce2e5296da1b)icon.
    * View the **restore log report** using![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FuXUIQ6fsxRAVk3P2gymP%2Fimage.png?alt=media\&token=70335a94-b207-4717-8af5-73a8c2855962)icon.
    * Trigger **linking kav to case** using![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F1HUUKUdSUA7TudpGf6eN%2Fimage.png?alt=media\&token=cec31979-ff55-4b7e-8f88-75377ff2aa6b)icon.

{% hint style="info" %}
**Points to Note:**

* To ensure successful linking, do confirm that the **kav records** for linking are in `Published` status in Salesforce.
* Once the Kav record is successfully linked, the job status changes to complete (![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fmgf39w84GC2PCidzTqIn%2Fimage.png?alt=media\&token=98cfb573-1b6d-4e3d-887f-8f9cbafaf047)) state.
* The **`trigger`** (![](https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FcavLn1t3CExeYVYAEkQj%2Fimage.png?alt=media\&token=07916650-ecfe-4a1a-b3bc-8e2e2bc3bf1b)) button will not be available; henceforth, linking kav to case is triggered.
  {% endhint %}
