Hello and welcome to our Knowledge Base. Our experts provide answers to the most frequently asked questions of our customers. Start your information search here to find your answer quickly and easily.
Please enter your query or select one of the above categories.
All entries (Page 4 / 6)
DFS share does notrepresent a physical directory structure, so the options "Follow Mount Points and Symbolic Links" (Configure Scans / ScanOptions) must be set. DFS shares will be included in your scan reportautomatically then.
Anormal Windows 2000 system contains approx. 6000 to 100000 files in the WINDOWSdirectory alone. Printing these file names would result in a hard copy of90-120 pages – printing all file names on your disc would consume considerablymore paper.That’swhy SpaceObServer supports only the print-output for single, selected branches.But there’s a way to achieve a quite similar goal: you can copy a completeresult list for a drive to the clipboard and paste it into a spreadsheet or adatabase table for further processing. Please refer to the manual for furtherinformation on the subject "Copy files".
There are ways to reducethe occupied disk space as well for MS Access as for MS SQL Server:)" to reduce the occupied diskspace. SpaceObServer will perform this action at regular intervals.You may adjust the maximumsize of your "transaction protocol" of your MS SQL Server database by using theintegrated Enterprise Manager. Please do a right-click on the database andchoose the "Transaction protocol" tabfrom the "Properties" dialog.>/pPlease note: If you restrict the maximum file sizeof your database, you should not use the complete recovery model (Options/Recovery model), because youwon’t be able to make changes in the tables, if the maximum file size isreached.
If you usea MS SQL Server 2000 database, then only size limits set within the "EnterpriseManager" apply. By default, there are no size limits. MS Accessdatabase files are always restricted to a size of 2GB, largest table within canbe 1GB.For large file systems, a MS SQL Server 2000database is recommended.
The space used by the database depends on the number of files, the number of folders and the change rate of your files. Generally the database needs approx. 35 MB per 100.000 files. This is just a rule of thumb and is only valid if the database has been compressed recently. When you enable the MD5 checksums for your scans, the database size will increase about 1.5 MB per 100,000 files.
You can use this option to store the file system sizes of the selected directories in a different databaseon the connected SQL server. This way the collected information of different directory branches can be easily separated and the access permissions to these data are configurable through the database access rights.You do not have to reconnect to the second database to see the scanned information. SpaceObServer itself knows where to find it and opens a second connection to this database.This does not mean that the information of all scans are stored in the same tables, so you cannot use this option to merge information of multiple scans. So the answer to your questionis: No.
Open the Windows systemdialog "Services" under System/Maintenance/Administration/Services Look for the SpaceObServerListener in the list oflocal services and stop it.Right-click to the SpaceObServerListener and choose Properties from the context menu Choose the tab "Log-in" and change the setting under "Log-in as" from "Local account" to "Useraccount: ".Please enter now therequired log-in information (user name, password) for a user account withsufficient access rights on the network drive you want to scan.Restart the SpaceObServerListener service.>p If you use the Windows Authentication for securing your databaseconnection, please make sure that the logged in user account running theservice has sufficient access rights for the database.>p style= "margin-left: 36pt; text-indent: -18pt; "
By default, SpaceObServer ships with a SpaceObServer Embedded database (FDB file)SpaceObServer.fdb. You can change this connection by choosing "View / Options / Database" and selecting a new database connection. If you want to use a SQL server database for backing up data, your computer has to be connected to a server with a running MS SQL server. Alternatively, you could use a locally installed MS SQL Server as well. You will also need avalid user account for the database access (user name and password). A free MS SQL server version from Microsoft can be downloaded from the internet or you can use the MS SQL Server installer in SpaceObServer by choosing the corresponding link in "Options > Database".
Unfortunately,the Netware Client for Windows provides no information about compression rateor file ownership to the regular Windows API. So developers for Netware have toadd a special support functionality. We will provide this functionality in alater version of SpaceObServer. All the other functions are availableon Netware drives, too.
Windowsupdates the date of last access every time, when an application reads(read-only) a file. Because many back-up utilities or virus scanner do thisevery day at least once, the date of last access is often the same for manyfiles on your hard disk.
The date of last change andthe date of last access shown for a folder by SpaceObserver, is the latest datefound in this folder and in all subfolders. So there must be a file in thisfolder with a file date in the future. This happens frequently and is caused byvirus checks, system tests or client PC’s with incorrect system date. TheWindows explorer considers only file dates of files directly in this folder, soif a subfolder (or a file within a subfolder) will be altered, the parentfolder’s file date remains (incorrectly) unchanged.This issue only happens inolder versions of SpaceObServer. Version 3.x and later versions won’t show thisbehaviour.
The Windows"Properties" dialog in the Windows Explorer shows the physically allocatedspace on a drive and SpaceObServer shows the space occupied by all files withina given path.Beyond space that is needed for storing thefiles itself, additional space is used for storing management data like theFile Allocation Table of the file system or the boot sector. This is usually0.5-2% of the occupied space. Anotherpossibility is that you are using Software RAID, like Windows NT/2000 offers,which spreads the data with redundancy over several disks. These disks willappear as one logical volume and the failure of a single disk will not causeany data loss. But for storing the redundant information, additional space isneeded. If a networkdrive points only to a subfolder of a servers drive, the allocated space(correctly) reported by SpaceObServer may also be much smaller than thephysically allocated space on this drive reported by Windows Explorer, becausepossibly not the whole drive is accessible through the network. Anotherpossibility is that not all parts of the drive could be scanned due to securityrestrictions. So you will see only parts of a drive in the results. If the SpaceObServerListener system servicestarts with the default settings, you will always have appropriate rights toscan local drives, but this does not hold true for scanning network drives.