---
title: "Upgrade from Database 5.0.0 or 5.1.0 to 5.3.0"
description: "Upgrade Aerospike Database from 5.0.0 or 5.1.0 to 5.3.0 when using XDR bin projection functionality."
---

# Upgrade from Database 5.0.0 or 5.1.0 to 5.3.0

> For the complete documentation index see: [llms.txt](https://aerospike.com/docs/llms.txt)
> 
> All documentation pages available in markdown.

Upgrading from 5.0.0 or 5.1.0 to 5.3.0 or newer - if using the XDR bin projection functionality using the [`ship-only-specified-bins`](https://aerospike.com/docs/database/reference/config#xdr__ship-only-specified-bins) configuration parameter.

When using the XDR bin projection feature in versions 5.0.0 or 5.1.0, upgrading to version 5.3.0 or above requires first upgrading to version **5.2**.

**Contents**

-   [Upgrade to 5.2](#upgrade-to-520)
-   [Upgrade to 5.3.0 or newer](#upgrade-to-530-or-newer)

## Upgrade to 5.2.0

Upgrade to 5.2.0 with the [`bin-policy only-specified`](https://aerospike.com/docs/database/reference/config#xdr__bin-policy) configuration (replacing the `ship-only-specified-bins`configuration). Setting the [`bin-policy only-specified`](https://aerospike.com/docs/database/reference/config#xdr__bin-policy) configuration parameter in version 5.2.0 will keep doing the bin projection, but without causing bin metadata to be stored and avoid interference with 5.0/5.1 nodes still in the cluster during the rolling upgrade.

## Upgrade to 5.3.0 or newer

Once the 5.2.0 upgrade is complete, upgrade to 5.3.0 or newer and update the configuration as follows:

-   Update the [`bin-policy`](https://aerospike.com/docs/database/reference/config#xdr__bin-policy) from `only-specified` to `changed-and-specified` (or whatever desired).

::: note
While running a mixed version cluster the 5.2.0 nodes will understand the bin metadata the 5.3.0 or newer nodes send.
:::