Results 1 to 6 of 6

Thread: Alternate Index, Store and DB Location?

  1. #1
    marrotte is offline Trained Alumni
    Join Date
    Aug 2008
    Location
    Orlando, FL
    Posts
    9
    Rep Power
    6

    Default Alternate Index, Store and DB Location?

    Can the store, index and db location be easily changed?

    For example, is there a config file that specifies:

    /opt/zimbra/index
    /opt/zimbra/db
    /opt/zimbra/store

    I'm working from the command line and doing a backup for a new client. This is the first time I have looked at their system and there's some artifacts (index and store folders in other locations with recent dates) that lead me to believe the index, store and db have been re-located outside of /opt/zimbra... Any help help is greatly appreciated.

  2. #2
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    20

    Default

    Welcome to the forums,

    Are you trying to change or just figure out what external locations you might need to backup?

    su - zimbra
    zmvolume --list (or zmvolume --displayCurrent)

    CLI zmvolume - Zimbra :: Wiki

    Or visit the Admin Console GUI > server > volumes tab.

    To view it in the DB:
    su - zimbra
    mysql
    select * from zimbra.volume;

    http://www.zimbra.com/forums/announc...html#post62754 so we know what version you're using.

  3. #3
    marrotte is offline Trained Alumni
    Join Date
    Aug 2008
    Location
    Orlando, FL
    Posts
    9
    Rep Power
    6

    Default good stuff

    Mike:

    Thanks for the quick reply -- good stuff.

    With zmvolume -dc, I get the locations I was curious about:

    Volume id: 4
    name: messageRAID1
    type: primaryMessage
    path: /raid/zimbra/store
    compressed: true threshold: 4096 bytes

    Volume id: 3
    name: indexRAID1
    type: index
    path: /raid/zimbra/index
    compressed: true threshold: 4096 bytes

    And with zmvolume -l, I get the defaults + the one's I was curios about:

    Volume id: 2
    name: index1
    type: index
    path: /opt/zimbra/index
    compressed: false

    Volume id: 4
    name: messageRAID1
    type: primaryMessage
    path: /raid/zimbra/store
    compressed: true threshold: 4096 bytes

    Volume id: 1
    name: message1
    type: primaryMessage
    path: /opt/zimbra/store
    compressed: false

    Volume id: 3
    name: indexRAID1
    type: index
    path: /raid/zimbra/index
    compressed: true threshold: 4096 bytes

    I suppose, the previous Admin created new volumes on the raid drive at some point and -dc is the stuff that needs backing up, right?

    Also, I updated my profile with my version...

    Thanks,

    ~Mike

  4. #4
    marrotte is offline Trained Alumni
    Join Date
    Aug 2008
    Location
    Orlando, FL
    Posts
    9
    Rep Power
    6

    Default

    Mike:

    Forgot to answer your question:

    Yeah, I am just trying to figure out what to back up and at the moment I do not have access to the Web UI. I read up on Volumes and figure I'll need to back up everything that comes back with zmvolume -l , and not just zmvolume -dc... Form what I understand, mailboxes could have been created, before the "current" volumes were created...

  5. #5
    mmorse's Avatar
    mmorse is offline Moderator
    Join Date
    May 2006
    Location
    USA
    Posts
    6,242
    Rep Power
    20

    Default

    Correct - all of it.

    Essentially, with Zimbra stopped (zmcontrol stop) you need to backup /opt/zimbra & any linked directories; so that means everything in --list output (not just -displayCurrent)
    Backup and Restore Articles - Zimbra :: Wiki

    Because you're coming from 4.5.3 I would backup > and to go 4.5.11 first > backup> 5.0.8 (/.9 if it's out when your ready.)

    Explanation:

    Each Zimbra mailbox server is configured with one current index & message (NE can add secondary HSM volumes).

    Each mailbox is assigned to a permanent index directory on the current index volume. When an account is created, the current index volume is automatically defined for the account. You cannot change which index volume the account is assigned. As volumes become full, you can create a new current index volume for new accounts. When a new index volume is added as current, the older index volume is no longer assigned new accounts. Index volumes not marked current are still actively in use as the index volumes for accounts assigned to them. Any index volume that is referenced by a mailbox as it's index volume cannot be deleted.

    When a new message is delivered or created, the message is saved in the current message volume. Additional message volumes can be created, but only one is configured as the current volume where new messages are stored. When the volume is full, you can configure a new current message volume. The current message volume receives all new messages. New messages are never stored in the previous volume. A current volume cannot be deleted. If there are accounts with messages referencing a volume it should not be deleted until you point the volume path to wherever you've now moved the items.

  6. #6
    marrotte is offline Trained Alumni
    Join Date
    Aug 2008
    Location
    Orlando, FL
    Posts
    9
    Rep Power
    6

    Default

    Yeah. Upgrading has been requested by the client and next on the todo list. I'm havng some trouble finding an "official" upgrade doc.

    I get your suggestion about doing intermediate upgrades, i.e. 4.5.3->4.5.11->5.0.8. But, is backing/upgrading/restoring the way to go?

    The closest doc I could find on backing/upgrading/restoring is: http://wiki.zimbra.com/index.php?tit...dure#Restoring ... And that doc doesn't really cover upgrading. Is there a better source?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •