Data Domain DD400 Series, User Manual

Page: 121 / 300

Chapter 9: File System Management 83
Clean Operations
Using an asterisk (*) as a wild card to display compression for more than one file returns the same
information as above for each file, but in a single line for each file. The
g_comp and l_comp in each
line is short for global and local compression. The display ends with a summary that has the same
format for total figures as with a file system. For example:
# filesys show compression /backup/*.tar
/backup/usr.tar: bytes: 3,930,583,040, g_comp: 53,484,389,
l_comp: 29,214,049, meta-data: 27,439,680, bytes/storage_used:
69.4
/backup/var.tar: bytes: 2,733,137,920, g_comp: 1,941,043,800,
l_comp: 1,103,938,251, meta-data: 31,147,968,
bytes/storage_used: 2.4
Total files: 2, bytes/storage_used: 5.6
Original Bytes: 6,663,720,960
Globally Compressed (g_comp): 1,994,528,189
Locally Compressed (l_comp): 1,133,152,300
Meta-data: 58,587,648
Clean Operations
The
filesys clean
operation reclaims physical storage used by deleted objects in the Data
Domain file system. Use the
clean
operations of the
filesys
command to manually start a
clean
operation, change the schedule that automatically runs the operation, or check the status of
the operation.
The default settings for
clean
operations are:
•
A run time of Tuesday at 6 a.m. (
tue 0600
).
•
25% of the restorer’s total data capacity.
•
A maximum of 48 hours run time.
•
A network-bandwidth throttle of 50.
Note Cleaning 25% of the space available for data on a restorer that is not busy with other tasks
generally takes two to three hours when the cleaning throttle is set to 100. Different types of
data, a busy system, and throttle settings below 100 all can extend the time needed. During
cleaning, the speed of backup and restore operations may be affected.
The
clean
operation does not run on a replica restorer.