Is the Garbage collection completing successfully everyday ?

All maintenace activity is fine except GC I got

Also this is the out put for status.dpn

root@IDKU-AVE08:~/#: status.dpn
Tue Dec 11 09:51:20 EET 2012  Tue Dec 11 07:51:20 2012 UTC (Initialized Sun Dec  2 11:41:12 2012 UTC)
Node   IP Address     Version   State   Runlevel  SrvrRootUser Dis Suspend Load UsedMB Errlen  %Full   Percent Full and Stripe Status by Disk
0.0    172.16.5.114  6.1.0-402  ONLINE fullaccess mhpu0hpu0000   3 false   0.9     0 5803   351622  19.4%  19%(onl:231)
SrvrRootUser Modes = migrate + hfswriteable + persistwriteable + useraccntwrit                                                                              eable

All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu0hpu0000)
System-Status: ok
Access-Status: admin

Last checkpoint: cp.20121210104054 finished Mon Dec 10 12:41:19 2012 after 00m 2                                                                              5s (OK)

Last GC: finished Tue Dec 11 09:49:34 2012 after 03m 00s >> recovered 0.00 KB (M                                                                              SG_ERR_DISKFULL)
Last hfscheck: finished Mon Dec 10 11:22:08 2012 after 13m 10s >> checked 230 of                                                                               230 stripes (OK)

Maintenance windows scheduler capacity profile is active.
  The blackout window is currently running.
  Currently running task(s): script
  Next backup window start time: Tue Dec 11 20:00:00 2012 EET
  Next blackout window start time: Wed Dec 12 08:00:00 2012 EET
  Next maintenance window start time: Tue Dec 11 11:00:00 2012 EET

the out put for capacity.sh

root@IDKU-AVE08:~/#: capacity.sh
Date          New Data #BU       Removed #GC    Net Change
--

Top 3 High Change Clients:
--

Total for all clients                   137898 mb      100.0%
 * idkuevs01.egyptianlng.com             103714 mb       75.2%*
  IDKUVMSQL01_UCtr78HWiuWulxm7t3SlNQ      20348 mb       14.8%
  IDKUVMSQL01                             9180 mb        6.7%

I want to delete * idkuevs01.egyptianlng.com 103714 mb 75.2% from storage. I deleted the client from GUI Admin console but it seems it is still in the storage.*

Please advice.

Regards,

Ahmed Salah

Garbage collection is failing and hence, client backup is not getting deleted from the storage.

Please run :

avmaint nodelist | grep fs-percent

avmaint config --ava | grep disknogc

If the first command's output shows utilization more than 'disknogc'(disknogc should be 85 by default) , then please open a Service Request with Avamar support.

Please refer to this article :

http://solutions.emc.com/EMCSolutionView.asp?id=esg118578&usertype=C

Dear Sandeep,

below is the output from the two commands, My problem is in the OS capacity it is 97.1% how could I reduce this capacity and get back to normal.

Also the GC will stop after 85% threshold.

root@IDKU-AVE08:~/#: avmaint nodelist | grep fs-percent
fs-percent-full="97.1"

root@IDKU-AVE08:~/#: avmaint config --ava | grep disknogc
disknogc="85"

root@IDKU-AVE08:~/#: dpnctl status
Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: gsan status: degraded
dpnctl: INFO: MCS status: up.
dpnctl: INFO: EMS status: up.
dpnctl: INFO: Backup scheduler status: up.
dpnctl: INFO: dtlt status: up.
dpnctl: INFO: Maintenance windows scheduler status: enabled.
dpnctl: INFO: Unattended startup status: enabled.

Please advice,

I went through the articale you sent it is very nice and it clarifide the cause of the "MSG_ERR_DISKFULL" error but what should I do to free up OS space I have no support right now.

Please advice.

Thanks

Ahmed Salah

I don't know if you are still having issues with this or not but OS capacity will be recovered during maintenance cycles -- specifically when hfscheck completes successfully. A successful hfscheck will allow older checkpoints to roll off and the space consumed by checkpoint overhead (the sum of the differences between the oldest checkpoint and the current version of the data) to be recovered.

I would recommend allowing the maintenance scheduler to take care of all running maintenance. Running maintenance manually has non-obvious pitfalls that may cause serious problems on the system.