NetApp:SNAPDrive and SNAPManager for Exchange on an RDM

Similar Questions

• Unity 4.0 (2) and /ForestPrep for Exchange 2003

  We plan to upgrade our Active Directory in Windows Server 2000 and Exchange 2000 to Exchange 2003 and Windows Server 2003 AD network. We currently have two unit 4.0 (2) servers (Unified Messaging) in two separate locations, each serving a different group of offices. All in all, we have more than 1,000 users in 5 different locations. All these users and locations upgrade to Windows 2003, Exchange 2003 and unity 4.0 (4) at the same time is not an option. Therefore, we would gradually migrate each location to Exchange 2003, Windows 2003 and unity 4.0 (4).

  I understand that unity 4.0 (4) is the recommended version to use with Windows 2003 and Exchange 2003, but I've also read in Cisco documentation as 4.0 (4) unit when running on Windows 2003 requires that you are already running Exchange 2003. What confronts a dilemma in that we have separate locations of mutiple supported by one server shared unity and we simply cannot risk all these sites simultaneously to unity 4.0 upgrade (4), Server 2003, and Exchange 2003. So, what would be the best strategy to go where we want to be? This brings me to the following questions:

  a. If we run / Exchange 2003 ForestPrep against our field now even if we are always unity 4.0 (2)?

  b. can we begin to introduce Exchange 2003 servers in each of our branches (administrative groups & routing Exchange) while staying at unity 4.0 (2) provided that these servers are not designated as a partner of unity and without voice mail server or connectors of the unit (for example, unity voice bridge connector) are on these servers?

  c. would make sense to upgrade the servers of the 4.0 unit (3) first and then move to unity 4.0 (4) once all the Exchange servers in all our branches have been improved in Server 2003 and Exchange 2003? This interim update seems to give us more flexibility in our path to upgrade its operating system to Microsoft Exchange server version requirements are less onerous

  Windows 2003 is not necessary for the 4.0 unit (4). Likewise, it is not recommended because there is evidence of the way in which Windows 2000 with the unit, but we do support Windows 2003 if the client really wants to use it. We ship the unit on Windows 2000 and that's what we recommend at this time. No functionality is lost under Windows 2000.

  Officially we do not support have all Exchange 2003 servers or even execution of ForestPrep if you have lower than 4.0 (3). That said, the only flaw we've never seen this is when the unit is connected under the local system or when the subscriber accounts are on Exchange 2003 servers. You wouldn't be the first customer to do so and it should be fine but really understand that it is not technically a Cisco tested and taken in charge of the configuration.

  Thank you

  Keith

• Storage NFS for Exchange Server OS

  While I believe that Microsoft Support policy and recommendations for Exchange servers in hardware virtualization environments, document is very clear, I was faced with the following question:

  Microsoft does support the operating system Exchange server running on a NFS datastore?

  I believe that this issue is the result of the lack of understanding of the support strategy.  Here is the statement in question ("BOLD" emphasis is mine):

  The storage used by the Exchange Server guest machine for storage of data Exchange (for example, the basics of data from the mailbox or hub transport queues) can be virtual storage of a fixed size (for example, fixed virtual hard drives [VHD] in a Hyper-V environment), SCSI direct storage, or Internet SCSI (iSCSI) storage. Pass through storage is storage that is configured at the host level and dedicated to one guest machine. All storage used by a computer invited exchange for the storage of Exchange data must be block-level storage. Exchange 2010 is not compatible with network attached storage (NAS) volumes. NAS storage presented to the guest as block-level storage using the hypervisor is not supported. Transmission volumes must be presented as storage of block level for hardware virtualization software. This is because Exchange 2010 does not support the use of storage (NAS) devices connected to the network. The following virtual disk requirements apply to volumes that are used to store Exchange data.

  While I thought that the statement applied specifically to Exchange data, you can read this includes the OS data server as well (based on the second sentence in bold).  A customer was told by an engineer from MS that NAS storage was not at all based.  I disagree, because the recommended storage configuration is to separate the BONES of exchanging data anyway.

  Reference http://TechNet.Microsoft.com/en-us/library/cc794548%28EXCHG.80%29.aspx

  I'm all for pick up statements of support from MS and calling him on it, when the issue is raised in question and this one is no different.  I read the Data Exchange simply means that databases, newspapers, etc.  In fact they make it that some clearly in this statement:

  "The storage used by the Exchange guest machine for storage of data Exchange (for example, the basics of data from the mailbox or Hub transport queues)...". »

  There is no mention of the operating system being considered as Exchange data... which is not.  As for this one:

  "All storage used by a guest computer in Exchange for the storage of Exchange data must be block-level storage because Exchange 2010 does not support the use of storage (NAS) devices connected to the network."

  OK, this has been an attitude of long-standing support for MS, no biggie there since we have some that only qualified Data Exchange.  To the following:

  "In addition, NAS storage presented to the guest as block via the hypervisor level storage no is not supported."

  The key point here is that the NAS storage can be presented to a guest in two ways, one through the prompt (mounting storage NAS for Windows, that is, \\server\share) and another through the hypervisor (supported NFS VMDK).  In this statement, they are referring to the latter.  So, after all, this hike that my point is that it seems to me that the drive for your Exchange virtual computer operating system can absolutely be hosted on NAS-based storage and be supported.

  .. .then it's VMware spin on it, a little.  For Hub Transport, client access and stand-alone Mailbox servers, we have no problem with that.  We recommend, however, that if a clustering solution is deployed within the guest, i.e. DAG, you create the VMDK as eagerzeroedthick.  VMDK supported by NFS cannot be eagerzeroedthick, by our advice should not be hosted on NFS.  This little nugget of information is available here: http://kb.vmware.com/kb/1037959.  The reason behind this is when you use a disk virtual standard thickness blocks must be cancelled before the data is written, this (albeit low) latency is avoided by using the eagerzeroedthick option.  What we are proposing is avoid any additional latency that clusters tend to not like and zero all on.  BTW, we suggest this to any level of clustering, not just Exchange or MSCS comments.

  -alex

