TEXT 12
Backups.xml Guest on 26th June 2020 08:13:03 PM
  1. <article>
  2. <title>CS Disaster Recovery Plan</title>
  3. <articleinfo>
  4. <legalnotice>
  5. <para>
  6. This document is a
  7. <application>DocBook</application>
  8. <literal>article</literal>
  9. and should only be edited as such at
  10. <filename>~sysadmin/docs/RecoveryBible/backups.xml</filename>
  11. </para>
  12. </legalnotice>
  13. <revhistory>
  14. <revision>
  15. <revnumber>$Revision $</revnumber>
  16. <date>$Date: 2010/01/25 20:34:49 $</date>
  17. <authorinitials>$Author: leblancd $</authorinitials>
  18. <revremark/>
  19. </revision>
  20. <revision>
  21. <revnumber>1.4</revnumber>
  22. <date>2010/01/25 12:30:24 </date>
  23. <authorinitials>leblancd</authorinitials>
  24. <revremark>updated for new NetApp filer, tape library, TiNa version</revremark>
  25. </revision>
  26. <revision>
  27. <revnumber>1.3</revnumber>
  28. <date>2008/12/24 23:41:17</date>
  29. <authorinitials>leblancd</authorinitials>
  30. <revremark>resized screenshot images</revremark>
  31. </revision>
  32. <revision>
  33. <revnumber>1.2</revnumber>
  34. <date>2008/12/24 03:37:28</date>
  35. <authorinitials>leblancd</authorinitials>
  36. <revremark>Replaced SAFE.cs with FILER.cs</revremark>
  37. </revision>
  38. <revision>
  39. <revnumber>1.1</revnumber>
  40. <date>2006/04/07 23:41:28</date>
  41. <authorinitials>leblancd</authorinitials>
  42. <revremark>marked up in DocBook XML (from DocBook SGML <- LyX/LaTeX)</revremark>
  43. </revision>
  44. <revision>
  45. <revnumber>1.0</revnumber>
  46. <date>April 7, 2006</date>
  47. <author>
  48. <surname>LeBlanc</surname>
  49. </author>
  50. <revremark>initial</revremark>
  51. </revision>
  52. </revhistory>
  53. </articleinfo>
  54. <section>
  55. <title>Introduction</title>
  56. <para>
  57. The CS support model of servers and workstations is that no permanent/semi-permanent data that is to be kept should be stored locally. All permanent data is stored centrally on the CS file server,
  58. <systemitem class="fqdomainname">filer.cs.caltech.edu</systemitem>
  59. (
  60. <systemitem class="systemname">filer</systemitem>
  61. ). This enables any computer to be installed/rebuilt/upgraded quickly since there is no persistent data to be migrated, meanwhile making disaster recovery easy since there is only one device to backup. It is true that while backups are important, it is restoration that is most important since that is the entire point of backing up data in the first place. This document will cover both backup and restoration of user data, in addition to procedures for total disaster.
  62. </para>
  63. </section>
  64. <section>
  65. <title>Implementation</title>
  66. <section>
  67. <title>Software</title>
  68. <para>
  69. Software used is Time Navigator v4.2 (TiNa), made by Atempo, installed locally on
  70. <systemitem class="fqdomainname">safe.cs.caltech.edu</systemitem>
  71. . There is a 140GB disk dedicated to storage of TiNa's catalog of tapes/data.
  72. </para>
  73. <section>
  74. <title>
  75. Files specific to
  76. <systemitem class="server">filer</systemitem>
  77. :
  78. </title>
  79. <itemizedlist>
  80. <listitem>
  81. <para>
  82. <filename class="directory">/opt/tina4/*</filename>
  83. </para>
  84. </listitem>
  85. <listitem>
  86. <para>
  87. <filename class="directory">/etc/init.d/tina.tina4</filename>
  88. </para>
  89. </listitem>
  90. <listitem>
  91. <para>
  92. <filename class="directory">/etc/services</filename>
  93. :
  94. </para>
  95. <programlisting># Time Navigator (TiNa) tina 2527/tcp tina-msg 2528/udp</programlisting>
  96. </listitem>
  97. </itemizedlist>
  98. </section>
  99. <section>
  100. <title>
  101. Files specific to
  102. <systemitem class="server">safe</systemitem>
  103. :
  104. </title>
  105. <para>
  106. Everything is located in
  107. <filename>/opt/tina4</filename>
  108. , including the "catalog" (see also
  109. <xref linkend="catalog"/>
  110. ).
  111. </para>
  112. </section>
  113. </section>
  114. <section>
  115. <title>Hardware</title>
  116. <para>
  117. Other than
  118. <systemitem class="server">safe</systemitem>
  119. (the host running the TiNa software), there is the SpectraLogic T50e tape library that is directly attached to filer via fiber channel interface. The T50e also has a web interface, protected with administrative password, located at
  120. <uri>http://spectrat50e.cs.caltech.edu</uri>
  121. , which will allow remote tape changes and other utilities.
  122. </para>
  123. </section>
  124. <section>
  125. <title>Operational Overview</title>
  126. <para>
  127. As the "orchestrator" of the backup and restoration process,
  128. <systemitem class="server">safe</systemitem>
  129. sends commands to the TiNa client (
  130. <systemitem class="server">filer</systemitem>
  131. ) pertaining to the data and tape manipulation.
  132. <systemitem class="server">safe</systemitem>
  133. does not do any actual data backup/restoration. During a backup process,
  134. <systemitem class="server">safe</systemitem>
  135. sends commands over the network to the TiNa daemon process on
  136. <systemitem class="server">filer</systemitem>
  137. to:
  138. </para>
  139. <itemizedlist>
  140. <listitem>
  141. <para>load a tape with the appropriate label,</para>
  142. </listitem>
  143. <listitem>
  144. <para>begin backup of a specific "strategy" to the tape,</para>
  145. </listitem>
  146. <listitem>
  147. <para>
  148. send output of the process (status messages) back to
  149. <systemitem class="server">safe</systemitem>
  150. , and
  151. </para>
  152. </listitem>
  153. <listitem>
  154. <para>output a list of files that were backed up such that safe can process the metadata.</para>
  155. </listitem>
  156. </itemizedlist>
  157. <para>
  158. So, safe becomes aware of the data that was backed up, which tapes store files and which tapes are loaded in the tape library. This metadata involved becomes the "TiNa catalog" (see also
  159. <xref linkend="catalog"/>
  160. ).
  161. </para>
  162. </section>
  163. </section>
  164. <section>
  165. <title>Configuration</title>
  166. <section>
  167. <title>Classes</title>
  168. <para>
  169. TiNa employs the concept of "classes" in a backup strategy. This allows sectioning of the data to be backed up such that backup does not become an all-or-nothing process. Classes are declared on
  170. <systemitem class="server">safe</systemitem>
  171. in
  172. <filename class="directory">/opt/tina4/catalog0/vol_description</filename>
  173. :
  174. </para>
  175. <programlisting>DIR vol ( DIR infosys("/vol/infosys") DIR install("/vol/install") DIR software("/vol/software") DIR staff("/vol/staff") DIR students("/vol/students") DIR courses("/vol/courses") DIR complexity( DIR users("/vol/complexity/users") ) DIR gg( DIR users("/vol/gg/users") ) DIR geometry( DIR users("/vol/geometry/users") ) DIR infospheres( DIR users("/vol/infospheres/users") ) DIR iqi( DIR users("/vol/iqi/users") ) DIR mls( DIR users("/vol/mls/users") ) DIR multires( DIR users("/vol/multires/users") ) DIR networks( DIR users("/vol/networks/users") ) DIR perflab( DIR users("/vol/perflab/users") ) DIR theory( DIR users("/vol/theory/users") ) )</programlisting>
  176. <para>
  177. Each entry, or
  178. <literal>DIR</literal>
  179. , corresponds to a directory on the system to be backed up. Using this scheme, we can choose to back up
  180. <filename class="directory">ic_users</filename>
  181. , or
  182. <filename class="directory">instruction</filename>
  183. , or even back up the entire
  184. <filename class="directory">vol</filename>
  185. tree.
  186. </para>
  187. </section>
  188. <section>
  189. <title>Backup Strategies</title>
  190. <para>
  191. For our purposes, we have divided all the data that needs to be backed up into 3 backup strategies;
  192. <emphasis>instruction</emphasis>
  193. ,
  194. <emphasis>staff/infrastructure</emphasis>
  195. , and
  196. <emphasis>research</emphasis>
  197. that are named "A", "B", and "D" respectively. Although TiNa allows us to backup more than one class in a strategy, our strategies "A", "B", and "D" only backup single classes, to keep things as simple as possible; i.e., when backup strategy "A" launches, only files in
  198. <filename class="directory">/vol/courses</filename>
  199. and
  200. <filename class="directory">/vol/students</filename>
  201. are backed up.
  202. </para>
  203. </section>
  204. <section>
  205. <title>Tape Cartridge Pools</title>
  206. <para>Cartridge pools in TiNa allow administrators to easily distinguish tapes from one another, and also specify which tapes get written in which backup strategies. Keeping with our simple implementation, we have pools named "INS-L0", "INS-L1", "RES-L0", "RES-L1", "STINF-L0", and "STINF-L1". For each tape in a cartridge pool, TiNa writes a label at the beginning of the tape that declares which pool it belongs to. This label is in the form of <pool>-<number>; i.e., RES-L0-00001 for the first tape in the RES-L0 cartridge pool.</para>
  207. <para>You may already see a pattern emerging with classes, strategies and cartridge pools. Of course there's a pattern! We like to keep things as simple as possible! Here is a basic matrix of what gets backed up and where it goes.</para>
  208. <informaltable>
  209. <tgroup cols="5">
  210. <colspec align="center" colsep="1" colwidth="0.75in" rowsep="1"/>
  211. <colspec align="center" colsep="1" colwidth="1.2in" rowsep="1"/>
  212. <colspec align="center" colsep="1" colwidth="1in" rowsep="1"/>
  213. <colspec align="center" colsep="1" colwidth="2.5in" rowsep="1"/>
  214. <colspec align="center" colsep="1" colwidth="1.2in" rowsep="1"/>
  215. <thead>
  216. <row>
  217. <entry align="center">Strategy</entry>
  218. <entry>Backup Level</entry>
  219. <entry>Class</entry>
  220. <entry>Directory</entry>
  221. <entry align="center">Cartridge Pool</entry>
  222. </row>
  223. </thead>
  224. <tbody>
  225. <row>
  226. <entry>A</entry>
  227. <entry>0</entry>
  228. <entry>instruction</entry>
  229. <entry>
  230. <filename>filer:/vol/courses & students</filename>
  231. </entry>
  232. <entry>INS-L0</entry>
  233. </row>
  234. <row>
  235. <entry>A</entry>
  236. <entry>1 (Incr)</entry>
  237. <entry>instruction</entry>
  238. <entry>
  239. <filename>filer:/vol/courses & students</filename>
  240. </entry>
  241. <entry>INS-L1</entry>
  242. </row>
  243. <row>
  244. <entry>B</entry>
  245. <entry>0</entry>
  246. <entry>staff & infrastructure</entry>
  247. <entry>
  248. <filename>filer:/vol/staff, infosys, install, software</filename>
  249. </entry>
  250. <entry>STINF-L0</entry>
  251. </row>
  252. <row>
  253. <entry>B</entry>
  254. <entry>1 (Incr)</entry>
  255. <entry>staff & infrastructure</entry>
  256. <entry>
  257. <filename>filer:/vol/staff, infosys, install, software</filename>
  258. </entry>
  259. <entry>STINF-L1</entry>
  260. </row>
  261. <row>
  262. <entry>D</entry>
  263. <entry>0</entry>
  264. <entry>research</entry>
  265. <entry>
  266. <filename>filer:/vol/complexity, geometry, gg, iqi, mls, multires, networks, perflab, theory</filename>
  267. </entry>
  268. <entry>RES-L0</entry>
  269. </row>
  270. <row>
  271. <entry>D</entry>
  272. <entry>1 (Incr)</entry>
  273. <entry>research</entry>
  274. <entry>
  275. <filename>filer:/vol/complexity, geometry, gg, iqi, mls, multires, networks, perflab, theory</filename>
  276. </entry>
  277. <entry>RES-L1</entry>
  278. </row>
  279. </tbody>
  280. </tgroup>
  281. </informaltable>
  282. </section>
  283. <section id="catalog">
  284. <title>Catalog</title>
  285. <para>
  286. It is important to keep a current catalog for TiNa's operation because without the organized metadata from previous backups the system cannot locate files needed for restoration in the event of a disaster. Hence, TiNa also backs up the catalog to tape. A catalog on tape also comes in handy when performing a total system restore in response to a catastrophic disaster in which all data is destroyed, including the TiNa software.
  287. <tip>
  288. <title>Humans with magnetic fingers:</title>
  289. <para>System administrators won't necessarily know which files are stored on which tapes, unless they can read the labels on the first 64KB of every backup tape, hence the need for the TiNa backup catalog.</para>
  290. </tip>
  291. </para>
  292. </section>
  293. <section>
  294. <title>Schedule</title>
  295. <para>The individual strategies are scheduled to launch as follows:</para>
  296. <itemizedlist>
  297. <listitem>
  298. <para>
  299. <emphasis role="bold">A</emphasis>
  300. : Full backup => monthly, first Friday of the month @ 19:00
  301. </para>
  302. </listitem>
  303. <listitem>
  304. <para>
  305. <emphasis role="bold">A</emphasis>
  306. : Incremental => weekly, every Friday @ 19:00
  307. </para>
  308. </listitem>
  309. <listitem>
  310. <para>
  311. <emphasis role="bold">B</emphasis>
  312. : Full backup => monthly, first Saturday of the month @ 01:00
  313. </para>
  314. </listitem>
  315. <listitem>
  316. <para>
  317. <emphasis role="bold">B</emphasis>
  318. : Incremental => weekly, every Saturday @ 01:00
  319. </para>
  320. </listitem>
  321. <listitem>
  322. <para>
  323. <emphasis role="bold">D</emphasis>
  324. : Full backup => monthly, first Sunday of the month @ 01:00
  325. </para>
  326. </listitem>
  327. <listitem>
  328. <para>
  329. <emphasis role="bold">D</emphasis>
  330. : Incremental => weekly, every Sunday @ 01:00
  331. </para>
  332. </listitem>
  333. </itemizedlist>
  334. <tip>
  335. <title>A word about schedules:</title>
  336. <para>Sometimes it is necessary to reschedule backups, since specific dates are not possible and the aim is to perform full backups at the beginning of the month.</para>
  337. </tip>
  338. </section>
  339. <section>
  340. <title>Data/Tape Retention</title>
  341. <para>Tapes are retained according to the level of backup accomplished, and when the backup was performed. Full (level 0) backups are retained for 3 months, with an annual kept for as long as possible. Incremental (level 1) backups are retained for a minimum of 3 weeks, or until the next full (level 0) backup is accomplished, or possibly longer depending on the number of current availability of blank tapes. This backup scheme provides:</para>
  342. <itemizedlist>
  343. <listitem>
  344. <para>files on tape for the last 3 weeks on a weekly basis</para>
  345. </listitem>
  346. <listitem>
  347. <para>files on tape for the last 3 months on a monthly basis</para>
  348. </listitem>
  349. <listitem>
  350. <para>files on tape for the last few years on an annual basis</para>
  351. </listitem>
  352. </itemizedlist>
  353. <tip>
  354. <title>When all goes as planned:</title>
  355. <para>A typical retention window will contain 3 weekly (level 1) sets, 3 monthly (level 0) sets, and 1 or 2 annual (level 0) sets of backup tapes.</para>
  356. </tip>
  357. </section>
  358. </section>
  359. <section>
  360. <title>Operation</title>
  361. <para>To describe the process of backup and restoration, the following sections will cover backup according to the above configuration and employ scenarios to describe the restoration process.</para>
  362. <section id="backup-fileserver-data">
  363. <title>Backup Operation (central file server data)</title>
  364. <orderedlist>
  365. <listitem>
  366. <para>
  367. Log into
  368. <systemitem class="server">safe</systemitem>
  369. via ssh:
  370. <userinput>ssh [email protected]</userinput>
  371. </para>
  372. </listitem>
  373. <listitem>
  374. <para>
  375. Source the TiNa Environment:
  376. <userinput>source /opt/tina4/tina4/.tina.sh</userinput>
  377. </para>
  378. </listitem>
  379. <listitem>
  380. <para>
  381. Launch the TiNa Administrative Interface:
  382. <userinput>tina_adm &</userinput>
  383. </para>
  384. </listitem>
  385. <listitem>
  386. <para>A graphical (remote X) login prompt will appear. Login using the sysadmin's credentials.</para>
  387. <screenshot>
  388. <mediaobject>
  389. <imageobject>
  390. <imagedata fileref="images/TiNaLogin.png"/>
  391. </imageobject>
  392. <caption>
  393. <para>
  394. Administrative login for
  395. <command>tina_adm</command>
  396. </para>
  397. </caption>
  398. </mediaobject>
  399. </screenshot>
  400. </listitem>
  401. <listitem>
  402. <para>A remote X session with Time Navigator tools will appear on the desktop.</para>
  403. <screenshot>
  404. <mediaobject>
  405. <imageobject>
  406. <imagedata contentdepth="50%" contentwidth="50%" fileref="images/TiNaAdmin.png" format="PNG"/>
  407. </imageobject>
  408. <caption>
  409. <para>TiNa Administrative Interface</para>
  410. </caption>
  411. </mediaobject>
  412. </screenshot>
  413. </listitem>
  414. <listitem>
  415. <para>
  416. In the upper left corner is
  417. <emphasis role="bold">terminus...</emphasis>
  418. , with
  419. <emphasis role="bold">A</emphasis>
  420. ,
  421. <emphasis role="bold">B</emphasis>
  422. , and
  423. <emphasis role="bold">D</emphasis>
  424. under the icon. Right-clicking on any of these strategies enables the operator to perform a full backup, incremental backup or edit the strategy itself.
  425. </para>
  426. </listitem>
  427. <listitem>
  428. <para>
  429. Viewing the schedule is possible by clicking
  430. <emphasis role="bold">Monitoring -></emphasis>
  431. <emphasis role="bold"> Task Viewer...</emphasis>
  432. , and adjusting the options to view the backups/timeframe as needed.
  433. </para>
  434. <screenshot>
  435. <mediaobject>
  436. <imageobject>
  437. <imagedata contentdepth="50%" contentwidth="50%" fileref="images/TiNaSchedule.png" format="PNG"/>
  438. </imageobject>
  439. <caption>
  440. <para>TiNa Schedule Interface</para>
  441. </caption>
  442. </mediaobject>
  443. </screenshot>
  444. </listitem>
  445. <listitem>
  446. <para>
  447. Viewing the event log is possible by clicking
  448. <emphasis role="bold">Monitoring</emphasis>
  449. ->
  450. <emphasis role="bold">Event Viewer...</emphasis>
  451. , or
  452. <emphasis role="bold">Job Manager...</emphasis>
  453. for backup operations that are currently processing.
  454. </para>
  455. <screenshot>
  456. <mediaobject>
  457. <imageobject>
  458. <imagedata contentdepth="40%" contentwidth="40%" fileref="images/TiNaEventLog.png" format="PNG"/>
  459. </imageobject>
  460. <caption>
  461. <para>TiNa Event Log Interface</para>
  462. </caption>
  463. </mediaobject>
  464. </screenshot>
  465. </listitem>
  466. <listitem>
  467. <para>
  468. Tape library operations are performed in the Library Manager window, accessible by right-clicking the library icon and choosing
  469. <emphasis role="bold">Operations</emphasis>
  470. .
  471. </para>
  472. <screenshot>
  473. <mediaobject>
  474. <imageobject>
  475. <imagedata contentdepth="50%" contentwidth="50%" fileref="images/TiNaLibrary.png" format="PNG"/>
  476. </imageobject>
  477. <caption>
  478. <para>TiNa Library Manager</para>
  479. </caption>
  480. </mediaobject>
  481. </screenshot>
  482. </listitem>
  483. </orderedlist>
  484. </section>
  485. <section>
  486. <title>Backup Operation (catalog data)</title>
  487. <para>
  488. The backup operation is essentially the same as outlined above in
  489. <xref linkend="backup-fileserver-data"/>
  490. , with the exception that the actual data backed up is different. In a catalog backup, metadata is written to tape rather than the actual data previously backed up.
  491. </para>
  492. <para>
  493. The catalog is backed up on a daily basis at 18:00. There is a "boot catalog" also written to
  494. <filename class="directory">/opt/tina4/tina4/Data.catalog0/Boot</filename>
  495. , with 7 historical copies. The "boot catalog" is used in the case that the system itself needs to be recovered and a catalog recreated.( see
  496. <xref linkend="no-catalog"/>
  497. )
  498. </para>
  499. </section>
  500. <section>
  501. <title>Recovery Operation</title>
  502. <section id="file-deleted">
  503. <title>Scenario: a file (or set of files) accidentally deleted</title>
  504. <procedure>
  505. <step>
  506. <para>
  507. In the TiNa Administration screen, select the
  508. <emphasis role="bold">safe.cs.caltech.edu...</emphasis>
  509. icon by right-clicking it, and choosing
  510. <emphasis role="bold">Restore & Archive Manager...</emphasis>
  511. to display the restoration login prompt.
  512. </para>
  513. <screenshot>
  514. <mediaobject>
  515. <imageobject>
  516. <imagedata fileref="images/TiNaLogin.png"/>
  517. </imageobject>
  518. <caption>
  519. <para>TiNa Admin Login</para>
  520. </caption>
  521. </mediaobject>
  522. </screenshot>
  523. </step>
  524. <step>
  525. <para>
  526. Login, using '
  527. <systemitem class="username">root</systemitem>
  528. ' as a username (and the filesystem-level password for that user).
  529. </para>
  530. </step>
  531. <step>
  532. <para>
  533. Using the
  534. <emphasis role="bold">Date Control</emphasis>
  535. on the left and the file browser, you can restore a specific version of a file, or simply restore the last backed up version of the file or directory.
  536. </para>
  537. <screenshot>
  538. <mediaobject>
  539. <imageobject>
  540. <imagedata contentdepth="40%" contentwidth="40%" fileref="images/TiNatina.png" format="PNG"/>
  541. </imageobject>
  542. <caption>
  543. <para>TiNa Restoration Interface</para>
  544. </caption>
  545. </mediaobject>
  546. </screenshot>
  547. </step>
  548. <step>
  549. <para>
  550. If you inadvertently attempt to restore a file that already exists, TiNa will warn you that you should use the
  551. <emphasis role="bold">Depth of Field</emphasis>
  552. on files that have been deleted.
  553. </para>
  554. <screenshot>
  555. <mediaobject>
  556. <imageobject>
  557. <imagedata contentdepth="85%" contentwidth="85%" fileref="images/TiNaRestoreInThePresent.png" format="PNG"/>
  558. </imageobject>
  559. <caption>
  560. <para>TiNa Depth of Field Warning</para>
  561. </caption>
  562. </mediaobject>
  563. </screenshot>
  564. </step>
  565. <step>
  566. <para>
  567. After selecting the appropriate file/directory and version thereof, right-click and choose
  568. <emphasis role="bold">Restore</emphasis>
  569. . A separate window will appear, prompting you for the options on restoration of the file/directory. You can choose to restore the file in its original location or to a different location, with or without metadata, permissions, etc.
  570. </para>
  571. <screenshot>
  572. <mediaobject>
  573. <imageobject>
  574. <imagedata contentdepth="50%" contentwidth="50%" fileref="images/TiNaRestore.png" format="PNG"/>
  575. </imageobject>
  576. <caption>
  577. <para>TiNa Restoration Options Dialog</para>
  578. </caption>
  579. </mediaobject>
  580. </screenshot>
  581. </step>
  582. <step>
  583. <para>TiNa will display a progress of the restoration process.</para>
  584. <screenshot>
  585. <mediaobject>
  586. <imageobject>
  587. <imagedata contentdepth="50%" contentwidth="50%" fileref="images/TiNaRestoreInProgress.png"/>
  588. </imageobject>
  589. <caption>
  590. <para>TiNa Restoration Progress</para>
  591. </caption>
  592. </mediaobject>
  593. </screenshot>
  594. </step>
  595. <step>
  596. <para>TiNa will display an "operation complete" status when restoration is complete.</para>
  597. <screenshot>
  598. <mediaobject>
  599. <imageobject>
  600. <imagedata contentdepth="85%" contentwidth="85%" fileref="images/TiNaRestoreComplete.png" format="PNG"/>
  601. </imageobject>
  602. <caption>
  603. <para>TiNa Restoration Complete Dialog</para>
  604. </caption>
  605. </mediaobject>
  606. </screenshot>
  607. </step>
  608. </procedure>
  609. </section>
  610. <section>
  611. <title>Scenario: no user files exist on the filer server</title>
  612. <para>
  613. Follow the same steps above in
  614. <xref linkend="file-deleted"/>
  615. , but instead of selecting individual files (in step 3) you should select the directories/volumes in which to restore. This may take considerable time, depending on how much data needs to be restored and how many changes (incremental) there have been since the last full level 0 backup.
  616. </para>
  617. </section>
  618. <section id="no-catalog">
  619. <title>Scenario: no catalog exists (TiNa is not aware of any backup data of user files)</title>
  620. <para>A manual restoration of TiNa's catalog needs to be performed.</para>
  621. <orderedlist>
  622. <listitem>
  623. <para>
  624. Perform the same procedure as
  625. <xref linkend="file-deleted"/>
  626. , but in step 1 right-click on
  627. <guimenuitem>catalog0.cat</guimenuitem>
  628. and choose
  629. <guimenuitem>Restore & Archive Manager...</guimenuitem>
  630. .
  631. </para>
  632. </listitem>
  633. </orderedlist>
  634. </section>
  635. <section>
  636. <title>Scenario: no catalog exists and catalog backup does not exist</title>
  637. <para>A manual Boot restoration of TiNa's "boot catalog" needs to be performed.</para>
  638. <orderedlist>
  639. <listitem>
  640. <para>
  641. After SSH'ing into
  642. <systemitem class="server">safe</systemitem>
  643. as
  644. <systemitem class="username">root</systemitem>
  645. , and sourcing
  646. <filename>.tina.sh</filename>
  647. , on the command-line enter: tina_init -boot /opt/tina4/tina4/Data.catalog0/Boot/bootxxxx.cod where xxxx represents the last boot-catalog file written.
  648. </para>
  649. </listitem>
  650. </orderedlist>
  651. </section>
  652. <section>
  653. <title>Scenario: no data exists on file server AND backup server</title>
  654. <para>
  655. In the unlikely event that all data is destroyed the backup server (
  656. <systemitem class="server">safe</systemitem>
  657. ) which runs the TiNa software needs to also be restored.
  658. </para>
  659. <orderedlist>
  660. <listitem>
  661. <para>
  662. Re-install the operating system on
  663. <systemitem class="server">safe</systemitem>
  664. .
  665. </para>
  666. </listitem>
  667. <listitem>
  668. <para>
  669. Re-install the TiNa software on
  670. <systemitem class="server">safe</systemitem>
  671. .
  672. </para>
  673. </listitem>
  674. <listitem>
  675. <para>
  676. Proceed to
  677. <xref linkend="no-catalog"/>
  678. and restore the catalog.
  679. </para>
  680. </listitem>
  681. <listitem>
  682. <para>
  683. Proceed to
  684. <xref linkend="file-deleted"/>
  685. and restore all files.
  686. </para>
  687. </listitem>
  688. </orderedlist>
  689. </section>
  690. </section>
  691. </section>
  692. </article>

Paste is for source code and general debugging text.

Login or Register to edit, delete and keep track of your pastes and more.

Raw Paste

Login or Register to edit or fork this paste. It's free.