Ssd Back-up Retrieval Procedure

The purpose of this procedure is to safeguard all the important/working files and databases at IRRI SSD/GIS Workstations and laptops. This is also vital to SSD’s Identified Risks (464-220-SSD) Loss of Research data in compliance with IRRI’s Business Continuity Management (BCM). To the event that a data was loss a quick recovery plan is in place.
View more...
   EMBED

Share

Preview only show first 6 pages with water mark for full document please download

Transcript

SOCIAL SCIENCES DIVISION BACKUP/ RETRIEVAL PROCEDURE Objective: The purpose of this procedure is to safeguard all the important/working files and databases at IRRI SSD/GIS Workstations and laptops. This is also vital to SSDs Identified Risks !"#"$%%&$SSD' Loss of Researc !ata in compliance with IRRIs (usiness )ontinuit* +anagement !()+'. To the event that a data was loss a ,uick recover* plan is in place. Sco"e a#! !e$i%itatio# This procedure covers data backup and recovery of • -ll SSD Research database !doc. pdf. /ls. ppt. t/t. db. mdb etc.' • SSD applications data !S0SS. ST-T-' • +S 1utlook !pst' • 1fficial media content2 recorded interviews. presentations. conferences. seminars. important events in SSD. o -udio !mp3. wav' o 4ideo !mp". avi. mpeg. mov' o 0ictures or scanned documents related to work !5peg. bmp.. pdf' Not covered are data stored in • 6S( 7lash drive • 0artition Drive )2 !1perating S*stem' • 8-S !ITS handles the backup/retrieval' • Source file capacit* is larger than backup storage capacit* !e/. 9%&Gb of file : ;&G( e/ternal drive' • Remote -ccess of backed$up data • 8on$official data Proce!&re +aDD with a )apacit* of "&Gb up to 9Terab*te. Identified SSD ?/ternal (ackup =ist./ls '( Bac)&" Soft*are a. 0roprietar* Software !Iomega. +a/tor. Seagate. -cronis' b. )obian (ackup !open source' +( Devices , ?/ternal >DD !6S(. eS-T-. firewire "&&' ranging from "&Gigab*te$" Terrab*te of capacit*. -( Ti%e of Bac)&" . 0referred time of backup is set !ai$/ and will start at '+ #oo#. with this the user can check if there are an* errors with the backup Take note that a user ma* also e/perience downtime during this process. It ma* a take a few hours depending on the amount of backup files. 0( 1o!e of Bac)&" . &ser ca# !eci!e *ic bac)&" is i!ea$ a' 2&$$ bac)&"s( This is a complete set of all of the data *ou want to back up. @ouAll want to keep a current backup of *our entire s*stem around. but *ou donAt need to do these backups dail*. as most of *our files donAt change ever* da*. and full backups are time$consuming. b' Differe#tia$ bac)&"s( This is the set of an* files that have changed since the last full backup. These backups take less time and space than a full backup but more than an incremental backup. c' I#cre%e#ta$ bac)&"s( This is the set of files that have changed since the previous backup !whether it is a differential. incremental. or full backup'. These backups take the least time and space. but. in the event of data loss. *ouAll need to restore data from several backups !the last full backup. last differential. and all the incremental backups since the last differential' and restore them in precisel* the correct order. )onsumes more disk space and time 3( 2i$es #ee!e! to bac)&" . +ostl* files needed to backup are located on the partitioned drive !data drive'. ITS alread* imposed a standard of deplo*ing units with partitioned drive to which the user should allocate all the working documents. e/change folder. research data in case of an 1.S. breakdown. recover* will be less time consuming. 4( Effective Data Bac)&" a#! Recover/ . To make sure *ou have an effective data backup and recover* s*stem. *ouAll need to plan in detail for disaster recover*. • 0erform a comparison of source data to backup data using (e*ond compare. • Remove duplicate files !since backup is one wa* it is ideal to check the • 1ld files !more than B *ears' can be transferred to a disc !)D/D4D/ (lue ra* medium' and stored in a vault. 5( Preve#tive 1ai#te#a#ce ,?/ternal storage are prone to malfunction if mishandled. It is important to perform preventive maintenance b*2 • 0erforming defragmentation • Disk clean$up • -void unplugging especiall* while read/write is in progress • 6se the Csafel* remove deviceD when unplugging a device • When travelling !for mobile storage' o 0lace device on a flat surface o -void lifting the storage device especiall* when the disk is in its spindle process. since >DDs are ver* fragile. • If temperature is getting high it is advisable to turn the device off 6( SSD NAS , ITS provided SSD a 8etwork -llocated Storage !8-S' with a capacit* of 9 Terab*te accessible to IRRIs network onl*. )harges appl* per megab*te. with that ITS also handles the backup and recover*. +anaging the repositor* will be the responsibilit* of ITS and IT )oordinators of SSD. -ccess level is administered b* D. Deleon and -. Rala. - draft overview of the folders and re,uired access levels set in EEvirriadfsEssd 2o$!er Na%e P&r"ose User Access Ca"acit/ -rchive )oncluded SSD 0ro