Announcement

Collapse
No announcement yet.

Is it really the Enterprise version?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Is it really the Enterprise version?

    I have five Storage Groups on an Exchange 2003 server, V6.5 Build 7638.2 SP2. I tried to create another Storage Group, but I get the error "The server already contains the maximum number of storage groups allowed. ID no: c1034a7b", but the Application Log shows:
    Event Type: Information
    Event Source: MSExchangeIS Mailbox Store
    Event Category: General
    Event ID: 1217
    Date: 18/07/2007
    Time: 1:13:33 PM
    User: N/A
    Computer: XMAIL
    Description:
    The Exchange store 'V Storage Group\V Mail Store' has unlimited storage capacity. The current physical size of this database (the .edb file and the .stm file) is 127 GB. The only size constraint for this database is the maximum size that is supported by the database storage engine (8000 GB).

    For more information, click http://www.microsoft.com/contentredirect.asp.
    Doesn't this mean the Enterprise version is installed and that we have unlimited capacity for Storage Groups?
    |
    +-- JDMils
    |
    +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
    |

  • #2
    Re: Is it really the Enterprise version?

    AFAK the limit is not on your DB but it is on the amount of the storage groups
    you can install another exchange server and then you will be able to create more storage groups.

    Eitan

    Comment


    • #3
      Re: Is it really the Enterprise version?

      http://support.microsoft.com/kb/822440 Oh gee, guess what I used to find this.
      1 1 was a racehorse.
      2 2 was 1 2.
      1 1 1 1 race 1 day,
      2 2 1 1 2

      Comment


      • #4
        Re: Is it really the Enterprise version?

        At the moment, our existing production Exchange server has the four Storage Groups, but using 7 Information Stores.

        What I'm worried about is that I need to move one Storage Group which contains 3 Information Stores but one shared Transaction Log folder, to another Exchange server but one IS at a time.

        To move the IS's one at a time, I'd have to backup the IS on its own and restore it onto the new Exchange server, then import it into a new SG. I can't see how I would do this simply by copying the IS across the network as I can't tell which TL files to also copy.

        Thanks guys (yeah, you too Chris )
        Last edited by JDMils; 19th July 2007, 05:50.
        |
        +-- JDMils
        |
        +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
        |

        Comment


        • #5
          Re: Is it really the Enterprise version?

          IIRC one of the recommended ways is to create a new (empty) store and them migrate mailboxes.

          Alternatively backup (commits TLogs) and restore on the new box -- obviously stop mail coming into the store while you are doing this
          Tom Jones
          MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
          PhD, MSc, FIAP, MIITT
          IT Trainer / Consultant
          Ossian Ltd
          Scotland

          ** Remember to give credit where credit is due and leave reputation points where appropriate **

          Comment


          • #6
            Re: Is it really the Enterprise version?

            Tom, will this work if the new server has a different name from the original?

            Is there a (working and tested) procedure for moving the IS physically across the network to the new server and importing the IS on the new server? How do I incorporate the TLog files with this method?

            Thanks.
            |
            +-- JDMils
            |
            +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
            |

            Comment


            • #7
              Re: Is it really the Enterprise version?

              You can't move databases between servers and expect them to mount.
              If you want to split the users or mailboxes up you will have to build the new server and then use move mailbox to move the data to the new server. That will update the domain with the new location nd Outlook will redirect automatically.

              Simon.
              --
              Simon Butler
              Exchange MVP

              Blog: http://blog.sembee.co.uk/
              More Exchange Content: http://exchange.sembee.info/
              Exchange Resources List: http://exbpa.com/
              In the UK? Hire me: http://www.sembee.co.uk/

              Sembee is a registered trademark, used here with permission.

              Comment


              • #8
                Re: Is it really the Enterprise version?

                Thanks Sembee,

                I was looking at Faster Exchange Server recovery with the Dial Tone Method but it doesn't mention if you can migrate the IS to a server with a different name.
                |
                +-- JDMils
                |
                +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
                |

                Comment


                • #9
                  Re: Is it really the Enterprise version?

                  That is a disaster recovery technique, not a migration technique.
                  Is there any reason you don't want to use the move mailbox method?

                  Simon.
                  --
                  Simon Butler
                  Exchange MVP

                  Blog: http://blog.sembee.co.uk/
                  More Exchange Content: http://exchange.sembee.info/
                  Exchange Resources List: http://exbpa.com/
                  In the UK? Hire me: http://www.sembee.co.uk/

                  Sembee is a registered trademark, used here with permission.

                  Comment


                  • #10
                    Re: Is it really the Enterprise version?

                    Yeah, cos I have to move around 60 or more mailboxes which range from 1 to 5 GB in size and that's going to take a LONG time.

                    Also, this IS a disaster in the making for me.....the original server keeps rebooting and management now knows where I sit- they have left tracks in the carpet to my office!
                    Last edited by JDMils; 24th July 2007, 16:04.
                    |
                    +-- JDMils
                    |
                    +-- Regional Systems Engineer, DotNet programmer & Jack of all trades
                    |

                    Comment


                    • #11
                      Re: Is it really the Enterprise version?

                      This question is now almost a week old.
                      If you had built the new server with a new name last week, you could have moved the mailboxes using move mailbox, with zero downtime in that time quite easily.

                      What is worse? Taking a few days to move the mailboxes across during the night, decreasing the number of mailboxes at risk as you do so, or attempting to move the entire lot, going through all the hassle of trying to get the databases to mount, only for something to go wrong and no one has access to email?

                      Build the server, start moving the mailboxes. The quicker you get started the quicker it is done.
                      Move mailbox is zero risk, zero downtime.

                      Simon.
                      --
                      Simon Butler
                      Exchange MVP

                      Blog: http://blog.sembee.co.uk/
                      More Exchange Content: http://exchange.sembee.info/
                      Exchange Resources List: http://exbpa.com/
                      In the UK? Hire me: http://www.sembee.co.uk/

                      Sembee is a registered trademark, used here with permission.

                      Comment

                      Working...
                      X