LAN Storage Discovery considerations
Creation Date: April 01, 2008
Revision Date: April 01, 2008
Product: DS‑Client
Summary
The LAN Storage Discovery process can be disruptive. The reason is because DS-Client must connect to each target share, read the files in the share, and prepare a signature for each file to report on common files, largest file sizes, file types, etc.
Considerations & Recommendations
The following considerations and recommendations will help you when using the LAN Storage Discovery Tool:
• To avoid interruptions to normal work flow, schedule LAN Discovery to run after business hours and set an End Time for the schedule.
Shares that have been recently scanned will not be in priority sequence for scanning. Only shares that have not been scanned will receive priority for the scanning process when the schedule is triggered again.
• It is recommended that you prepare a special Domain Administrator account that can access all the shares that need to be scanned. This will simplify the configuration of credentials required on the DS-Client and thereby reduce the potential for connection errors during LAN Discovery (DS-Client will try to use each of the credentials provided to connect to each share it tries to discover).
If using a Domain Administrator account is not an option, then you can create the same local Administrator account (user name and password) on each server that will be scanned.
• After the share discovery process has finished, a share list that may include duplicate shares (shares that are included in other shares) is displayed. Retain the duplicate shares with the option disabled, since you do not need to scan those files twice.
• Ignoring small files can reduce the network load and the total time required for the Scan Shares process.
• Adjust the number of threads used to scan the shares. If the number is higher, the network will be busier, but the total time for the scan share process will be less than if the number of threads is smaller.
• If you have both Windows and Linux computers on the network, you should use two different DS-Clients to scan the shares: a Windows DS-Client to scan your Windows shares and a Linux DS-Client to scan your Unix shares.
During a Scan Shares process, the network and I/O of the scanned machines and the SQL Server where the DS-Client database resides will normally remain under a constant heavy load.