Volume Inventory


The tool you need to create a Volume Inventory is the web based RemoteManager. RemoteManager is accessible via https on port 8009: https://Server_or_IP:8009 (if that does not work, you can use http://Server_or_IP:8008 but be careful, your password will be transferred in clear text then)

Login with Admin rights to the RemoteManger (on OES2 Linux with a LUM User e.g. Admin.YourOrg)
NetWare: Manage Server → Volumes → info2.gif → Volume Inventory Report → Create a new report
Linux: View File System → Volume Inventory → Volume Link

If there are some Java Security Messages accept them.

Now the Inventory Report will be created. Depending to your Volume size this can take from a few minutes to some hours. I noticed that the Report on Linux is much faster than on NetWare. You should run the report during off-peak hours.

Thats it!

Now you have a detailed view with the following Graphs:

  • File Types (By Bytes In Use)

  • File Type (By File Count)

  • File Owners (By Bytes In Use)

  • File Owners (By File Count)

  • Last Moified Times (By Bytes In Use)

  • Last Moified Times (By File Count)

  • Last Access Times (By Bytes In Use)

  • Last Access Times (By File Count)

  • File Creation Times (By Bytes In Use)

  • File Creation Times (By File Count)

  • File Size Chart (By Bytes In Use)

  • File Size Chart (By File Count)

You can use the following tables to cut and paste it into your favorite spreadsheet program:

  • Last Modified Range

  • Last Accessed Range

  • Creation Time Range

  • File Size Range

  • File Owner

  • File Extension

All lists are hyperlinked – a file list will be created if you choose one.

Last but not least with "Custom report" customized reports can be created!

With a few clicks you gain a detailed overview of how old, which size and which types your overeater's are. With the detailed owner report you know who is responsible for the data (on Linux the users must be LUM-enabled to have a owner overview!)

( … and if you do that the first time on your Server, I would almost bet that you wonder how old your data is, and how much space the *.jpg use



How To-Best Practice
Comment List