Please enter your query or select one of the above categories.
All entries (Page 1 / 6)
Can I use SpaceObServer in a Cluster environment?
You can use SpaceObServer in a clustered server environment by installing it on one of the nodes. That means that a node fail over is not handled, but scheduled scans will be started automatically after the node is running again. You can also install SpaceObServer on both nodes and in case of a fail over you simply have to change the observing server for all scanned roots. You can do this by selecting "Set Observing Server" in the context menu of the "Configure Scans" dialog ("Scan > Configure Scans > Expert Settings"). Leave the observing service blank to allow any service to perform the scheduled scans. Then you should deactivate the scan services ("Tools > Options > Service") on all but one of the nodes in the cluster and activate it again on a node fail over.
I tried to uninstall SpaceObServer to install the latest version, but the file "SpaceObServerAgent.exe" was not removed and the installer cannot replace it. How can I remove the file to install the latest version?
The file "SpaceObServerAgent.exe" is the SpaceObServer scan service, called "SpaceObServer Agent". Normally this service automatically shot down before un-/reinstallation. To avoid this problem please do the following: 1. Ensure that the service "SpaceObServer Agent" is stopped. 2. Use your Windows task manager to ensure that there is no process"SpaceObServerAgent.exe" running (tab "Processes"). If so, use the "Terminate process" button to kill this process. 3. Ensure that your windows event log is closed (The Windows event log could hold a handle to this file).
SpaceObServer doesn't start to scan a specified directory. What's the problem?
There could be reasons for this issue:
1. Is the system service "SpaceObServer Agent" started? The "SpaceObServer Agent" processes all scans of directories. If thisservice is stopped or paused, no scan can be processed.
2. Is theselected directory on a network drive? You cancustomize the login of SpaceObServer Agent within the installation ofSpaceObServer (username, domain and password). If you do not enter a valid useraccount the login is set to the local system account. That may cause problemswhile scanning network drives. To fix this problem please switch the servicelog on to a user account with sufficient access rights (See: "How can Iswitch the login...").
3. Do you use"Windows Authentication" for the database login? If you usethis option ("Tools > Options > Database > Login info") andyou switched the login of the system service SpaceObServer Agent to a specifieduser account, this user must have read and write access on the selecteddatabase.If it isnot possible to give the user access rights to this database, please do not usethe Windows Authentication for the database access. Use a valid database useraccount instead.
4. Does the"Observing Server" exists and is an SpaceObServer Agent running onthis machine? If the"Observing Server" is set (not blank) for a root directory, only thisserver will execute scans for this directory, no matter from which client thescan was triggered or scheduled. If for any reason (e.g. a rename of theserver) this machine is not found or no SpaceObServer Agent is running on thismachine, the scan will not be executed. You can configure the Observing Serverform within the context menu of the Configure Scans dialog (sub menu "ExpertSettings"). If none ofthe above applies, please check the column "Last Error" in the"Configure Scans" dialog and the Windows Event Log for furtherinformation and error messages. Please include this information if you contactus, together with the type and version of database software you are using.
Will SpaceObserver take advantage of multiple CPUs if available (both the client and the agent)?I 've installed it on a multi-core Windows 2008 64-bit server, and I am seeing the client is only utilizing 100% of one of the CPUs, and not any of the others that are available.
Both, the user interfaceand the scan service of SpaceObServer, are designed multithreaded. That meansthat they "could" take advantage of a multi core environment.I say "could"because for the scans of the service and the reports of the user interface the bottleneckis always/mostly the database. Means that most the time the SpaceObServerprocesses/threads are waiting for results of the database. That 's why you will mostlikely not see that any of the SpaceObServer processes holds over 50% on a dualcore machine. Anyway, using a multi coremachine with SpaceObServer makes sense, because you are running both, theservice and the user interface at the same time. In case you are using a localdatabase, the multi core system is very useful.
I 'm about to upgrade SpaceObServer from 3.2 to the latest version. Can you tell me if the upgrade needs an OS restart? If so I need to make plans accordingly...Also, is there a database upgrade performed in the upgrade? If so, is there a particular order I need to do this in?
The upgrade ofSpaceObServer to a higher version does not require an restart of your operationsystem.In some upgrades there aredatabase updates done (normally only in major updates), but they do all runautomatically within the installation and the first start of the software.Note: Do not use multipleinstances of SpaceObServer (SpaceObServer Clients) of different major versionswith the same database. This could cause errors in the user interface and thescan service!
Does SpaceObserver support SQL Server 2008 as Database Platform? I only found a reference to SQL Server 2000 on your website.
SpaceObServer supports MS SQL Server 2000-2012.
When I shutdown a server with space observer installed..The information scanned of the server is erased from the DB?
Of course not. The data is persistent in the database. SpaceObServer will not delete data, it will only update data.
I would suggest putting the following information in the manual for the next release of SpaceObServer.Calculating MD5 checksums for duplication checking will modify the access date on all files.This seems obvious in retrospect but I didn 't think of it until after I turned it on.
We will take care in V4.2 that the last access date is no longer changed when SpaceObServer calculates the MD5 checksum. Thanks for pointing our attention to this matter.
Is it possible to "move " the history information to a new server name? We recently retired some of our older file servers and the new server have different names. The directory structure (i.e., \dept\dept_name\users) stayed the same.
In the context menu of the Configure Scans dialog (Scan > ConfigureScans) there is an entry "Change Scan Location" in the sub menu "ExpertSettings". Use this option to change the selected directory path, when thedirectory was moved.
I currently have SpaceObserver 3.1.1 installed and want to upgrade to 4.02Is it an easy process?Can I upgrade or is it a re-install?Does the upgrade use the same SQL Database, i.e. upgraded during the install, or does it need a new DB?Do I upgrade the client or the server agents first?
To upgrade youSpaceObServer instance to a newer version (no matter if minor or major update),you just have to install the new version over the existing installation.All the user settings andthe connected database will be kept.We recommend installing theSpaceObServer instances before the SpaceObServer Remote Administration Clients. Note: Please ensure that you are using the same versions of SpaceObServer andRemote Administration Clients.
Hello,we use SpaceObServer and are satisfied with its functions and features. However, our management would like to have an automatically generated report from which they could address obsolete data and mark them for archiving/deleting from production shares. I found out that there is something like OLE Automation available through custom scripting. So I would like to ask you if you could kindly provide us with some already finished and working scripts if they are available?
SpaceObServerships with some OLE Automation example scripts, showing most of the automationfunctionality. Please find this scripts in your Windows start menu entry"OLE Automation Examples" (entry "SpaceObServer") or in theinstallation sub directory "demos". For more detailed documentation of the OLE Automation interface, please take alook at the SpaceObServer help file, Section "OLE Automation".
I believe there is a problem with how Create Date is reported.SpaceObServer reports the same Create Date as my file 's file system create date (seen in Explorer) when it initially scans the file system. If the file is moved my Create Date does not change on my file system. However, when SpaceObServer scans the file system after the file move it will report the file as being Created when it is scanned and entered into the database. This does not match the Create date of the file on the file system.
When youmove a file on your hard disk, SpaceObServer will notice this file as newfiles. To show correct size growth in the SpaceObServer "History" wecannot use the reported creation date of the moved files, because in this casethe file will be reported twice in the SpaceObServer "History".