Symptoms

Avamar does not save Cloud Tiering configuration. "Enable Cloud Tier" (Server tab -> Edit Data Domain System -> Tiering) can be selected in the Avamar UI once the Cloud Unit is provided, but the configuration is not retained. Note: This article applies even if the data-movement policy was configured manually.

Cause

If a data-movement policy has already been configured for the Avamar on the Data Domain (DD), it prevents the Management Console Server (MCS) and the ddr_info file from being updated on Avamar.

Resolution

Reset the data-movement policy on Data Domain, and enable cloud tiering on Avamar using the UI: 1. On the Avamar grid, verify that the "ddrmaint read-ddr-info" command shows that the "ltr" fields are empty: admin@avamar:~/#: ddrmaint read-ddr-info <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <avamar dpnid="1447xxxxxx" type="default" version="5"> <datadomain count="1"> <ddrconfig client-map-default="true" dd-cert-chain="" ddos-version="6.1.2.6-600545" ddrcreatetime="145xxxxxxx" ddrid="73F47DDDC33FAxxxxxxxxxxxxxxxxxxxxxxxx" gsan-backup-target-default="false" hostname="dd01host.aa.com" index="1" instant-access-limit="32" ipv4-hostname="dd01host.aa.com" ipv6-hostname="" ltr-dmp-id="" ltr_cloud_unit_name="" ltr_mtree_name="" max-streams="1400" max-streams-for-cp-backup="0" modelno="DD9500" password="o/m5V4IwfZlxxxxxxxxxxx==" serialno="FLAxxxxxxxxxx" token="AQAEwUCbd39f8qijHLT39xxxxxxxxxxxxxxxxxxx==" username="ddboost"> <snmp community="ImxnDthItWxxxxxxxxxxxxx=="> <ports getter-setter="161" trap="163"> </ports> </snmp> <client-map> </client-map> </ddrconfig> </datadomain> </avamar> 2. (Optional) On the Avamar grid, verify that MCS has already created a data-movement policy on Data Domain: admin@avamar:~/#: grep -i ltr /usr/local/avamar/var/mc/server_log/mcserver.log.* INFO: get LTR cloud unit(s)... INFO: 1 LTR cloud unit(s) found, spent (486 ms) INFO: create LTR data movement policy... at com.avamar.mc.datadomain.DataDomainService.updateLTR(DataDomainService.java:1431) INFO: create LTR data movement policy spent (279 ms) 3. On the Data Domain, verify that the data-movement policy is still present: ddboost@ddhostname# data-movement policy show Mtree Target(Tier/Unit Name) Policy Value ------------------------------------------- -------------------------------- -------------------- ----------- /data/col1/avamar-1447xxxxxxx Cloud/emcbackup app-managed enabled ------------------------------------------- -------------------------------- -------------------- ----------- 4. Reset the data-movement policy for the Avamar mtree: ddboost@ddhostname# data-movement policy reset app-managed mtrees /data/col1/avamar-1447xxxxxx The data-movement "app-managed" policy for Mtree(s) "/data/col1/avamar-1447xxxxxx" is reset to "none". 5. Enable Cloud Tiering using the Avamar UI. (Server tab > Edit Data Domain System > Tiering.) 6. Back on the Avamar grid, confirm that the "ddrmaint read-ddr-info" command output now shows populated "ltr" fields: admin@avamar:~/#: ddrmaint read-ddr-info <avamar dpnid="1447xxxxxx" type="default" version="5"> <datadomain count="1"> <ddrconfig client-map-default="true" dd-cert-chain="" ddos-version="6.1.2.6-600545" ddrcreatetime="145xxxxxxx" ddrid="73F47DDDC33FAxxxxxxxxxxxxxxxxxxxxxxxx" gsan-backup-target-default="false" hostname="dd01host.aa.com" index="1" instant-access-limit="32" ipv4-hostname="dd01host.aa.com" ipv6-hostname="" ltr-dmp-id="%2Fdata%2Fcol1%2Favamar-1447xxxxxx%3Aemcbackup" ltr_cloud_unit_name="emcbackup" ltr_mtree_name="/data/col1/avamar-1447xxxxxx" max-streams="1400" max-streams-for-cp-backup="0" modelno="DD9500" password="o/m5V4IwfZlxxxxxxxxxxx==" serialno="FLAxxxxxxxxxx" token="AQAEwUCbd39f8qijHLT39xxxxxxxxxxxxxxxxxxx==" username="ddboost"> <snmp community="ImxnDthItWxxxxxxxxxxxxx=="> <ports getter-setter="161" trap="163"> </ports> </snmp> <client-map> </client-map> </ddrconfig> </datadomain> </avamar>

Support Cases