dpnctl info backup scheduler status down

Dpnctl info backup scheduler status down code#
Dpnctl info backup scheduler status down windows#

Next maintenance window start time: Fri Nov 4 08:00:00 2016 df -hįilesystem Size Used Avail Use% Mounted on Next backup window start time: Thu Nov 3 20:00:00 2016 KST The maintenance window is currently running.

Dpnctl info backup scheduler status down windows#

Maintenance windows scheduler capacity profile is active. Last GC: finished Thu Nov 3 12:32:44 2016 after 00m 30s > recovered 0.00 KB (MSG_ERR_DISKFULL) System ID: reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0000)Ĭheckpoint failed with result MSG_ERR_DISKFULL : cp.20161103033244 started Thu Nov 3 12:33:14 2016 ended Thu Nov 3 12:33:14 2016, completed 0 of 3497 stripes Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)ĭpnctl: INFO: Backup scheduler status: up.ĭpnctl: INFO: Maintenance windows scheduler status: enabled.ĭpnctl: INFO: Unattended startup status: enabled. Here are some of my VDP state, anyone can help? Thank you so dpnctl status From the logs I can see it might caused by disk full, but even I cleared all my restore points, disk space won't be reclaimed because appliance status is 'admin'. VDP Backup schedule is not running, because that appliance state is 'admin' status.

Unable To Connect VDP To vCenter: 'login returned.

vSphere Replication Jobs Fail Due to NFC_NO_MEMORY.

VDP Cannot Connect To Web Client 'MIME media type.

Unable To Send Scheduled Email Reports In VDP 'com.

SRM Service Crashes Due To CR/LF Conversion.

VDP Tomcat Service Crashes With 'line 1, column 0.

# ls -lh /space/avamar/var/em/server_data/prefs/ List out the permissions on the file using: # cp -p /tmp/emback/var/em/server_data/prefs/emserver.xml /space/avamar/var/em/server_data/prefs/ĥ. Copy to restored file to the actual location using: # mv /space/avamar/var/em/server_data/prefs/emserver.xml /space/avamar/var/em/server_data/prefs/Ĥ. Rename the older emserver.xml file using:

Dpnctl info backup scheduler status down code#

# avtar -x -labelnum=209 -path=/EM_BACKUPS -target=/tmp/embackĪ successful restore would end with a similar snippet:Īvtar Info : Restoring backup to directory '/tmp/emback'Īvtar Info : Restored 55.55 KB from selection(s) with 55.55 KB in 10 files, 6 directoriesĪvtar Info : Restored 55.55 KB in 0.01 minutes: 306.5 MB/hour (56,489 files/hour)Īvtar Info : Finished at 21:26:53 GST, Elapsed time: 0000h:00m:00sĪvtar Info : Not sending wrapup anywhere.Īvtar Info : Command completed (1 warning, exit code 0: success)ģ. Next, we will choose a label number and then restore the EM Flush to a temp directory. 08:00:04 210 57K Linux /usr/local/avamar var/em/server_data 08:00:08 211 57K Linux /usr/local/avamar var/em/server_data 08:00:05 212 57K Linux /usr/local/avamar var/em/server_data 08:00:05 213 57K Linux /usr/local/avamar var/em/server_data # avtar -backups -path=/EM_BACKUPS -count=5 | lessĭate Time Seq Label Size Plugin Working directory Targets List out the latest 5 available EM backups using: So, it looks like the emserver.xml file had been corrupted and we just need to restore this particular file from a previous EM Flush.ġ. etc/profile /usr/local/avamar/bin/emwebapp.sh -start' - exit status 255 If we ran the alternative command to start the service, it would fail to and the dpnctl.log would have the similar Error trace.Ģ-17:11:42 syntax error at line 1, column 0, byte 0:Ģ-17:11:42 Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)Ģ-17:11:42 tomcatctl: ERROR: problem running command ' &.

Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)Īt /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linux-thread-multi/XML/Parser.pm line 187 Syntax error at line 1, column 0, byte 0:

When we tried to restart the tomcat service using the below command as the ' root' user of VDP it used to fail: The core services seemed to be fine, it was just the EM tomcat that was unresponsive. Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)ĭpnctl: INFO: Backup scheduler status: down.ĭpnctl: INFO: Maintenance windows scheduler status: enabled.ĭpnctl: INFO: Unattended startup status: enabled.ĭpnctl: INFO: While working with one of my colleague the last day, there was an issue where the tomcat service would not start dpnctl status