This post is more than 5 years old
17 Posts
0
9375
Protecting Avamar PostgreSQL database
Hi All,
How do we protect the configuration and other information (PostgreSQL DB) of the Avamar Utility node?
Regards, Binod
This post is more than 5 years old
17 Posts
0
9375
Hi All,
How do we protect the configuration and other information (PostgreSQL DB) of the Avamar Utility node?
Regards, Binod
Top
ionthegeek
2K Posts
1
July 22nd, 2013 04:00
The Avamar software has built-in mechanisms to protect the databases on the utility node. There is no need to configure manual protection for the utility node.
As Amol stated above, the MCS database and configuration are backed up to the MC_BACKUPS account on the Avamar storage nodes. If the system is configured for replication, these backups will be replicated to the replication partner so the configuration is still protected in case of a disaster.
christopher_ime
2K Posts
0
July 13th, 2013 23:00
Binod,
Please consider moving this question as-is (no need to recreate) to the proper forum for maximum visibility. Questions written to the users' own "Discussions" space don't get the same amount of attention and questions can go unanswered for a long time.
You can do so by selecting "Move" under ACTIONS along the upper-right. Then search for and select: "Avamar Support Forum" which would be the most relevant for this question.
Seeing though that over a month has elapsed since you posted, maybe you have already found the answer (possibly opened up a ticket with support)? If so, once relocated, consider sharing the resolution and also marking the question as "Answered" so that it can help others that have the same question. If not, once relocated, it will then have more visibility by the community of dedicated customers, partners, and EMC employees that are eager to assist.
DELL-Leo
Community Manager
Community Manager
•
7.1K Posts
1
July 18th, 2013 02:00
Hi bpras,
Avamar uses a PostgreSQL database to store various kinds of data, such as backup and restore activities, events, defined groups and clients. This information is available for reporting using third-party reporting tools such as Crystal Reports, MS Query, and Microsoft Excel. PostgreSQL is a highly regarded open-source Relational Database Management System (RDMS). Information in the Avamar database is accessible through any PostgreSQL-compliant Open DataBase Connectivity (ODBC) interface.
Actually, Avamar Server will maintenance PostgreSQL DB. So, I think the you do not need to worry about it. If you still need to protect it, maybe you can backup the PostgreSQL DB. But, I'm not sure how to backup PostgreSQL DB.
binodprasai
17 Posts
0
July 18th, 2013 16:00
Thanks Leo,
I am actually looking for the procedure to backup the PostgreSQL DB.
DELL-Leo
Community Manager
Community Manager
•
7.1K Posts
0
July 19th, 2013 00:00
OK. Hope other peers can help you for PostgreSQL DB backup.
Amol
207 Posts
0
July 19th, 2013 10:00
You don't need to backup the database manually, Avamar backups up MCS database and configuration every 1 hour and stores on the GSAN, you can list the content of last MC_BACKUPS using following command on utility node
avtar --list --path=/MC_BACKUPS
Default database dump is stored on following location which is update every hour
/usr/local/avamar/var/mc/server_data/mcs_data_dump.sql
If you still want to backup database manually, run the following command as user admin
pg_dump -p 5555 mcdb >/tmp/mc_database_backup.sql
This will dump the database schema and content in "/tmp/mc_database_backup.sql" file
binodprasai
17 Posts
0
July 21st, 2013 19:00
Thanks Amol, Is there a way to redirect the backup to other storage device (other then Avamar)?
martingoh
31 Posts
0
September 1st, 2013 22:00
If there is no replication server, and if the utility node goes down, how do you recover it?
Can I say there is no redundancy protection like the storage nodes?
umichklewis
1.2K Posts
0
September 4th, 2013 07:00
As mentioned above, the MCS database is stored on the GSAN itself. That means, when the utility node is replaced, EMC Support can recover the MCS database from the GSAN back to the newly-replaced node.