• behavior of application with BES flavours IE for Exchange, Domino and GroupWise.

  Hello

  I have a java application to networking than woks with BES for Exchange. Can I assume that the same application works also with other i.e two flavors Domino and GroupWise.

  my application uses MDS and makes use of the BES network.

  Please clarify for me.

  Thank you

  Sri.

  The Mobile Data System (MDS) component of BlackBerry Enterprise Server offers the same features for Exchange, Domino and GroupWise flavors.  An application using the SDM as transport should work the same, regardless of the messaging platform.

• How to list the security settings for distributed virtual switches and distributed virtual exchanges

  Is there a .pl can I use to list the security settings for distributed virtual switches and distributed virtual exchanges?

  parameters such as

  Mode promiscuity (license /reject)

  Mac address changes (license /reject)

  Allows the transmission of forged (permitted /reject)

  Thank you

  Fred

  Take a look at this article from blog for the script and details - http://www.virtuallyghetto.com/2011/12/retrieving-information-from-distributed.html

• Best practices for Exchange 2003 with VMWare ESXi 3.5 and iSCSI SAN

  Hello guys,.

  Here's the Q? We have 1 physical Exchange 2003, the HOST of 4 and 1 iSCSI SAN with LUN 3, 1 for data, 1 for VMWare and 1 for SQL, if we're going to virtualize it, I don't know where to put data Exchage and newspapers. I do not think that that is a good practice to put together the data but I do not have another SAN. So, what can I do?

  Thank you.

  We have 813 mailbox.

  I agree with cainics, start an average size and go from there.  I know it's a production mail server and you can not exactly 'play' with the settings because this requires time, but if you do the VM too big, you would have nothing left for other virtual machines.

  I would go 2 vCPU and at least 4 GB of RAM, maybe 8GB.  There must be parameters for the Exchange mailbox 813 and X users # to implement your environments in order to get an idea of the amount of RAM that will be... 4GB seems minimal to me, but 8 GB would probably be better like that.

• Anyone know how to get a license for Exchange Server 2007?

  Exchange Server on Windows Server 2008

  Hello

  Does anyone know how to get a license for Exchange Server 2007. I've been on the Microsoft Web site, and it is only showing Exchange 2010.

  Thank you

  Hello R McMullen,

  The Microsoft Answers community focuses on issues and problems related to the consumer environment. Please join the public IT pro TechNet forums below:
  TechNet - Windows Server
   
  Thank you

