Loading...
Loading...
New nodes are added to an existing Avamar grid, but stripe balancing makes little to no progress. After several weeks, the number of stripes on the new nodes is still lower than the original nodes. Below is an example output from status.dpn command, showing the stripe numbers on each node partition: Thu Sep 14 17:25:37 CEST 2017 [avamar-server . customer . com] Thu Sep 14 15:25:37 2017 UTC (Initialized Tue Aug 27 07:32:25 2013 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.255.3 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 1 false 0.36 31869 12707315 54.4% 54%(onl:3661) 54%(onl:3690) 54%(onl:3701) 0.1 192.168.255.4 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.49 31713 14168999 54.4% 54%(onl:3702) 54%(onl:3691) 54%(onl:3671) 0.2 192.168.255.5 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 1.05 31853 12673034 54.3% 54%(onl:3674) 54%(onl:3666) 54%(onl:3697) 0.3 192.168.255.6 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.45 31603 12991585 54.3% 54%(onl:3702) 54%(onl:3671) 54%(onl:3692) 0.4 192.168.255.7 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 1 false 0.47 31865 12004871 54.4% 54%(onl:3656) 54%(onl:3678) 54%(onl:3715) 0.5 192.168.255.8 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 1 false 0.30 31631 8245977 54.4% 54%(onl:3805) 54%(onl:3611) 54%(onl:3623) 0.6 192.168.255.9 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.92 31855 7928968 54.3% 54%(onl:3587) 54%(onl:3846) 54%(onl:3608) 0.7 192.168.255.10 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 1 false 0.14 31370 597225 5.0% 4%( onl:700 ) 5%( onl:785 ) 5%( onl:789 ) <-- NEWLY ADDED NODE 0.8 192.168.255.11 7.2.0-401 ONLINE fullaccess mhpu+0hpu+0hpu 0 false 0.36 31424 548361 4.6% 4%( onl:877 ) 4%( onl:679 ) 4%( onl:659 ) <-- NEWLY ADDED NODE Srvr+Root+User Modes = migrate + hfswriteable + persistwriteable + useraccntwriteable (In this example, 0.7 and 0.8 are the new nodes.)
Balancing runs during the maintenance window when the grid is idle. If backups or incoming replication is running during the maintenance window, balancing cannot run.
Take one of the following actions: 1. Configure balancing as recommended in the Solve procedure. -- or -- 2. Review the grid schedule to determine if backups or incoming replication data is written to the Avamar server during the maintenance window. This can be done by running the most recent version of the sched.sh script or by running the health check script ( proactive_check.pl ) with the --sched flag. See the following knowledge articles for more information: Avamar: How to Run the proactive_check.pl health check script on an Avamar Server. Avamar: How to use sched.sh to check historical backup, replication and maintenance activities . -- or -- 3. Review the activity monitor for incoming backup activity during the hours of the day when maintenance runs. If the maintenance window clashes, reconfigure backups to end before the maintenance window or move the maintenance window to another time of day.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.