Quantcast
Channel: VMware Communities: Message List - Backup & Recovery
Viewing all articles
Browse latest Browse all 5692

Re: How to freeing up space in VDP with the capacity health check limit reached?

$
0
0

Thanks again. But it looks I was caught in a trap.


Checkpoints are validating but old:

 

root@vm-vdp:~/#: cplist

cp.20131202100237 Mon Dec  2 11:02:37 2013   valid rol ---  nodes   1/1 stripes   1916

cp.20131202103632 Mon Dec  2 11:36:32 2013   valid rol ---  nodes   1/1 stripes   1916

 

 

No hfscheck yet (since last reboot?) and gsan status is degraded:

 

root@vm-vdp:~/#: status.dpn|less

Čt pro  5 15:26:42 CET 2013  [vm-vdp.racom.cz] Thu Dec  5 14:26:42 2013 UTC (Initialized Wed Nov

  7 19:55:37 2012 UTC)

Node   IP Address     Version   State   Runlevel  Srvr+Root+User Dis Suspend Load UsedMB Errlen

%Full   Percent Full and Stripe Status by Disk

0.0   192.168.20.17 6.1.81-130  ONLINE fullaccess mhpu+0hpu+0000   2 false   0.28 3594 27424967

62.6%  62%(onl:644) 62%(onl:648) 62%(onl:642)

Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable

 

All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0000)

System-Status: ok

Access-Status: admin

 

No checkpoint yet

No GC yet

No hfscheck yet

 

Maintenance windows scheduler capacity profile is active.

  WARNING: Scheduler is WAITING TO START until Fri Dec  6 08:00:00 2013 CET.

  Next backup window start time: Fri Dec  6 20:00:00 2013 CET

  Next blackout window start time: Fri Dec  6 08:00:00 2013 CET

  Next maintenance window start time: Fri Dec  6 16:00:00 2013 CET

 

root@vm-vdp:~/#: dpnctl status

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: gsan status: degraded

dpnctl: INFO: MCS status: up.

dpnctl: INFO: Backup scheduler status: down.

dpnctl: INFO: axionfs status: up.

dpnctl: INFO: Maintenance windows scheduler status: enabled.

dpnctl: INFO: Unattended startup status: enabled.

 

 

I've tried to get GC in active state along to reply-5 but it looks like used capacity 96.4% is too high. I suppose GC not to start in the morning, am I right?

 

root@vm-vdp:~/#: avmaint config --ava | grep diskrep disk

  disknocreate="90"

  disknocp="96"

  disknogc="85"

  disknoflush="94"

  diskwarning="50"

  diskreadonly="65"

  disknormaldelta="2"

  freespaceunbalancedisk0="30"

  diskfull="30"

  diskfulldelta="5"

  balancelocaldisks="true"

 

root@vm-vdp:~/#: avmaint config disknogc=97  --ava

2013/12/05-13:55:10.94029 [avmaint]  ERROR: <0949> Command failed because these config values do not meet the following criteria:

2013/12/05-13:55:10.94040 [avmaint]  ERROR: <0001> 0 < diskwarning(50) < diskreadonly(65) < disknogc(97) < disknocreate(90) < disknoflush(94) < disknocp(96) < 100

ERROR: avmaint: config: server_exception(MSG_ERR_INVALID_PARAMETERS)

 

root@vm-vdp:~/#: avmaint config disknocp=99  --ava

2013/12/05-13:55:41.90331 [avmaint]  ERROR: <0949> Command failed because these config values do not meet the following criteria:

2013/12/05-13:55:41.90342 [avmaint]  ERROR: <0001> disknocp(99) <= diskfulldelta(5 -> 96.5) < diskfull(30 -> 97.0) < poolnocreate(20 -> 98.0) < 100

ERROR: avmaint: config: server_exception(MSG_ERR_INVALID_PARAMETERS)


Viewing all articles
Browse latest Browse all 5692

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>