The GSR Collector can generate anomaly reports to identify issues that might need to be addressed before you create storage policies. The anomaly report, which is generated through data collected by the GSR Collector, lists potential problems according to seven different categories:
Tab Name |
Explanation |
---|---|
Orphan Candidates |
Lists home directories that are not currently assigned to a User object in eDirectory. |
|
Lists cases where a username and the associated home directory name do not match. This is frequently the case when a User object is renamed, but the corresponding home directory is not. |
Path Overlap |
List home directories that are parent paths of other user home directories. For example, a user’s home directory attribute in eDirectory is set to VOL1:\HOME\USERS instead of VOL1:\HOME\USERS\JBANKS. This is a potential conflict because if you move an object that resides in the first path, it moves all users below the user. |
Duplicate Storage Pointer |
Lists users that have identical home directory paths. |
Missing Primary Folders |
Lists users who do not have assigned home directories. |
|
Lists users that have auxiliary storage assigned, but the storage is not yet created. |
Objects Not Managed |
Lists users in eDirectory whose storage is presently not managed through Novell Storage Manager. |
In NSMAdmin, click the
tab.Click
.Click the tab for the category you want to view.
At this point, because none of your existing users are being managed through Novell Storage Manager, each user in eDirectory should be listed when you click the
tab. Additionally, you might notice other potential problems by viewing data categorized through the other tabs.