1mysql‐zrm‐manage‐backup(1)                             mysql‐zrm‐
2manage‐backup(1)
3
4
5
6NNAAMMEE
7       mmyyssqqll‐‐zzrrmm‐‐mmaannaaggee‐‐bbaacckkuupp  ‐   Utility   to  manage  on‐line
8(quick) snapshot
9       backups  created  with  the  ’’’msql‐zrm‐backup  ‐‐backup‐
10type  quick’’’
11       option.
12
13SSYYNNOOPPSSIISS
14       mmyyssqqll‐‐zzrrmm‐‐mmaannaaggee‐‐bbaacckkuupp
15                       [‐‐‐‐ccoonnvveerrtt‐‐ttoo‐‐rreegguullaarr|‐‐‐‐mmoouunntt‐‐ssnnaappsshhoottss|‐‐‐‐rreemmoovvee‐‐bbaacckkuupp
16                       [‐‐‐‐ssoouurrccee‐‐ddiirreeccttoorryy _d_i_r_e_c_t_o_r_y___n_a_m_e]
17                       [‐‐‐‐bbaacckkuupp‐‐sseett _n_a_m_e]
18                       [‐‐‐‐ooppttiioonnss‐‐ffiillee conf_file]
19                       [‐‐‐‐ttmmppddiirr _t_e_m_p___d_i_r_e_c_t_o_r_y]
20                       [‐‐‐‐qquuiieett|‐‐‐‐nnoo‐‐qquuiieett]
21                       [‐‐‐‐vveerrbboossee]
22                       [‐‐‐‐hheellpp]
23
24DDEESSCCRRIIPPTTIIOONN
25       Use  this utility to  convert  on‐line  (quick)  snapshot‐
26based  backups
27       (created   with   the   ’’’msql‐zrm‐backup   ‐‐backup‐type
28quick’’’ option) to
29       standard  (near‐line)  ZRM for MySQL archive, or to remove
30unwanted quick
31       backups from the MySQL server. It is not possible to  con‐
32vert a standard
33       ZRM for MySQL backup archive to a quick backup.
34
35       Please    see    the    ZRM    for   MySQL   documentation
36(http://mysql‐
37       backup.zmanda.com/)  for procedures on  how  to  configure
38and use ZRM for
39       MySQL.
40
41
42OOPPTTIIOONNSS
43       ‐‐‐‐ccoonnvveerrtt‐‐ttoo‐‐rreegguullaarr|‐‐‐‐mmoouunntt‐‐ssnnaappsshhoottss|‐‐‐‐rreemmoovvee‐‐bbaacckkuupp
44              The  ‐‐‐‐ccoonnvveerrtt‐‐ttoo‐‐rreegguullaarr  option  converts a quick
45snapshot backup
46              (created  with  the  ’’’msql‐zrm‐backup   ‐‐backup‐
47type  quick’’’
48              option) to a standard backup. It does this by copy‐
49ing  the  data
50              from  the  snapshot  to the ZRM server  destination
51directory and
52              then deleting the snapshot.
53
54              The  ‐‐‐‐rreemmoovvee‐‐bbaacckkuupp  option  simply   removes  the
55backup  without
56              copying the data first.
57
58              The  ‐‐‐‐mmoouunntt‐‐ssnnaappsshhoottss  option  is  provided  as  a
59convenience; use
60              it  to  mount  a  snapshot  volume  that  has  been
61inadvertently
62              unmounted (such as when a server has been  re‐boot‐
63ed).
64
65       ‐‐‐‐ssoouurrccee‐‐ddiirreeccttoorryy _d_i_r_e_c_t_o_r_y___n_a_m_e]
66              Specifies  the  quick  snapshot‐based  backup to be
67managed.
68
69       ‐‐‐‐bbaacckkuupp‐‐sseett _n_a_m_e
70              Specify  the  backup‐set.  The  default  value   is
71BBaacckkuuppSSeett11. If such
72              a value is already present, it will be used.
73
74       ‐‐‐‐ooppttiioonnss‐‐ffiillee _c_o_n_f___f_i_l_e
75              Set   the   file   along    with    full   pathname
76that   contains
77              mmyyssqqll‐‐zzrrmm‐‐bbaacckkuupp  configuration  options; this file
78has the same
79              format as mmyyssqqll‐‐zzrrmm..ccoonnff(5).
80
81       ‐‐‐‐ttmmppddiirr _t_e_m_p___d_i_r
82              Full path of the directory to  be  used  for  stor‐
83ing  temporary
84              files  and  directories  on the backup host. If not
85specified it
86              defaults  to  the system  specified  temporary  di‐
87rectory  on  the
88              backup host, e.g. //ttmmpp.
89
90       ‐‐‐‐qquuiieett|‐‐‐‐nnoo‐‐qquuiieett
91              Choose  ‐‐‐‐qquuiieett  to  suppress display of  log  mes‐
92sages on ssttddoouutt.
93              Choose _n_o_‐_q_u_i_e_t to display the log messages ssttddoouutt.
94Default  is
95              ‐‐‐‐nnoo‐‐qquuiieett.
96
97       ‐‐‐‐vveerrbboossee
98              Provide  verbose  output  in the  log.  Default  is
99that verbose is
100              turned off and a terse output is generated.
101
102       ‐‐‐‐hheellpp  Displays  the help message and  exits.  This  com‐
103mand  line  only
104              parameter cannot be specified in the  configuration
105file.
106
107FFIILLEESS
108       //vvaarr//lliibb//mmyyssqqll‐‐zzrrmm
109              Directory under which all backup data is stored.
110
111
112       //eettcc//mmyyssqqll‐‐zzrrmm//_b_a_c_k_u_p _s_e_t _n_a_m_e//mmyyssqqll‐‐zzrrmm..ccoonnff
113              The ZRM for MySQL configuration file.
114
115
116RREETTUURRNN VVAALLUUEESS
117       On  success,  zero is returned. On error, a non‐zero value
118is returned.
119
120
121SSEEEE AALLSSOO
122       mysql‐zrm(1),      mysql‐zrm‐backup(1),     mysql‐zrm‐man‐
123age‐backup(1),
124       mysql‐zrm‐restore(1),                  mysql‐zrm‐check(1),
125mysql‐zrm‐list(1),
126       mysql‐zrm‐getconf(1),   mysql‐zrm‐parse‐binlogs(1), mysql‐
127zrm‐purge(1),
128       mysql‐zrm‐verify‐backup(1),     mysql‐zrm‐abort‐backup(1),
129mysql‐zrm‐sched‐
130       uler(1), mysql‐zrm‐reporter(1), mysql‐zrm.conf(5),  mysql‐
131dump(1), mysql‐
132       binlog(1),   mysql(1),  lvm(8),  Zmanda  Recovery  Manager
133for   MySQL
134       (http://mysqlbackup.zmanda.com/)
135
136
137AAUUTTHHOORR
138       Zmanda Inc. (http://www.zmanda.com)
139
140
141
142Zmanda, Inc.                   ZRM FOR  MySQL  2.1     mysql‐zrm‐
143manage‐backup(1)
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198