Clustering Access-based Enumeration (ABE)

 

I Saw this newsgroup post how to do this and what to do.

Remember ABE needs to setup on ALL Cluster nodes !!

First We set up the Access-based Enumeration (ABE) on the nodes.

Access-based Enumeration (ABE)  Access-based Enumeration (ABE) Access-based Enumeration (ABE) Access-based Enumeration (ABE) Access-based Enumeration (ABE) Access-based Enumeration (ABE)

Do this on all the nodes !!

First We need to create a File share that We will use for Access-based Enumeration (ABE)

Start the Cluadmin and create New fileshare

Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare

Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare

Now that the File share is in place we move on to the next step.

In the Cluster admin

Microsoft Clustering

Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare

Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare

Access-based Enumeration (ABE) Fileshare

So Now that the Cluster Resources are online lets check the status of the file shares, first the share that runs on the cluster but without the abe

clip_image030  As you can see the box in not checked

The ABE created file share

Access-based Enumeration (ABE) Fileshare Access-based Enumeration (ABE) Fileshare  ABE is enabled

Below are some Items about the Cmd tool

Syntax

abecmd [/enable | /disable] [/server <ServerName>] {/all | <ShareName>}

Parameter Description

/enable Enables ABE on the shared specified resource or on all shared resources.

/disable Disables ABE on the shared specified resource or on all shared resources.

/server <ServerName>

Apply the action (making ABE enabled or not enabled) for shared resources on a server instead of the local computer.

/all Apply the action (making ABE enabled or not enabled) for all shared resources.

Note: If /all and a ShareName is specified, the ShareName is ignored.

<ShareName> Designates the shared resource to which ABE will be applied or removed.

Note: Either /all or ShareName must be specified.

Performance Sheets

ABE not enabled

1 Chart comparing folder access times with ABE not enabled and enabled, in turn

ABE enabled

2 Detail of the first comparative chart focusing on smaller folders, filtered for disk reading

The data in Figure 72shows the same information as the data in Figure 1, narrowed down to smaller directories: the chart only shows information for directories with 500 to 16,000 files.

Note that accessing the shared folder can sometimes be slower with ABE not enable. The server cache was primed before these test runs, enumerating the shared folders with ABE not enabled in order to read things like security profiles from the hard disk. This was done in order not to skew the test results: reading information from the hard disk is much more time-consuming than enumerating a shared folder with ABE enabled (as evidenced by Runs 1 and 2, both of which still had to read some information from the hard disk). Most importantly, with less than 15,000 files in the shared folder, access time for a server with ABE enabled and not enabled is indistinguishable—less than one second. While enabling ABE can certainly affect access time for particularly large folders, it represents a near trivial performance loss for smaller folders.

Technorati Tags: ,,,,

Posted February 9, 2009 by Robert Smit in System Center

Tagged with

  • Tag