- #DPNCTL INFO BACKUP SCHEDULER STATUS DOWN MANUAL#
- #DPNCTL INFO BACKUP SCHEDULER STATUS DOWN FULL#
- #DPNCTL INFO BACKUP SCHEDULER STATUS DOWN SOFTWARE#
- #DPNCTL INFO BACKUP SCHEDULER STATUS DOWN WINDOWS#
Here is the files, it will show you tail -f /tmp/dpnctl-mcs-start-output-4109
#DPNCTL INFO BACKUP SCHEDULER STATUS DOWN WINDOWS#
STOP MCS (Its always suggested that you run dpnctl status first before stopping the MCS to check any services is dpnctl stop mcsĪfter MCS Stopped, check the dpnctl statusĭpnctl: INFO: Backup scheduler status: down.ĭpnctl: INFO: Maintenance windows scheduler status: enabled.ĭpnctl: INFO: ĭpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-4109ĭuring the start back MCS, there's a line shows to tail one file to monitor the progress. I have made some changes on configurations on mcserver.xml files /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml and after the changes i'll need to restart MCS to make sure it takes affect.Īs usual, you will need to login as ADMIN, or in my case i login as root and then change to Admin - ssh-add ~admin/.ssh/admin_key The MCS contacts the client’s avagent process and starts an avtar to perform a backup or recovery.
#DPNCTL INFO BACKUP SCHEDULER STATUS DOWN SOFTWARE#
Avamar agents are platform-specific software processes that run on the client and communicate with the Management Console Server (MCS) and any plug-ins installed on The MCS interacts with the client avagent to start backup and recovery. When you start the Avamar GUI you are interacting with the MCS The MCS also runs the server-side processes used by the Avamar Administrator graphical management console which is serviced by JAVA. The last bit was using xfs_growfs on /dev/sdb1 and /dev/sdd1 to fix wrong size of nodes.Įdit: I think that checkpoint rollback and waiting was enough.The Management Console Server (MCS) provides centralized administration (scheduling, monitoring, and management) for the Avamar server.
#DPNCTL INFO BACKUP SCHEDULER STATUS DOWN MANUAL#
Several times rebooting and running manual checkpoint including unmounting disks and running xfs_check helped at last. Thare was a good checkpoint, good hfscheck and good gc. On Monday it has magically repaired itself. At this point I have up and let the system run for a weekend.Ħ. Only checkpoint succeeded, hfscheck and gc failed with MSG_DISK_FULL.ĥ. Run manual checkpoint, integrity check and garbage collection. Expand storage! Wizard went successfully. Same errors when trying to set values to 99%.Ĥ.
Modify configuration threshold amounts to allow garbage collection run (as described above). Rollback to earlier checkpoint, run manual checkpoint, integrity check and garbage collection. Delete big backups, run manual checkpoint, integrity check and garbage collection.
#DPNCTL INFO BACKUP SCHEDULER STATUS DOWN FULL#
I do not know what exactly helped but here is a full list of my actions (add reboots as needed):ġ. It have had ended up with nodes full at 98, 97 and 98 % respectively. One unlucky day I have fed a couple of OLAP VMs to VDP and it choked failing to deduplicate properly. Here goes the sad story with happy end about VDP 6.1.2.19. I suppose GC not to start in the morning, am I avmaint config -ava | grep diskrep avmaint config disknogc=97 -avaĥ-13:55:10.94029 ERROR: Command failed because these config values do not meet the following criteria:ĥ-13:55:10.94040 ERROR: 0 Command failed because these config values do not meet the following criteria:ĥ-13:55:41.90342 ERROR: disknocp(99) 96.5) 97.0) 98.0) < 100ĮRROR: avmaint: config: server_exception(MSG_ERR_INVALID_PARAMETERS) I've tried to get GC in active state along to reply-5 but it looks like used capacity 96.4% is too high. 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. Next maintenance window start time: Fri Dec 6 16:00:00 2013 dpnctl status Next blackout window start time: Fri Dec 6 08:00:00 2013 CET Next backup window start time: Fri Dec 6 20:00:00 2013 CET WARNING: Scheduler is WAITING TO START until Fri Dec 6 08:00:00 2013 CET. Maintenance windows scheduler capacity profile is active. Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteableĪll reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0000) Node IP Address Version State Runlevel Srvr+Root+User Dis Suspend Load UsedMB Errlen No hfscheck yet (since last reboot?) and gsan status is status.dpn|less
0 kommentar(er)
