Condusiv Technologies Blog

Condusiv Technologies Blog

Blogging @Condusiv

The Condusiv blog shares insight into the issues surrounding system and application performance—and how I/O optimization software is breaking new ground in solving those issues.

Up Around the Bend

by Michael 30. June 2008 19:28
Microsoft is around the corner from an exciting new release, perhaps as compelling as Windows Server 2008 itself - the contender to VMware's hypervisor dominance (ESX). Hyper-V (a Windows Server 2008 server role) has wrapped up and is ready to go to market (RTM - or Release To Manufacturing). Diskeeper Corporation has worked closely with Microsoft to fully support Hyper-V from early on. That technology alliance includes the recent Microsoft announcement that Diskeeper was one of the first three software vendors to certify their software for Hyper-V (the other software vendors were IBM and Symantec). In the coming months it will culminate in advanced Diskeeper performance functionality announced by Microsoft several years back. As a long time Microsoft Gold partner, we believe that Microsoft is providing an excellent option for corporation's looking to save power and space, ease provisioning efforts, and achieve full hardware utlilization through virtualization. Also around the bend is the RTM for a new 2009 iteration of a Diskeeper software release - broadly available in late July/early August. Keep an eye open for the official release!

Tags:

General

Installing Diskeeper on Server Core

by Michael 19. June 2008 18:11
Here are the basic steps to installing Diskeeper on a Windows 2008 Server Core system and how you can access the full Diskeeper UI remotely. 1. Turn off the Firewall on the Server Core system. (The default Firewall settings on the Server Core system will not allow remote installation or external file copies to occur, so you will need to disable the Firewall temporarily. We will enable it after the installation has completed.) a. Logon to the Server Core system and on the command prompt window execute the below command to disable the firewall "C:\>netsh firewall set opmode disable" - You can use netsh set machine command to remotely connect to the Server Core system. The Diskeeper User Manual contains the specific ports/protocols/process names necessary for communications. These ports can be opened for Diskeeper, using netsh, in lieu of fully disabling the firewall, albeit temporarily, if there are any security considerations. 2. Install Diskeeper Administrator console on another (remote) system that supports .Net (preferably one that has an internet connection). a. Install/configure your database of choice. If you have internet connection you can easily download the free MSDE (SQL Lite) product. b. When complete, select the ‘Install Diskeeper’ option from the main page and follow the wizard to install Diskeeper on the Server Core system. c. On the ‘Select Diskeeper Edition option, select “Diskeeper 2008 Server” which is the default. d. On ‘Select Installation File’ menu section, select the button option ‘Specify or browse…’ which will have the included Diskeeper Server edition selected, then select the ‘Package Type’ you want to install , X86 or X64 and select ‘Next’ e. On next, use the default ‘Activate Silently and Automatically’ f. On next, select the machine name of the Server Core system. If the machine name does not show up in the network neighborhood display, you can add the IP address with the following steps: - Right click on the Domain name where the Server Core machines resides and select ‘Add Multiple Computers” - In the Computers to add list, enter in the IP address of the machine and select OK. - That IP address will now be available to select from g. Next it will ask you for a Username and Password for that Server Core machine. If it is not part of the domain, then you can permission type of ‘workgroup’ or ‘local admin’. h. Continue on with the wizard to complete the Installation. 3. After the Installation is complete, you can re-enable the firewall on the Server core machine with this command line: "C:\>netsh firewall set opmode enable" 5. Remote connect to Diskeeper on the Server Core system. a. From the system, with DK Admin, select the “Remote Control Diskeeper” option and follow the wizard to select the machine (Server Core System) to connect to Diskeeper on. This will connect you to the full UI.

Tags:

General

Access Time Graphs in the Diskeeper Analysis

by Michael 9. June 2008 13:51
After running a manual analysis, Diskeeper will open a new window with two tabs. The first is the Volume Map display and will show a visual depiction of File Performance or File Structure. The second tab provides the detailed data. It is separated into numerous sections; Recommendations, Health, Access Time, Statistics and Most Fragmented Files. A question we get on occasion is what the two bar graphs in the Access Time section represent. The graph labels tell you what is measured, Fragmented Files or All Files, but how does this relate to performance? The first graph is probably best viewed as a "Worst Case" scenario. That graph shows how long it takes to access all the fragmented files, and only those fragmented files. As you can imagine that probably almost never happens. One case where this might apply is a database volume that contains only those small handful of potentially all-fragmented database files. The second graph shows how long it takes to read all the files on the volume, both fragmented and contiguous. This is likely closer to a "Best Case" scenario. Unlike the Worst Case scenario, this has a bit more real-world applicability. One such example is running an anti-virus/spyware scan or a volume file backup, as those processes read the entire volume. Typically you'll find a performance gain somewhere in between the two graphs. As fragmentation affects the files you use (read/write/delete) you will likely be accessing/writing a good percentage of fragmented files, relative to all the files on a volume. Keep in mind that the Access Times are good general indicators, but aren't designed to watch exactly how you (or your users) use the PC/Server.

Tags:

General

Diskeeper and Server Core

by Michael 5. June 2008 19:07
Here are the steps to running Diskeeper 2008 on a Sever Core Environment. Note for test purposes, you need DK Admin to remotely connect to the Diskeeper GUI on the Server Core system. 1. You will need Diskeeper 2008 Server (or EnterpriseServer) and a Diskeeper 2008 Administrator version. 2. Install Diskeeper on the Server Core system. a. From another system, you will need to copy over the setup.exe and the *.dal (license file) to the Server Core system. To do this, you will need to map the C: volume on the Server Core system from another system. We found you will need to disable the firewall on the Server Core system, so it will allow you to map the Server Core volume. Here are the steps b. Logon to the Server Core system and on the command prompt window execute the below command to disable the firewall (we will enable it back later) - "C:\>netsh firewall set opmode disable" c. From the other Windows system (non-server core), map the C: volume on the Server Core system d. From the other Windows system, copy the setup and *.dal file from the Diskeeper Server Enterprise kit to the C: volume on the Server Core system. e. On the Server Core system, on the command prompt windows, set the folder to where the setup.exe and *.dal files were copied to and execute setup.exe. This will install Diskeeper on the Server Core system. 3. Install Diskeeper Admin on the other remote system a. On the other system, install Diskeeper 2008 Administrator. b. In the folder that DK Admin was install at (“\Program Files\Diskeeper Corporation\Diskeeper Administrator”), you will find this file “DkClient_XPSP2.bat”. This file will setup the specific firewall settings to allow DK Admin to communicate with DK Server Enterprise on the Windows Server Core system. Of course, you can just leave the firewall disabled and that would work too. c. From the other Windows system, copy the “DkClient_XPSP2.bat” file to the C: volume on the Server Core system. d. On the Server Core system, on the command prompt windows, re-enable the Firewall with the following command. - "C:\>netsh firewall set opmode enable" e. On the Server Core system, on the command prompt windows, execute the “DkClient_XPSP2.bat” file that you had copied over. 4. Remote connect to Diskeeper on the Server Core system. a. On the other system, start up Diskeeper Administrator and run through the setup process, which includes setting up an SQL express engine if needed. After setup is complete, you should get the following DK Admin GUI. b. Select the “Remote Control Diskeeper” option and connect to the Diskeeper on the Server Core system.

Tags:

General

Month List

Calendar

<<  November 2017  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
27282930123
45678910

View posts in large calendar