Basics – Getting Data Protection Central Installed and Running

March 9, 2020 4 Comments

Data Protection Central is, to me, a great mechanism for keeping your eye on your data protection environment. If you’re in charge of backups within your environment, you shouldn’t need to spend an hour reviewing backup completion reports each morning. That’s what Data Protection Central is for. It’s not there for your end-users, or your manager, it’s there for you, as the data protection administrator. It’s about saving you time, every day.

DPC Main Dashboard

DPC isn’t a big, juggernaut of an interface. If you don’t have any changes to make in your data protection environment, you should be able to log in, see 100% success on backups and replication, then get on with your day. But if something has failed overnight, you should also be able to drill in, issue restarts, jump into administrative interfaces if necessary.

DPC is free. If you’re running NetWorker, Avamar, Data Domain, PowerProtect Data manager, or any combination thereof within your environment, you can download and install DPC. There’s no licensing to fuss with, you just install DPC and start attaching your servers.

And that’s what I want to show you in these videos. Now here’s the thing: they’re all simple and short videos! What you should see from these is that if you’ve got half an hour to spare, you could get DPC up and running in your environment!

Deploying Data Protection Central

DPC Deployment

Adding NetWorker to a DPC Server

Adding a NetWorker Server to DPC

Adding Avamar to a DPC Server

Adding an Avamar Server to DPC

Adding a Data Domain to a DPC Server

Adding a Data Domain to DPC

Adding a PowerProtect Data Manager System to a DPC Server

Adding PowerProtect Data Manager to DPC

Integrating Data Protection Advisor with DPC

Integrating Data Protection Advisor with DPC

Wrapping Up

So you see, getting DPC up and running in your environment won’t take any time at all. So what are you waiting for? Here’s a link to the support site so you can get started!

Related posts:

  1. Looking Back on a Decade of Data Protection
  2. Pool size and deduplication
  3. 2015 – that’s a wrap!
  4. Reflections on 2018

4 thoughts on “Basics – Getting Data Protection Central Installed and Running”

  1. Hi,

    Thanks for this detailed blog, Very helpful.
    I looked and decided to give a try but i do not have vmware environment . I decided to go for .jar file installation on my SUse linux server.
    Have you tried the .jar file installation and would you give some lines for non-ova installation. I got confirmation that only SLES12-SP2 is supported and 550 GB disk space needed. I am not sure about FS layout and and error logs when .jar file is executed.
    I was told by my EMC counterpart that it needs 2 disks like OVA. Please assist here with FS layout and installation.

    Appreciate your help.

    my install failed with below error.

    Unpacking emc-dpc-19.2.0-7.bin…
    Exception in thread “main” java.lang.RuntimeException: Cannot run program “/tmp/bin2jar2660436617682030497.tmp/emc-dpc-19.2.0-7.bin”: error=13, Permission denied
    at com.emc.dpsg.mojo.makeself.jarexec.Exe2JarExec.innerMain(Exe2JarExec.java:62)
    at com.emc.dpsg.mojo.makeself.jarexec.Exe2JarExec.main(Exe2JarExec.java:72)
    Caused by: java.io.IOException: Cannot run program “/tmp/bin2jar2660436617682030497.tmp/emc-dpc-19.2.0-7.bin”: error=13, Permission denied
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
    at com.emc.dpsg.mojo.makeself.jarexec.Exe2JarExec.innerMain(Exe2JarExec.java:56)
    … 1 more
    Caused by: java.io.IOException: error=13, Permission denied
    at java.lang.UNIXProcess.forkAndExec(Native Method)
    at java.lang.UNIXProcess.(UNIXProcess.java:247)
    at java.lang.ProcessImpl.start(ProcessImpl.java:134)
    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
    … 2 more

    Reply

    1. Hi, here’s an output of df, and mount:

      admin@andoria:~><strong> df -h</strong>
Filesystem      Size  Used Avail Use% Mounted on
devtmpfs        3.9G     0  3.9G   0% /dev
tmpfs           3.9G     0  3.9G   0% /dev/shm
tmpfs           3.9G   41M  3.9G   2% /run
tmpfs           3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda3        20G  2.0G   17G  11% /
/dev/sda2       194M   54M  127M  30% /boot
/dev/sda5        30G   46M   28G   1% /logs
/dev/sdb1       489G  387M  488G   1% /data01
tmpfs           787M     0  787M   0% /run/user/500

admin@andoria:~> <strong>mount</strong>
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
devtmpfs on /dev type devtmpfs (rw,nosuid,size=4016052k,nr_inodes=1004013,mode=755)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
/dev/sda3 on / type ext4 (rw,relatime,data=ordered)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=32,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/sda2 on /boot type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered)
/dev/sda5 on /logs type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered)
/dev/sda5 on /var/log/dpc type ext4 (rw,nosuid,nodev,noexec,relatime,data=ordered)
/dev/sdb1 on /data01 type xfs (rw,relatime,attr2,inode64,noquota)
/dev/sdb1 on /var/lib/dpc type xfs (rw,relatime,attr2,inode64,noquota)
tmpfs on /run/user/500 type tmpfs (rw,nosuid,nodev,relatime,size=805280k,mode=700,uid=500,gid=500)
      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.