La magia del compellent!!

 

 

Compellent logro q es la virtualización de un disco, con esto y especialmente a mis amigos administradores de Exchange y base de datos nos olvidamos el concepto de raid, simplemente asignamos un disco a un server y compellent en base a un calco de i/o sabrá q es lo mejor para nuestros archivos.

En pocas palabras:

 

Sus fundamentos:

Su inteligencia se basa en división de discos por tiers, solo 3 en los cuales están dividos en base a su performance:

 

El primer dato se guarda en el tier 1 (discos de estado solido) todo configurado en raid (de gand performance hasta b ajar los tiers de menor performance), pasada unas 24 horas y dependiendo del acceso al dato, compelen mueve el dato viejo a un tier de menor performance pero a su ves mas económico, si existe una modificación el en dato el mismo es guardado en tier 1 hasta q caduque su tiempo y lo mueva a otro tier, en el caso de q el file sea accedido con mucha frecuencia es alojado en tier 1 permanentemente, del mismo modo si un dato accedido permanentemente en tier 3 , compellent moverá este a tier 1:

 

Todo esto lo hace en bloques de 2 mb (configurables) o sea, mi dato esta en toda la caja y aquí el concepto de “disco virtual”.

 

Leverages all other software features

 

Tight integration between automated tiered storage and other enterprise storage functionality drives the efficiency and performance of Data Progression. Thin provisioning optimizes disk utilization within the tiering environment. Users can provision virtual volumes of any size without setting aside physical space, and expand those volumes on demand. There are no RAID set capacity limitations or write performance penalties, as is common with other sub-LUN tiering solutions.

 

To help ensure ongoing write and read performance within the tiering scheme, Data Progression leverages Dell Compellent Replay (snapshot) technology. New data is written to Tier 1 to help provide the best write performance, yet change-only snapshots move to a lower tier and/or RAID level within 24 hours. Over time, the Replay engine prepares infrequently accessed blocks for downward migration through read-only conversion. This can free up 20 to 40 percent of space on Tier 1 while maintaining read performance. Users can take a high number of snapshots without affecting volume performance or capacity. And virtual pointers maintain continuity between all read and write blocks, despite distinct placement within the array.

 Así se ve desde el Compellent storage center (la interfaz de management):

 

 Thin Provisioning?????????????????????

La primera ves q escuche esto fue un que????, y la respuesta fue una promesa q puede ser verdad mas adelante, o sea:

Puedo asignar mas espacio del q tengo ¡!!!!!!!

Es bueno al momento del diseño, pero asegúrate q vas a tener todo el disco q prometiste, sino chau discos virtuales!!!!!

 

Mi interfaz:

 

 

Mi máximo físicamente es 4.5TB, vamos a crear un volumen de 5 teras entonces o varios q sumados den unos cuantos TB. 

Ffffffffffffffffffffffffffffffffffffffuuuuuuuuuuuuuuuuuuuuuaaaaaaaaaaaaaaaaaaaaaa

 

 

A los 32 gb de espacio libre no permite mas replays (snapshot ), a los 512MB libres pone la caja en modo read -only, mucho cuidadito con esto!!!!!

Claro q permite expandir volúmenes con 0 disrupción.

 

Data placement organization???????

 

Esto para del es “fast track”, y significa voy a poner los datos q mas acceso tienen en las pistas q están mas lejos del centro del disco ya q son las primeras y las mas rápidas de leer!!!!

 

Na, increíble!!!

Esto sumado a data progrecion loga la virtualización del dato, un claro ejemplo pongan sus bases de datos juntova sus logs, vana  ver q sus I/O no se verán afectados en lo mas mínimo, olvídense del concepto de disco, esto mueve el dato el bolkes de 2MB!!!!

Notas:Fast track es una licencia aparte.
Storage profile: es un feacture q puedo definir y en el cual puedo decir q tipo de raid quiero usar y si quiero q el dato se aloje permanentemente en tier 1, q dice compellent??, NO hagas eso!!! Deja q la inteligencia o la magia de compelent lo haga!!!!!!, salvo casos muy particulares.

 

Enterpice management client.

Si esto no es magia, escucho q cosa lo es!!!!!!!!!!

 

Vamos a crear un Volumen y se lo voy a pegar a Windows, todo desde el EM: 

 

 

Esta información la recolecta de un agente q corre en el server donde se esta asignando.

 

Mismo ejemplo con el disco M:

 

 

 

 http://www.compellent.com/Products/Software.aspx

 

 

Exchnage 2010 brick level backup

Este blog tiene excellence informacion de como podemos hacer un baclup brick lebel de nuestros servers de exchange.

PS command:

foreach ($i in (Get-Mailbox | Where {$_.ExchangeVersion.ExchangeBuild.Major -eq 14})) { New-MailboxExportRequest -Mailbox $i -FilePath "\\AZUA\Exports\${$i.Alias).pst" }

http://www.stevieg.org/2010/07/using-the-exchange-2010-sp1-mailbox-export-features-for-mass-exports-to-pst/

Para llamarlo desde un csv: 

foreach ($i in (Import-Csv .\exports.csv)) { New-MailboxExportRequest -Mailbox $i.Alias -FilePath "\\AZUA\Exports\$($i.Alias).pst" }

