MSTR Metabase Backup problem __ Database

MSTR Metabase Backup problemCan build multiple metabase on the same database, because I want to back up the project on the same metabase.
When I set up a metabase on the database, once again using Configration Wizard to create the metabase, it always pops up: the location has a metadata repository, only to move the original database repository to continue. But I want to copy the project should use a different metabase to do.
When I create a new project source, as long as I use ODBC to connect to my database, it will automatically connect to the database on the existing metabase, the previous project also automatically. How do I build two different project sources to replicate the project to make a backup of the project.
Would you please give me some advice? Alas, the concept is not clear.
A project source can contain multiple projects, and no common report objects and common objects (entities, facts) between projects and projects

Only one project source can be published on a server, but you can connect to a project source created by multiple individual servers by creating a 3-tier project source. (This is why you can see multiple 3-tier project source icons in desktop).

A project source corresponds to a metabase (whether it is a project source on your own server, a project source for someone else, or a 2-tier project source).

Generally do metadata backup, directly on the database to do a library backup on it. Upstairs, the backup library is for the entire user to back up, and it is useless to back up only the metabase table at the beginning of the DSS.

You can also make backups using the way that you copy items.
To create an access metabase that copies items that need to be backed up into the access metabase, access has the advantage of being able to migrate easily. ACCESSThe downside of ACCESS is that you need a Windows environment. My understanding the metabase is as good as it needs to be on the same database as the DW database, and it's easy to back up. about metabase IssuesDesktop is just a client that can be configured with two and three layers of project sources.
The two-tier project source is to connect to your metadata database directly with desktop (you need to configure the database connection on the desktop machine),
The three-tier project source is connected to the I-server and then i-server to the metabase (just configure the database connection on the I-server machine).
So the three floor is more convenient.

Creating a metabase through Configuration Wizard is a script execution process that you can open to read carefully,
Not only do you create tables, but there are other database objects, which is why only the 10 DSS tables cannot be backed up successfully.

You can have multiple items with different names in a single metabase.
So if you want to make a version backup of your project, copy the project directly from the metabase.

But if you want to prevent the metabase from breaking down and do a secure backup,
You will need to copy the items from the metabase to another metabase (which can be access).
and replication projects are best done in two-tier mode, faster and more stable. The backups made on this project are now backed up to local access.   Very easy to use. Backing up the backup library for the entire user, it is useless to back up only the metabase tables at the beginning of the DSS.
--Consult, how can the entire user backup. In fact, is to do ordinary database backup can be. It is useless to say "back up only the metabase table at the beginning of the DSS" because the backup database has not only "tables" but also other database objects such as indexes, triggers, and so on.

Access is doing file backup;
SQL Server is to do a database backup;
Oracle is doing a user backup.

In short, it is to do a normal database backup. If you do not have access to database backup and recovery, you should first find and learn relevant information. This has nothing to do with MSTR.