• Installation of Foglight for Exchange 2010

  Dear all,

  I downloaded Foglight for Exchange on DELL site, but I found that files html, zip, and car and could not find any file (exe/msi etc.) so guide which miss me to deploy foglight for Exchange.

  Thanks in advance

  Kind regards

  Hussain

  You will need to install the cartridge change and then configure agent/s to monitor your environment.

  Given the fact that you are not familiar with Foglight, you will need to get technical assistance d safe g involved working with you at this stage. Continuing this thread of discussion won't be effective.

  There is also a list of pre-requsites that need to be configured on the target Exchange server/s for our agent to be able to successfully complete:

  http://eDOCS.quest.com/vFoglight/800/files/FoglightForExchange_5.6.9_ReleaseNotes.html

• I need to contact ADOBE customer service, I just bought adobe photoshop and elements for windows first, but I have a Mac. Can I change the purchase? Thank you. Mauro

  I need to contact ADOBE customer service, I just bought adobe photoshop and elements for windows first, but I have a Mac. Can I change the purchase? Thank you. Mauro

  To the link below, click on the still need help? option in the blue box below and choose the option to chat or by phone...

  Make sure that you are logged on the Adobe site, having cookies enabled, clearing your cookie cache.  If it fails to connect, try to use another browser.

  Get help from cat with orders, refunds and exchanges (non - CC)

  http://helpx.Adobe.com/x-productkb/global/service-b.html ( http://adobe.ly/1d3k3a5 )

• SnapManager for Oracle error when creating profile

  Hi all

  I am deploying Snapmanager for Oracle on Windows and I get the error below, while I am trying to create a profile for a DB. Can help me solve this problem.

  -[WARN] SMO-12104: unable to connect to the database to perform the check. Database may not exist, may not be running, or the listener cannot be executed. Error's Oracle: ORACLE-10005: unable to connect to the instance of database ST88 using JDBC connection string JDBC: thin: snapmanager_ora/XXXXXXXX @(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = HostDB1)(PORT = 1521))) (CONNECT_DATA = (SID = ST88))).  Error: Listener refused the connection with the following error:

  ORA-12505, TNS:listener is not currently of SID given in connect descriptor

  Used by the client connect descriptor was:

  (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = HostDB1)(PORT = 1521))) (CONNECT_DATA = (SID = ST88)))

  .

  -[ERROR] SMO-05075: profile create failed: ORACLE-10005: unable to connect to the instance of database ST88 using JDBC connection string JDBC: thin: snapmanager_ora/XXXXXXXX @(DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = HostDB1)(PORT = 1521))) (CONNECT_DATA = (SID = ST88))).  Error: Listener refused the connection with the following error:

  ORA-12505, TNS:listener is not currently of SID given in connect descriptor

  Used by the client connect descriptor was:

  (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST = HostDB1)(PORT = 1521))) (CONNECT_DATA = (SID = ST88)))

  Thank you

  Noelie

  > ORA-12505, TNS:listener is not currently of SID given in connect descriptor

  How is the * auditor * configured?

  You try to use a SID in the connection descriptor.  The listener listen to this SID?  Check the STATUS of the listener.

  Hemant K Collette

• Purple screen on ESXi 5.5 for HP in preparing the AD for Exchange

  Hi,.
  
  we have a installed ESXi () ESXi 5.5 for HP - Image profile: HP-ESXi - 5.5.0 - iso - 5.72. 3) for both servers (DC and Exchange).

  
  

  Preparation of Active Directory for Exchange (). \setup/PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizationName.: "Enter the name of Org Exchange"), we get a
  

  Purple screen (photo attached). And that already for the second time !
  

  No matter which solve this problem or knows how to solve this problem.

  Thanks in advance.

  Alexander

  

  Looks like some sort network problems concerning virtual vnic in the prompt that is the cause.  See the Article KB KB VMware: VMware ESXi host 5.x undergoes a screen to diagnosis purple mentioning E1000PollRxRing and E1000DevRx

  VFK

• Migrate the virtual machine for Exchange 2010 from one host to another

  Dear members,

  Please let know us if the migration of a virtual machine for Exchange 2010 is supported to an Esxi host to another, the Esxi version is 5.0.

  There are unique Exchange environment with the role of hub, CAS and mailbox on the same virtual server. We have a maintenance window and we think moving exchange virtual machine from one host to another, but before that I need to be sure if it's supported my MS and do not want to have problems after, because I have also gotten to know here in the forums this snapshot for Exchange 2010 is not supported by Ms.

  Please notify.

  Kind regards

  I'm not aware of any limitations with VMS Exchange migration. Anyway, you can consider running the migration during the low workload.

  André

