Step: 1 Have account for portal site:
CB 2.x will need to be manage by external https://console.dpccloud.com portal site.
It’s not just registration, its whole mgmt. Note that there is not data (meta-data or actual data) movement from CBA to portal site.
Note: https://console.dpccloud.com has timeout issues without any visual error. Its best to logoff and login after sometime, else it gives un-necessary, un-related errors.
CB online help page: https://console.dpccloud.com/#/help/homepage/
Step 2: CB setup:
CB (physical or virtual) has control shell env, where once power-up, needs to configure IP, netmask, DNS, FQDN, NTP and proxy. Note that proxy is very important to communicate to external DPC portal site. Also it shouldn’t have any ID/password as most enterprise customer won’t allow internet access without that.
Make sure following three sites are in customer proxy white list.
Ensure following site is updated in customer DNS with both forward and reverse lookup…….
api.dpccloud.com. 300 IN A 184.108.40.206
or update CB /etc/hosts file with 220.127.116.11 api.dpccloud.com
If you want to hack it locally in CB itself than it's in /opt/maginatics/active/mgt_console/resources/templates/hosts.erb
Step 3: CB Registration:
Once step 2 finish, it needs to register CB via CLI which automatically send request to portal site. Here challenge is to ensure two-way communication is set properly. Customer needs to update gateway, proxy, firewall and SSL to allow communication else register will fail.
If customer has CA sign Cert and communication intercepted by customer proxy then you need to have root access to CB to update crt file which may need to open SR. Append customer crt file in /etc/ssl/cert/ca-authorities.crt
Here is CB CLI details https://community.emc.com/docs/DOC-53550
Step 4: Setup ECS profile:
Once you pass through registration successfully, you will see CBA in portal site. Next step will be to add ECS profile.
Make sure there is no proxy intercepting communication between CB and ECS.
Test following from CB…….
diagnostics blobstore-cli "--provider s3 –endpoint https:/<ECS FQDN>:9021 --identity <bucket owner> --credential <bucket credential> --trust-all-certs"
diagnostics blobstore-cli "--provider s3 –endpoint https://<ECS FQDN>:9021 --identity <bucket owner> --credential <bucket credential>"
If you see SSL or cert error than use http://ecs fqdn:9020 instead of https.
diagnostics blobstore-cli "--provider s3 –endpoint http://<ECS FQDN>:9020 --identity <bucket owner> --credential <bucket credential>"
Once blobstore successful to get S3 communication with ECS go ahead and set storage profile in console.dpccloud.com
Imp: Uncheck cache from profile which is enabled by default. For CB writing to ECS, its not recommended to use cache.
If cache profile already pushed and need to remove, CB needs to reset to factory default. Don’t interrupt profile or factory reset else it needs to reinstall OS.
It may need to upgrade CB itself from DPCCLOUD for NBU environment. Refer to CB online help for upgrade page: https://console.dpccloud.com/#/help/homepage/
Step 5: Setup Agent
Once profile push or set in DPC Cloud portal, install agent and detect share folder to configure as target storage for backup software. If agent successfully able to detect and mount magfs, its ready to configure backup software.
Use full UNC path as \\cloudboost.emc.com\cloud
If you face any issue in CB, either use https://<CB fqdn>:4444/support
Or from CB terminal tail -f /var/log/rails/maginatics.log
If still unable to resolve issues engage CB support……email@example.com