[Hadoop-common-user] Hadoop Backup & Restore

On Tue, Aug 30, 2011 at 7:05 AM, Avi Vaknin wrote:

Hi All,

While discussing about Hadoop backup & restore plan with my team I thought
about a scenario I wanted to ask you about:

I wonder what will happen following the steps below:

1. Backup the namenode's metadata (fsimage & edits log).

2. Adding files to the Hadoop clutser.

3. Deleting files from the Hadoop cluster.

4. Corruption in the namenode's metadata or whatever.

5. Restoring the namenode's metadata which I backed up (step 1).

How the namenode handle the blocks written or deleted before the corruption
?

Will I have access to them ? Is there any procedure I need to do in order
to
"fix" the gap created in the time since the last backup?



Thanks.



Avi

From: [email protected]
To: [email protected]; [email protected]
Subject: Hadoop multi tier backup
Date: Tue, 30 Aug 2011 16:54:07 +0000

All,

We were discussing how we would backup our data from the various environments we will have and I was hoping someone could chime in with previous experience in this. My primary concern about our cluster is that we would like to be able to recover anything within the last 60 days so having full backups both on tape and through distcp is preferred.

Out initial thoughts can be seen in the jpeg attached but just in case any of you are weary of attachments it can also be summarized below:

Prod Cluster --DistCp--> On-site Backup cluster with Fuse mount point running NetBackup daemon --NetBackup--> Media Server --> Tape

One of our biggest grey areas so far is how do most people accomplish incremental backups? Our thought was to tie this into our NetBackup configuration as this can be done for other connectors but we do not see anything for HDFS yet.

Thanks,
Matt
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled
to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and
all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.

All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto, including its
subsidiaries. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware".
Monsanto, along with its subsidiaries, accepts no liability for any damage caused by any such code transmitted by or accompanying
this e-mail or any attachment.


The information contained in this email may be subject to the export control laws and regulations of the United States, potentially
including but not limited to the Export Administration Regulations (EAR) and sanctions regulations issued by the U.S. Department of
Treasury, Office of Foreign Asset Controls (OFAC). As a recipient of this information you are obligated to comply with all
applicable U.S. export laws and regulations.