Zimbra Next Generation Modules/Zimbra NG Backup/Store: Difference between revisions

m (1 revision imported: Zimbra NG)
 
Line 1: Line 1:
<div class="col-md-12"><br></div>
#REDIRECT [[Zimbra_NG_Modules/Zimbra_NG_Backup/Store]]
<div class="col-md-12"><br></div>
<ol class="breadcrumb">
  <li>[[Main Page|Zimbra Wiki]]</li>
  <li>[[Zimbra_Next_Generation_Modules]]</li>
  <li>[[Zimbra_NG_Backup]]</li>
  <li class="active"> Store</li>
</ol>
__NOTOC__
<div class="col-md-12"><br /></div>
<div class="col-md-9">
    <h2 class="title-header" style="padding-bottom: 9px; border-bottom: 4px solid #0087c3;">Zimbra NG Backup - Store</h2>
    <div class="col-md-12">
        <div class="ibox-content">
            <div class="post animated fadeInLeft animation-delay-8" style="padding-top:5px">
                <div class="panel panel-default">
                    <div class="panel-body">
                        <h5 class="post-title">Zimbra NG Backup - Store</h5>
                        <div class="row">
==The Zimbra NG Backup Store==
=== Specs ===
The Zimbra NG Backup Store is the place where [[Zimbra_Next_Generation_Modules/Zimbra_NG_Backup]] saves all its data.
 
The default folder is /opt/zimbra/backup/zextras/, but the Backup Path can be changed in the Zimbra NG Backup section of the Zimbra Next Generation Modules Administration Zimlet. Similarly, an External Backup can be saved in any directory.
 
No Hardlinks are used, so the store can be on any filesystem as long as it is Case Sensitive.
 
Items in the Backup Path are compressed with the gzip algorithm and deduplicated, so a Backup Path will usually take between 50% and 75% of the total size of all Zimbra volumes.
 
=== Map Files ===
The External Import procedures creates 2 kinds of Mapfiles:
 
* the map_[server_id] file, inside the Zimbra NG Backup Store's root, contains the mapping between the account IDs in the Old and Current server.
* the id_mapper file, contained inside each imported account ''accounts'' subfolder, contains a list of mailitem mappings created during the Import procedure to keep tracks of the items imported into the account along with their id on the old server.
 
If you want to restart from scratch an already begun External Import operation, be sure to delete all the mapping files.
 
== Folder Tree ==
The structure of the Zimbra Next Generation Modules store is the following:
 
=== Depth 1 ===
'''tree /opt/zimbra/backup/zextras/ -L 1'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0">
/opt/zimbra/backup/zextras/
 
├── accounts
 
├── items
 
├── map_[server_id]
 
└── [server]
</div>
As you can see, the first level of the folder tree contains 3 main directories:
 
'''accounts''' - contains all the accounts' data and informations
 
'''items''' - contains all kind of items (deduplicated)
 
'''server''' - contains server configurations
 
The '''map_[server_id]''' is created when importing accounts with the External Import feature, and contains the mapping between the account IDs in the Old and Current server. Using this file's name as an argument for the ''zxsuite backup doFixShares'' will fix the consistency of any share broken during the import procedure.
 
 
==== Depth 2 ====
'''tree /opt/zimbra/backup/zextras/accounts -L 1'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0">
/opt/zimbra/backup/zextras/accounts/
 
├── 0051f1d5-82cc-40ee-8f29-dfa692a92ad8
 
├── 00f58d1f-1eb1-48c7-961e-8c474f98b314
 
├── 0157830e-00fa-4bcd-a723-390c9efbaa7c
 
[...]
 
[...]
 
[...]
 
├── ff005361-94e1-4a66-aa4f-1644484e16c5
 
├── ffabddbe-aca0-4378-a680-41add051d315
 
