• February 23, 2025, 01:05:20 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Backing up for the new firmware  (Read 3894 times)

Disk1of5

  • Level 1 Member
  • *
  • Posts: 9
Backing up for the new firmware
« on: September 17, 2009, 04:36:51 PM »

hey all, i have an idea of how i'm going to back this all up but i just wanted to run it past you all for feed back..

so when 1.08 comes out with out a doubt i am going to want EXT3 as my filesystem
my current setup is raid 1 so heres what  im thinking about doing

first off.. buying a new HD..
take 1 of the old hardrives out and place the new one in .. install 1.08 and then initialize both of them with raid1 on ext3  then place the old HD on a linux box mount the files and then send them over the network to the new fancy ext3 raid1 that way i have a backup encase any thing happends with 1.08
 
fool-proof or fool-ish?

Thanks!
Logged

fordem

  • Level 10 Member
  • *****
  • Posts: 2168
Re: Backing up for the new firmware
« Reply #1 on: September 17, 2009, 05:52:10 PM »

It's not fool-proof, but it's also not fool-ish.

I would add one addtional step.

When you remove the hard disk, before you install the new disk and reformat, take the time to install the removed disk and verify that you have access to the data using your proposed methods.  If perchance you don't, you can still return the disk to the DNS-323, which - because you have not powered it up - does not know that the disk was ever removed.

I have not done what you are trying to do with a linux system, but I have done somthing similar using Windows and the ext2ifs file system drivers.
Logged
RAID1 is for disk redundancy - NOT data backup - don't confuse the two.

Disk1of5

  • Level 1 Member
  • *
  • Posts: 9
Re: Backing up for the new firmware
« Reply #2 on: September 17, 2009, 07:36:25 PM »

that extra step is a great idea but is there  a way i can verify the data integrity is the exact same.. like run a md5 sum on both drives or something? if so any suggestions on tools?
Logged