• In-Guest iSCSI for Exchange 2010

  Hi, we just built and are ready to go into production with Exchange 2010 using LUNS in guest through the card Microsoft iSCSI initiator iSCSI separate network for iSCSI etc. Load tested with JetStress and everything seems fine. We just found out as snapshots are not supported with iSCSI in guest so we are concerned that the other things work or be taken in charge or another, i.e. of vmotion. So, does anyone know if we lose any other characteristic, and we need to change our minds and using ESX iSCSI? I read pieces on being comparable, that we stuck with a guest performance because that's what we know with our existing Exchange 2007 environment (physical). If we must change, is it simple?

  Hey everyone who is following this thread or found via Google.  It is important to understand what is and is not supported when you are running Exchange on a virtual machine.

  To be absolutely clear, combining Exchange 2010 DAG and migration technologies such as vMotion technology is supported.  You must ensure that you are running at least Exchange 2010 SP1 as well as a version of vSphere that sits on the server virtualization Validation program.

  I think that the link was already posted, but here is the final link:

  http://blogs.technet.com/b/Exchange/archive/2011/05/16/announcing-enhanced-hardware-virtualization-support-for-Exchange-2010.aspx

  More specifically, since the post above (in bold italics):

  Combining Exchange 2010 high availability solutions (database availability groups (DAG)) with hypervisor clustering high availability and migration solutions that will be moving or automatically failover servers for mailboxes that are members of a DAG between clustered root servers, is now supported.

  Improved, that we did in Exchange Server 2010 SP1, with more comprehensive tests of Exchange 2010 in an environment that is virtualized, we are pleased to offer this additional deployment flexibility to our customers. Management of updated support applies to any provider of hardware virtualization that participate in the Windows Server Virtualization Validation Program (SVVP).

  Logiboy123, can you provide any documents to support the statement that Microsoft does not support this configuration?  The above quotes are directly from Microsoft and are very clear that they support not only the migration of Microsoft technology, but also similar to any other provider of the hypervisor technology, provided that they are in the SVVP program.

  Since vSphere is part of the SVVP, Microsoft has extended support for the technologies of migration such as vMotion, in addition to their own Live Migration.  Of course, simply support something does not automatically make it works.  If you want knots vMotion DAG works correctly, you might have settings described in this blog post extended the cluster heartbeat timeout (also a fully supported configuration change):

  http://www.thelowercasew.com/vSphere-and-Exchange-Admins-can-live-in-harmony-Microsoft-finally-supports-HA-and-VMotion

  To answer the original question in this post, using the Protocol in-guest iSCSI is supported and with vMotion in this configuration is supported as well.  You're not really 'give up whatever it is' using this configuration well so if it meets your needs, I would stick with it.  I prefer generally VMFS just because of the flexibility it offers, but all the world has different requirements and I have absolutely no problem with guest iSCSI if your organization requires it.

  Do not forget that whatever configuration, snapshots of virtual machine are not supported for Exchange. Here is another post which goes into detail on it and cover the declaration of support for Microsoft Exchange 2010 snapshots and machine virtual: http://www.thelowercasew.com/virtual-machine-snapshots-and-tier-1-apps-not-always-supported

  So in general, I would say that provided you are running the correct versions of Exchange and vSphere must then take full advantage of your configuration to use features like vMotion and HA without problem.  If you adjust your settings accordingly cluster heartbeat timeout, you should have no problem using vMotion with your knots of DAG.

  Matt

  http://www.thelowercasew.com

• ESX 3i for Exchange 2003

  Hello people,

  Can I use ESX 3i to consolidate the two Exchange server 2003 for redundancy? 1 box of 2 virtual Exchange. We have about 500 users.

  Thank you.

  Before you Virtualize your Exchange boxes, I would consider using Exchange 2007 because that provides more users and performance through larger cache sizes.  There is a best practice to do this, use vmware for exchange 2007 pleas google online that he will quickly reveal.

  If you found this information useful, please consider awarding points to 'Correct' or 'useful '. Thank you!!!

  Kind regards

  Stefan Nguyen

  VMware vExpert 2009

  iGeek Systems Inc.

  VMware, Citrix, Microsoft Consultant

• I opened my phone i plwss send me password and id for Flavia

  I opened my phone i plwss send me password and id for Flavia

  open id is my