Exchnage 2010 brick level backup

Este blog tiene excelente informacion de como podemos hacer un baclup brick lebel de nuestros servers de exchange.

Clear the Auto-Complete Email Address Cache in Outlook

Clear the Auto-Complete Email Address Cache in Outlook

Outlook 2003 has an automatic completion for any email address that you try to type into the To or CC fields. This feature does not pull from the contacts or address book, because you may have tried to email somebody that wasn’t in your contact list, and it will still add that to the auto complete list.

The problem comes in when you put in a bad address, and then every time you go to type in the email address, the incorrect one appears in the auto complete list.

To fix this problem, there are two ways around this. The easiest way is this:

• Start typing in the address that shows up incorrectly.
• Hit the Down arrow key to select the auto completed address.
• Hit the Delete key to delete the auto complete address

The other way is by opening the profile folder and deleting the .nk2 file.

• Open up windows explorer, and paste the following into the address bar:

  %APPDATA%\Microsoft\Outlook

• Delete the Outlook.NK2 file that you find in this folder.

Message queue in Exchange 2007 (Author: Nathan Winters )

• Author: Nathan Winters (Excellent information)

Brief

This article investigates message queues in Exchange 2007. I begin by highlighting the differences in architecture between Exchange 2003 and 2007 in particular, discussing the fact that Exchange 2007 uses a queue database. I then discuss the new look queue viewer in Exchange 2007 and what it actually does! Finally I take a look at how the queue viewer is built on PowerShell and suggest some ways in which that could be useful!

Queue Theory

So where does this database fit in? Well as mentioned briefly above, all queue activity now occurs in a new ESE database. The main database file is called mail.que and by default can be found here:

C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue

Figure 6: Folder containing queue database files

The other files are in the locations as described below:

• Trn.chk - The checkpoint file.
• Trn.log - The current transaction log file.
• Trntmp.log - The next provisioned transaction log file that is created in advance.
• Trnnnn.log - Other transaction log files that are created when Trn.log reaches its maximum size.
• Trnres00001.jrs - The Reserve log file.
• Trnres00002.jrs - The Second Reserve log file.
• Temp.edb – Temp DB used to verify database schema on start-up.

You might wonder what happens with the logs in this scenario. Well, they are configured for circular logging with transaction logs being deleted after they have been committed.

Just before we move on to another area, it is worth stating how to move the queue databases. One important reason for moving the Queue DB and logs is performance. Another slightly less well known reason is that the drive on which the Queue DB and logs are stored must have 4GB or more free space otherwise the server will apply back pressure and start slowing the flow of messages!

When moving the DB, the usual rules for splitting transaction logs and DB files apply. To move the databases you must edit the EdgeTransport.exe.config file which by default is located at the location below and then stop and restart the msexchangetransport service:

C:\Program Files\Microsoft\Exchange Server\Bin\EdgeTransport.exe.config

The key thing to bear in mind before editing the config file is that the parent directory has the correct permissions as set up below; that way the directory will be created for you:

• Network Service: Full Control
• System: Full Control
• Administrators: Full Control

The relevant lines are shown below. To move the database, you should edit the line containing “QueueDatabasePath” and to move the logs, you should edit the line containing “QueueDatabaseLoggingPath”. You can see in Figure 7 that I have moved my DB and logs to H:

Figure 7: Editing the EdgeTransport.exe.config file (click to view a larger image)

Having looked at the Database it is now time to understand what it contains. There are various different queues:

• Submissions: Used by the categorizer to gather all messages that have to be resolved, routed, and processed by Transport agents.
• Poison Message: The poison message queue is a special queue that is used to isolate messages that are detected to be potentially harmful to the Exchange 2007 system after a server failure.
• Remote Delivery: Remote delivery queues hold messages that are being delivered to a remote server by using SMTP.
• Mailbox Delivery: The mailbox delivery queues hold messages that are being delivered to a mailbox server by using encrypted Exchange RPC.
• Unreachable Destination: Each transport server can have only one Unreachable queue. The Unreachable queue contains messages that cannot be routed to their destinations.
  

http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/exchange-2007-message-queues.html

Posters

http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17881

http://www.microsoft.com/download/en/confirmation.aspx?id=7002

http://www.microsoft.com/download/en/confirmation.aspx?id=3501

http://social.technet.microsoft.com/wiki/contents/articles/749.aspx

http://blogs.technet.com/b/schadinio/archive/2010/08/18/microsoft-technet-posters.aspx

http://blogs.msdn.com/b/cbowen/archive/2007/12/09/got-tech-posters.aspx

Get-RpcClientAccess

Use the Get-RpcClientAccess cmdlet to display the settings for the Exchange RPC Client Access service that's running on the Client Access server role on Microsoft Exchange Server 2010.

By default CAS role is enable an responsible for mailboxes services, and Mailbox server role is responsible for Public folders.



By default Outlook 2007/10 is enable for encrypted all communication between client / server but for outlook 2003 no, we must to disable the encryption from server side or just enable it on the clients:



http://technet.microsoft.com/en-us/library/dd335190.aspx