└── ffb87c28-d02b-452c-b225-fdd1a13476d0
</div>
The ''accounts'' folder is a container for account informations and data. Each subfolder is named after the zimbraId of the respective account.
 
 
'''tree /opt/zimbra/backup/zextras/items -L 1'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0">
/opt/zimbra/backup/zextras/items
 
├── ,,
 
├── ,+
 
├── +,
 
[...]
 
[...]
 
[...]
 
├── zZ
 
├── Zz
 
└── ZZ
</div>
The ''items'' folder is a container for backupped items. It contains a set of directories named after the first TWO character of the respective item's hash.
 
 
'''tree /opt/zimbra/backup/zextras/server -L 1'''
<div style="background:#D0D0D0;border:1px solid #FD0D0D0">
/opt/zimbra/backup/zextras/server/
 
├── backup_12_5_11#20_7_19
 
├── backup_13_5_11#11_42_36
 
├── backup_13_5_11#11_58_59
 
[...]
 
[...]
 
[...]
 
├── backup_29_4_11#18_41_5
 
└── backup_3_5_11#1_22_36
</div>
The ''server'' folder is a container for server configurations backupped by the Live Full Scan. It contains a set of files named after the timestamp of the corrisponding Live Full Scan.
 
===== Depth 3 =====
'''tree /opt/zimbra/backup/zextras/accounts/0051f1d5-82cc-40ee-8f29-dfa692a92ad8 -L 1'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0">
/opt/zimbra/backup/zextras/accounts/0051f1d5-82cc-40ee-8f29-dfa692a92ad8
 
├── account_info
 
├── id_mapper
 
└── items
</div>
 
 
'''tree /opt/zimbra/backup/zextras/accounts/0051f1d5-82cc-40ee-8f29-dfa692a92ad8/items -L 2'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0">
/opt/zimbra/backup/zextras/accounts/0051f1d5-82cc-40ee-8f29-dfa692a92ad8
 
├── 01
 
│  └── 1
 
├── 02
 
│  └── 2
 
├── 03
 
│  └── 3
 
├── 04
 
│  └── 4
 
├── 05
 
│  └── 5
 
├── 06
 
│  └── 6
 
├── 07
 
│  └── 7
 
├── 08
 
│  └── 8
 
├── 09
 
│  └── 9
 
├── 10
 
│  └── 10
 
├── 11
 
│  └── 11
 
├── 12
 
│  └── 12
 
├── 13
 
│  └── 13
 
├── 14
 
│  └── 14
 
├── 15
 
│  └── 15
 
└── 16
 
│  └── 16
 
</div>
Inside each "mailbox" folder there is the "account_info" file which contains all the LDAP data of the account and a group of folder/file couples inside the "items" folder containing all the metadata belonging to the items in the mailbox. An additional file named '''id_mapper''', which contains a list of mailitem mappings, is created during the import procedure to keep tracks of the items imported to the account and their id on the Old and Current server.
 
 
'''tree /opt/zimbra/backup/zextras/items/00 -L 3'''
<div style="background:#D0D0D0;border:1px solid #D0D0D0%">
 
/opt/zimbra/backup/zextras/items/00
 
├── 000S8xLSP4pckj97BqMaGuShm7s=
 
├── 0041ySPpK3moeXwBfDf5tl9LQnI=
 
├── 0047ooqYw8p5ToNPnqxEymRSovg=
 
├── 007SpLqlcsoL,XWIr5M,mVZNYBs=
 
[...]
 
[...]
 
[...]
 
├── 00Y4r9456KbnfuaUzvm3aXt5NdI=
 
├── 00YDxLMrZsHVja9Lid2T7O+kiSg=
 
├── 00YrLnM4bo8Vq1Aiz8AypX9Hgwc=
 
└── 00Z+mkHUNJ7Sl43V7sybTR,N7OI=
</div>
This is a view of one of the 4096 containers inside the '''items''' folder. Pretty straightforward, inside the "00" folder are contained all the items whose hash begins with "00". Please note that the ACTUAL DATA is contained here, as the "items" subfolder of a "mailbox hash" folder contains only the metadata.
 
                        </div>
                    </div>
                    <div class="col-md-9">
                        <div class="panel-footer">
                            <p><i class="fa fa-clock-o"></i> Aug 25, 2016 - [https://www.zimbra.com/email-server-software/ Know more »]</p>
                        </div>
                    </div>
                </div>
            </div>
        </div>
    </div>
</div>
<div class="col-md-3"><br /></div>
<div class="col-md-3">
    <div class="panel panel-zimbrared-light-border">
        <div class="panel-heading">
            <h3 class="panel-title"><i class="fa fa-gear pull-left"></i> Zimbra Next Generation Modules</h3>
        </div>
        <div class="panel-body">
            {{ZNG}}
        </div>
    </div>
</div>
<div class="col-md-3">
    <div class="panel panel-primary-light-border">
        <div class="panel-heading">
            <h3 class="panel-title"><i class="fa fa-info-circle pull-left"></i> Zimbra Next Generation Modules Resources</h3>
        </div>
        <div class="panel-body">
            {{ZNGL}}
        </div>
    </div>
</div>
<div class="clearfix"></div>
<div class="col-md-12"><br></div>
{{FH}}

Latest revision as of 13:12, 29 November 2017

Jump to: navigation, search