Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell PowerProtect Cyber Recovery 19.13 Product Guide

PDF

Preparing the production-side Avamar system

Optionally, create a checkpoint before performing a Secure Copy policy operation.

About this task

If you have already created a checkpoint, there is no need to perform the following procedure.

CAUTION:Ensure that a checkpoint validation (hfscheck) has verified the integrity of the checkpoint.

Steps

  1. Log in to the production Avamar server as root user and run a checkpoint operation. This step might take some time.
    1. Type su admin -c "mcserver.sh --flush":
      root@ave-03:~/#: su admin -c "mcserver.sh --flush"
      === BEGIN === check.mcs (preflush)
      check.mcs                        passed
      === PASS === check.mcs PASSED OVERALL (preflush)
      Flushing Administrator Server...
      Administrator Server flushed.
    2. Type mccli checkpoint create:
      root@ave-03:~/#: mccli checkpoint create
      0,22624,Starting to create a server checkpoint.
       
      root@ave-03:~/#: mccli checkpoint show
      0,23000,CLI command completed successfully.
      Tag               Time                    Validated Deletable
      ----------------- ----------------------- --------- ---------
      cp.20180316130025 2018-03-16 09:00:25 EDT Validated No
      cp.20180316130301 2018-03-16 09:03:01 EDT           No
      cp.20180316151143 2018-03-16 11:11:43 EDT           No
    3. To ensure that a checkpoint validation (hfscheck) has verified the integrity of the checkpoint, type mccli checkpoint validate --cptag=<cp tag name>:
      root@ave-03:~/#: mccli checkpoint validate --cptag=cp.20180316151143
      0,22612,Starting to validate a server checkpoint.
      Attribute Value
      --------- -----------------
      tag       cp.20180316151143
      type      Full
       
       
      root@ave-03:~/#: mccli checkpoint show
      0,23000,CLI command completed successfully.
      Tag               Time                    Validated Deletable
      ----------------- ----------------------- --------- ---------
      cp.20180316130301 2018-03-16 09:03:01 EDT           No
      cp.20180316151143 2018-03-16 11:11:43 EDT Validated No
  2. On the Cyber Recovery host, run a Secure Copy policy action for the DD MTree.
  3. Validate the size of the production DD system MTree that was replicated is the same as the replicated MTree on the destination DD system and the Cyber Recovery MTree (for example: /data/col1/avamar-1560177494-repl).
    1. Type mtree list, as shown in the following code example:
      sysadmin@crmgmthost# mtree list
      Name                                                 Pre-Comp (GiB)   Status
      --------------------------------------------------   --------------   -------
      /data/col1/avamar-1560177494-repl                                  4.2   RO/RD
      /data/col1/backup                                               0.0   RW
      /data/col1/cr-policy-5d5ad66394422f0001ced229-repo              0.0   RW/RLGE
      /data/col1/cr-policy-5d5ad69994422f0001ced22a-repo              4.2   RW/RLGE
      /data/col1/nw02-repl                                            0.0   RO/RD
      --------------------------------------------------   --------------   -------
       D    : Deleted
       Q    : Quota Defined
       RO   : Read Only
       RW   : Read Write
       RD   : Replication Destination
       RLGE : Retention-Lock Governance Enabled
       RLGD : Retention-Lock Governance Disabled
       RLCE : Retention-Lock Compliance Enabled
    2. Verify that the production-, target-, and policy-replicated MTrees are the same.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\