any consideration to store archive data on disks

[Hanry Zhou]

I know that the regular method to archive data (keep data for 3 years) is to store data on tape media. However, for some reasons, we decided not to use tape media, but use disk space instead.

Here is a few points I can think of
1. the file system could or should not be included in backup data list.
2. I am not sure if we should mount these file systems everytime when we boot up the system
3.....

Is there any other issues we should consider, what we should do, or should not do with regards using disk space to archive data as a long term strategy plan.

Appreciate your input.

[Albert Smith_1]

Most orginizations have LEGAL requirements to keep data around and vaulted at an offsite location. I would check with your manager and your legal department to make sure you are in compliance.

I would with out a doubt get the data to a removable media and have it secured. If you have a disk failure and it's not properly protected you could lose the data.

As it relates to storage on disk the data is only as secure as the system. If the data is on a tape and out of the system you recover storage and you can feel secure that the data is not being changed.

[Hoang Minh Tuan]

Hi,

Because you didn't tell exactly what type of your archive data, so it 's difficult to include or exclude what file system you should backup.

In my server system, I also configured to store data in disk daily. This is my criterias:
- The disks storing data is high availabilty (in diskarray)and secure (have a restric policy to access)
- The procedure of backup do not interfere the system performance. (I scheduled backup at midnight when system is idle)
- This data backup is continuous changing (not stable data). So that my data backing up to disks is Oracle archive file, data file and control file.
Take care: before backing data file, control file you must run a script to alter these file to switch to backup mode.

- File system (O.S) is not chaning very much so you could make a ignite tape to backup all file system in your server. Before creating an ignite tape, backing up LVM config file (vgcfgbackup), map file (vgexport) and copy it to /tmp and to disks

HMT

[Rashid Hamid]

Hi Hanry

I'm also use disks to store arhive data for some reasons into my R40 AIX box.
For my case, i have 2 sets of backup, local and offsite backup. I'm running the backup only if any changes occured.
To play safe with the achive data, I do not mount it. Only mount if somebody request it.

Regards
Rashid

[Hanry Zhou]

Rashid,

I am going to create a fs using lvm, but withough mounting it. Is there any way I can secure the fs to prevent anybody remove it by accident? There is the possibility that somebody may mistakenly think this is abandoned fs, and therefore to re-use the space.

Thanks,

[Bill Hassell]

You can always make your backup, then umount the volume, change /etc/fstab to mount the archive volume as read-only and mount it again. At least it will always be visible. To add more to the volume, un-mount it, change fstab and re-mount it. And of course, make sure there is some sort of off-site backup of this data for the possibility of smoke-and-rubble. The use of on-site disks for backup are for 'oops' restores and history, not disaster recovery.

[Hanry Zhou]

Anybody else has input on this?
I need to know any considerations in a big picture. Any issues we need to take care of?

I'm not asking if we we should use disk or tape media. Managers have already decided to use disk.

[A. Clay Stephenson]

Mounting these as read-only filesystems is probably the least-evil approach. If mounted read-only, the data are safe from ordinary users and admins will be much less likely to find some "unused" disk and find a use for it. Eventhough the data are static, I would definitely back it up periodically because it is possible that your offsite storage facility might make a mistake and return the wrong media so that your only backup is recycled.

One other approach to consider with very large amounts of data is the hierarchical filesystem. The idea is that often accessed data are stored on fast devives (magnetic disks), less often accessed data are stored or magneto-optical disks, and seldom accessed data are might be stored on tape. To an application this looks like a seamless huge filesystem -- sone data are accessed rapidly and other data might require 60 seconds or so to access but it's all there. The data are automatically migrated to faster or slower media based upon usage. HP had a product called OmniStorage that was built on top of a conventional vxfs filesystem.

[Mark Ellzey]

Hanry,

Just to re-iterate what Bill said about 'smoke-and-rubble': There may be a legal issue with archiving only to on-site disk. At least, removable media can be kept off-site. In case of a disaster, the off-site backup can be restored at any DR site. If your only backup is a charred, mashed disk, that won't help much.

Just my 2cts worth.
Mark

[Michael D. Zorn]

You might also consider optical disk or DVD. We used to use mag tapes (10.5" reels), but they're becoming unreliable - both the tapes and the drives. (We use OD now.)

You could still run the backup to your archive disks, then copy those disks to OD or DVD whenever it's reasonable.

Keeping the archives off-site is highly recommended. (Finding an off-site location may not be easy.)

The thing you make archive backups for is the time when the earthquake, fire or flood comes along and carries away all your hardware.

"2. I am not sure if we should mount these file systems everytime when we boot up the system."

No - don't mount them until you make the backup, then unmount them. Only root should be able to mount them.