4 \section*{Automatic Volume Recycling}
5 \label{_ChapterStart22}
6 \index[general]{Recycling!Automatic Volume }
7 \index[general]{Automatic Volume Recycling }
8 \addcontentsline{toc}{section}{Automatic Volume Recycling}
10 By default, once Bacula starts writing a Volume, it can append to the
11 volume, but it will not overwrite the existing data thus destroying it.
12 However when Bacula {\bf recycles} a Volume, the Volume becomes available
13 for being reused, and Bacula can at some later time overwrite the previous
14 contents of that Volume. Thus all previous data will be lost. If the
15 Volume is a tape, the tape will be rewritten from the beginning. If the
16 Volume is a disk file, the file will be truncated before being rewritten.
18 You may not want Bacula to automatically recycle (reuse) tapes. This would
19 require a large number of tapes though, and in such a case, it is possible
20 to manually recycle tapes. For more on manual recycling, see the section
21 entitled \ilink{ Manually Recycling Volumes}{manualrecycling} below in this
24 Most people prefer to have a Pool of tapes that are used for daily backups and
25 recycled once a week, another Pool of tapes that are used for Full backups
26 once a week and recycled monthly, and finally a Pool of tapes that are used
27 once a month and recycled after a year or two. With a scheme like this, the
28 number of tapes in your pool or pools remains constant.
30 By properly defining your Volume Pools with appropriate Retention periods,
31 Bacula can manage the recycling (such as defined above) automatically.
33 Automatic recycling of Volumes is controlled by three records in the {\bf
34 Pool} resource definition in the Director's configuration file. These three
39 \item VolumeRetention = \lt{}time\gt{}
43 The above three directives are all you need assuming that you fill
44 each of your Volumes then wait the Volume Retention period before
45 reusing them. If you want Bacula to stop using a Volume and recycle
46 it before it is full, you will need to use one or more additional
49 \item Use Volume Once = yes
50 \item Volume Use Duration = ttt
51 \item Maximum Volume Jobs = nnn
52 \item Maximum Volume Bytes = mmm
55 the \ilink{Basic Volume Management}{_ChapterStart39} chapter
56 of this manual for more complete examples.
58 Automatic recycling of Volumes is performed by Bacula only when it wants a
59 new Volume and no appendable Volumes are available in the Pool. It will then
60 search the Pool for any Volumes with the {\bf Recycle} flag set and whose
61 Volume Status is {\bf Full}. At that point, the recycling occurs in two steps.
62 The first is that the Catalog for a Volume must be purged of all Jobs and
63 Files contained on that Volume, and the second step is the actual recycling of
64 the Volume. The Volume will be purged if the VolumeRetention period has
65 expired. When a Volume is marked as Purged, it means that no Catalog records
66 reference that Volume, and the Volume can be recycled. Until recycling
67 actually occurs, the Volume data remains intact. If no Volumes can be found
68 for recycling for any of the reasons stated above, Bacula will request
69 operator intervention (i.e. it will ask you to label a new volume).
71 A key point mentioned above, that can be a source of frustration, is that Bacula
72 will only recycle purged Volumes if there is no other appendable Volume
73 available, otherwise, it will always write to an appendable Volume before
74 recycling even if there are Volume marked as Purged. This preserves your data
75 as long as possible. So, if you wish to "force" Bacula to use a purged
76 Volume, you must first ensure that no other Volume in the Pool is marked {\bf
77 Append}. If necessary, you can manually set a volume to {\bf Full}. The reason
78 for this is that Bacula wants to preserve the data on your old tapes (even
79 though purged from the catalog) as long as absolutely possible before
80 overwriting it. There are also a number of directives such as
81 {\bf Volume Use Duration} that will automatically mark a volume as {\bf
82 Used} and thus no longer appendable.
85 \subsection*{Automatic Pruning}
86 \index[general]{Automatic Pruning}
87 \index[general]{Pruning!Automatic}
88 \addcontentsline{toc}{subsection}{Automatic Pruning}
90 As Bacula writes files to tape, it keeps a list of files, jobs, and volumes
91 in a database called the catalog. Among other things, the database helps
92 Bacula to decide which files to back up in an incremental or differential
93 backup, and helps you locate files on past backups when you want to restore
94 something. However, the catalog will grow larger and larger as time goes
95 on, and eventually it can become unacceptably large.
97 Bacula's process for removing entries from the catalog is called Pruning.
98 The default is Automatic Pruning, which means that once an entry reaches a
99 certain age (e.g. 30 days old) it is removed from the catalog. Once a job
100 has been pruned, you can still restore it from the backup tape, but one
101 additional step is required: scanning the volume with bscan. The
102 alternative to Automatic Pruning is Manual Pruning, in which you explicitly
103 tell Bacula to erase the catalog entries for a volume. You'd usually do
104 this when you want to reuse a Bacula volume, because there's no point in
105 keeping a list of files that USED TO BE on a tape. Or, if the catalog is
106 starting to get too big, you could prune the oldest jobs to save space.
107 Manual pruning is done with the \ilink{ prune command}{ManualPruning} in
108 the console. (thanks to Bryce Denney for the above explanation).
110 \subsection*{Pruning Directives}
111 \index[general]{Pruning Directives }
112 \index[general]{Directives!Pruning }
113 \addcontentsline{toc}{subsection}{Pruning Directives}
115 There are three pruning durations. All apply to catalog database records and
116 not to the actual data in a Volume. The pruning (or retention) durations are
117 for: Volumes (Media records), Jobs (Job records), and Files (File records).
118 The durations inter-depend a bit because if Bacula prunes a Volume, it
119 automatically removes all the Job records, and all the File records. Also when
120 a Job record is pruned, all the File records for that Job are also pruned
121 (deleted) from the catalog.
123 Having the File records in the database means that you can examine all the
124 files backed up for a particular Job. They take the most space in the catalog
125 (probably 90-95\% of the total). When the File records are pruned, the Job
126 records can remain, and you can still examine what Jobs ran, but not the
127 details of the Files backed up. In addition, without the File records, you
128 cannot use the Console restore command to restore the files.
130 When a Job record is pruned, the Volume (Media record) for that Job can still
131 remain in the database, and if you do a "list volumes", you will see the
132 volume information, but the Job records (and its File records) will no longer
135 In each case, pruning removes information about where older files are, but it
136 also prevents the catalog from growing to be too large. You choose the
137 retention periods in function of how many files you are backing up and the
138 time periods you want to keep those records online, and the size of the
139 database. You can always re-insert the records (with 98\% of the original data)
140 by using "bscan" to scan in a whole Volume or any part of the volume that
143 By setting {\bf AutoPrune} to {\bf yes} you will permit {\bf Bacula} to
144 automatically prune all Volumes in the Pool when a Job needs another Volume.
145 Volume pruning means removing records from the catalog. It does not shrink the
146 size of the Volume or affect the Volume data until the Volume gets
147 overwritten. When a Job requests another volume and there are no Volumes with
148 Volume Status {\bf Append} available, Bacula will begin volume pruning. This
149 means that all Jobs that are older than the {\bf VolumeRetention} period will
150 be pruned from every Volume that has Volume Status {\bf Full} or {\bf Used}
151 and has Recycle set to {\bf yes}. Pruning consists of deleting the
152 corresponding Job, File, and JobMedia records from the catalog database. No
153 change to the physical data on the Volume occurs during the pruning process.
154 When all files are pruned from a Volume (i.e. no records in the catalog), the
155 Volume will be marked as {\bf Purged} implying that no Jobs remain on the
156 volume. The Pool records that control the pruning are described below.
160 \item [AutoPrune = \lt{}yes|no\gt{}]
161 \index[console]{AutoPrune }
162 If AutoPrune is set to {\bf yes} (default), Bacula
163 will automatically apply the Volume retention period when running a Job and
164 it needs a new Volume but no appendable volumes are available. At that point,
165 Bacula will prune all Volumes that can be pruned (i.e. AutoPrune set) in an
166 attempt to find a usable volume. If during the autoprune, all files are
167 pruned from the Volume, it will be marked with VolStatus {\bf Purged}. The
168 default is {\bf yes}. Note, that although the File and Job records may be
169 pruned from the catalog, a Volume will be marked Purged (and hence
170 ready for recycling) if the Volume status is Append, Full, Used, or Error.
171 If the Volume has another status, such as Archive, Read-Only, Disabled,
172 Busy, or Cleaning, the Volume status will not be changed to Purged.
174 \item [Volume Retention = \lt{}time-period-specification\gt{}]
175 \index[console]{Volume Retention}
176 The Volume Retention record defines the length of time that Bacula will
177 guarantee that the Volume is not reused counting from the time the last
178 job stored on the Volume terminated. A key point is that this time
179 period is not even considered as long at the Volume remains appendable.
180 The Volume Retention period count down begins only when the Append
181 status has been changed to some othe status (Full, Used, Purged, ...).
183 When this time period expires, and if {\bf AutoPrune} is set to {\bf
184 yes}, and a new Volume is needed, but no appendable Volume is available,
185 Bacula will prune (remove) Job records that are older than the specified
186 Volume Retention period.
188 The Volume Retention period takes precedence over any Job Retention
189 period you have specified in the Client resource. It should also be
190 noted, that the Volume Retention period is obtained by reading the
191 Catalog Database Media record rather than the Pool resource record.
192 This means that if you change the VolumeRetention in the Pool resource
193 record, you must ensure that the corresponding change is made in the
194 catalog by using the {\bf update pool} command. Doing so will insure
195 that any new Volumes will be created with the changed Volume Retention
196 period. Any existing Volumes will have their own copy of the Volume
197 Retention period that can only be changed on a Volume by Volume basis
198 using the {\bf update volume} command.
200 When all file catalog entries are removed from the volume, its VolStatus is
201 set to {\bf Purged}. The files remain physically on the Volume until the
202 volume is overwritten.
204 Retention periods are specified in seconds, minutes, hours, days, weeks,
205 months, quarters, or years on the record. See the
206 \ilink{Configuration chapter}{Time} of this manual for
207 additional details of time specification.
209 The default is 1 year.
211 \item [Recycle = \lt{}yes|no\gt{}]
213 This statement tells Bacula whether or not the particular Volume can be
214 recycled (i.e. rewritten). If Recycle is set to {\bf no} (the
215 default), then even if Bacula prunes all the Jobs on the volume and it
216 is marked {\bf Purged}, it will not consider the tape for recycling. If
217 Recycle is set to {\bf yes} and all Jobs have been pruned, the volume
218 status will be set to {\bf Purged} and the volume may then be reused
219 when another volume is needed. If the volume is reused, it is relabeled
220 with the same Volume Name, however all previous data will be lost.
223 It is also possible to "force" pruning of all Volumes in the Pool
224 associated with a Job by adding {\bf Prune Files = yes} to the Job resource.
227 \subsection*{Recycling Algorithm}
228 \index[general]{Algorithm!Recycling }
229 \index[general]{Recycling Algorithm }
230 \addcontentsline{toc}{subsection}{Recycling Algorithm}
232 After all Volumes of a Pool have been pruned (as mentioned above, this happens
233 when a Job needs a new Volume and no appendable Volumes are available), Bacula
234 will look for the oldest Volume that is Purged (all Jobs and Files expired),
235 and if the {\bf Recycle} flag is on (Recycle=yes) for that Volume, Bacula will
236 relabel it and write new data on it.
238 As mentioned above, there are two key points for getting a Volume
239 to be recycled. First, the Volume must no longer be marked Append (there
240 are a number of directives to automatically make this change), and second
241 since the last write on the Volume, one or more of the Retention periods
242 must have expired so that there are no more catalog backup job records
243 that reference that Volume. Once both those conditions are satisfied,
244 the volume can be marked Purged and hence recycled.
246 The full algorithm that Bacula uses when it needs a new Volume is:
247 \index[general]{New Volume Algorithm}
248 \index[general]{Algorithm!New Volume}
251 \item If the request is for an Autochanger device, look only
252 for Volumes in the Autochanger (i.e. with InChanger set and that have
253 the correct Storage device).
254 \item Search the Pool for a Volume with VolStatus=Append (if there is more
255 than one, the Volume with the oldest date last written is chosen. If
256 two have the same date then the one with the lowest MediaId is chosen).
257 \item Search the Pool for a Volume with VolStatus=Recycle and the InChanger
258 flag is set true (if there is more than one, the Volume with the oldest
259 date last written is chosen. If two have the same date then the one
260 with the lowest MediaId is chosen).
261 \item Try recycling any purged Volumes.
262 \item Prune volumes applying Volume retention period (Volumes with VolStatus
263 Full, Used, or Append are pruned).
264 \item Search the Pool for a Volume with VolStatus=Purged
265 \item If a Pool named "Scratch" exists, search for a Volume and if found
266 move it to the current Pool for the Job and use it. Note, when
267 the Scratch Volume is moved into the current Pool, the basic
268 Pool defaults are applied as if it is a newly labeled Volume
269 (equivalent to an {\bf update volume from pool} command).
270 \item If we were looking for Volumes in the Autochanger, go back to
271 step 2 above, but this time, look for any Volume whether or not
272 it is in the Autochanger.
273 \item Attempt to create a new Volume if automatic labeling enabled
274 If Python is enabled, a Python NewVolume event is generated before
275 the Label Format directve is used.
276 \item Prune the oldest Volume if RecycleOldestVolume=yes (the Volume with the
277 oldest LastWritten date and VolStatus equal to Full, Recycle, Purged, Used,
278 or Append is chosen). This record ensures that all retention periods are
280 \item Purge the oldest Volume if PurgeOldestVolume=yes (the Volume with the
281 oldest LastWritten date and VolStatus equal to Full, Recycle, Purged, Used,
282 or Append is chosen). We strongly recommend against the use of {\bf
283 PurgeOldestVolume} as it can quite easily lead to loss of current backup
285 \item Give up and ask operator.
288 The above occurs when Bacula has finished writing a Volume or when no Volume
289 is present in the drive.
291 On the other hand, if you have inserted a different Volume after the last job,
292 and Bacula recognizes the Volume as valid, it will request authorization from
293 the Director to use this Volume. In this case, if you have set {\bf Recycle
294 Current Volume = yes} and the Volume is marked as Used or Full, Bacula will
295 prune the volume and if all jobs were removed during the pruning (respecting
296 the retention periods), the Volume will be recycled and used.
297 The recycling algorithm in this case is:
300 \item If the VolStatus is {\bf Append} or {\bf Recycle}
301 is set, the volume will be used.
302 \item If {\bf Recycle Current Volume} is set and the volume is marked {\bf
303 Full} or {\bf Used}, Bacula will prune the volume (applying the retention
304 period). If all Jobs are pruned from the volume, it will be recycled.
307 This permits users to manually change the Volume every day and load tapes in
308 an order different from what is in the catalog, and if the volume does not
309 contain a current copy of your backup data, it will be used.
311 \subsection*{Recycle Status}
312 \index[general]{Status!Recycle }
313 \index[general]{Recycle Status }
314 \addcontentsline{toc}{subsection}{Recycle Status}
316 Each Volume inherits the Recycle status (yes or no) from the Pool resource
317 record when the Media record is created (normally when the Volume is labeled).
318 This Recycle status is stored in the Media record of the Catalog. Using
319 the Console program, you may subsequently change the Recycle status for each
320 Volume. For example in the following output from {\bf list volumes}:
324 +----------+-------+--------+---------+------------+--------+-----+
325 | VolumeNa | Media | VolSta | VolByte | LastWritte | VolRet | Rec |
326 +----------+-------+--------+---------+------------+--------+-----+
327 | File0001 | File | Full | 4190055 | 2002-05-25 | 14400 | 1 |
328 | File0002 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
329 | File0003 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
330 | File0004 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
331 | File0005 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
332 | File0006 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
333 | File0007 | File | Purged | 1896466 | 2002-05-26 | 14400 | 1 |
334 +----------+-------+--------+---------+------------+--------+-----+
338 all the volumes are marked as recyclable, and the last Volume, {\bf File0007}
339 has been purged, so it may be immediately recycled. The other volumes are all
340 marked recyclable and when their Volume Retention period (14400 seconds or 4
341 hours) expires, they will be eligible for pruning, and possibly recycling.
342 Even though Volume {\bf File0007} has been purged, all the data on the Volume
343 is still recoverable. A purged Volume simply means that there are no entries
344 in the Catalog. Even if the Volume Status is changed to {\bf Recycle}, the
345 data on the Volume will be recoverable. The data is lost only when the Volume
346 is re-labeled and re-written.
348 To modify Volume {\bf File0001} so that it cannot be recycled, you use the
349 {\bf update volume pool=File} command in the console program, or simply {\bf
350 update} and Bacula will prompt you for the information.
354 +----------+------+-------+---------+-------------+-------+-----+
355 | VolumeNa | Media| VolSta| VolByte | LastWritten | VolRet| Rec |
356 +----------+------+-------+---------+-------------+-------+-----+
357 | File0001 | File | Full | 4190055 | 2002-05-25 | 14400 | 0 |
358 | File0002 | File | Full | 1897236 | 2002-05-26 | 14400 | 1 |
359 | File0003 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
360 | File0004 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
361 | File0005 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
362 | File0006 | File | Full | 1896460 | 2002-05-26 | 14400 | 1 |
363 | File0007 | File | Purged| 1896466 | 2002-05-26 | 14400 | 1 |
364 +----------+------+-------+---------+-------------+-------+-----+
368 In this case, {\bf File0001} will never be automatically recycled. The same
369 effect can be achieved by setting the Volume Status to Read-Only.
371 As you have noted, the Volume Status (VolStatus) colume in the
372 catalog database contains the current status of the Volume, which
373 is normally maintained automatically by Bacula. To give you an
374 idea of some of the values it can take during the life cycle of
375 a Volume, here is a picture created by Arno Lehmann:
379 A typical volume life cycle is like this:
381 because job count or size limit exceeded
382 Append ----------------------------------------> Used
384 | First Job writes to Retention time passed |
385 | the volume and recycling takes |
388 Recycled <-------------------------------------- Purged
389 Volume is selected for reuse
395 \subsection*{Making Bacula Use a Single Tape}
397 \index[general]{Tape!Making Bacula Use a Single}
398 \index[general]{Making Bacula Use a Single Tape}
399 \addcontentsline{toc}{subsection}{Making Bacula Use a Single Tape}
401 Most people will want Bacula to fill a tape and when it is full, a new tape
402 will be mounted, and so on. However, as an extreme example, it is possible for
403 Bacula to write on a single tape, and every night to rewrite it. To get this
404 to work, you must do two things: first, set the VolumeRetention to less than
405 your save period (one day), and the second item is to make Bacula mark the
406 tape as full after using it once. This is done using {\bf UseVolumeOnce =
407 yes}. If this latter record is not used and the tape is not full after the
408 first time it is written, Bacula will simply append to the tape and eventually
409 request another volume. Using the tape only once, forces the tape to be marked
410 {\bf Full} after each use, and the next time {\bf Bacula} runs, it will
413 An example Pool resource that does this is:
419 Use Volume Once = yes
422 VolumeRetention = 12h # expire after 12 hours
428 \subsection*{A Daily, Weekly, Monthly Tape Usage Example}
430 \index[general]{Daily, Weekly, Monthly Tape Usage Example }
431 \index[general]{Example!Daily Weekly Monthly Tape Usage }
432 \addcontentsline{toc}{subsection}{Daily, Weekly, Monthly Tape Usage Example}
434 This example is meant to show you how one could define a fixed set of volumes
435 that Bacula will rotate through on a regular schedule. There are an infinite
436 number of such schemes, all of which have various advantages and
439 We start with the following assumptions:
442 \item A single tape has more than enough capacity to do a full save.
443 \item There are 10 tapes that are used on a daily basis for incremental
444 backups. They are prelabeled Daily1 ... Daily10.
445 \item There are 4 tapes that are used on a weekly basis for full backups.
446 They are labeled Week1 ... Week4.
447 \item There are 12 tapes that are used on a monthly basis for full backups.
448 They are numbered Month1 ... Month12
449 \item A full backup is done every Saturday evening (tape inserted Friday
450 evening before leaving work).
451 \item No backups are done over the weekend (this is easy to change).
452 \item The first Friday of each month, a Monthly tape is used for the Full
454 \item Incremental backups are done Monday - Friday (actually Tue-Fri
458 We start the system by doing a Full save to one of the weekly volumes or one
459 of the monthly volumes. The next morning, we remove the tape and insert a
460 Daily tape. Friday evening, we remove the Daily tape and insert the next tape
461 in the Weekly series. Monday, we remove the Weekly tape and re-insert the
462 Daily tape. On the first Friday of the next month, we insert the next Monthly
463 tape in the series rather than a Weekly tape, then continue. When a Daily tape
464 finally fills up, {\bf Bacula} will request the next one in the series, and
465 the next day when you notice the email message, you will mount it and {\bf
466 Bacula} will finish the unfinished incremental backup.
468 What does this give? Well, at any point, you will have the last complete
469 Full save plus several Incremental saves. For any given file you want to
470 recover (or your whole system), you will have a copy of that file every day
471 for at least the last 14 days. For older versions, you will have at least 3
472 and probably 4 Friday full saves of that file, and going back further, you
473 will have a copy of that file made on the beginning of the month for at least
476 So you have copies of any file (or your whole system) for at least a year, but
477 as you go back in time, the time between copies increases from daily to weekly
480 What would the Bacula configuration look like to implement such a scheme?
486 Run = Level=Full Pool=Monthly 1st sat at 03:05
487 Run = Level=Full Pool=Weekly 2nd-5th sat at 03:05
488 Run = Level=Incremental Pool=Daily tue-fri at 03:05
494 Client = LocalMachine
499 Schedule = "NightlySave"
501 # Definition of file storage device
506 Password = XXXXXXXXXXXXX
512 Include = signature=MD5 {
521 VolumeRetention = 10d # recycle in 10 days
527 Use Volume Once = yes
530 VolumeRetention = 30d # recycle in 30 days (default)
535 Use Volume Once = yes
538 VolumeRetention = 365d # recycle in 1 year
544 \subsection*{ Automatic Pruning and Recycling Example}
545 \label{PruningExample}
546 \index[general]{Automatic Pruning and Recycling Example }
547 \index[general]{Example!Automatic Pruning and Recycling }
548 \addcontentsline{toc}{subsection}{Automatic Pruning and Recycling Example}
550 Perhaps the best way to understand the various resource records that come into
551 play during automatic pruning and recycling is to run a Job that goes through
552 the whole cycle. If you add the following resources to your Director's
558 Name = "30 minute cycle"
559 Run = Level=Full Pool=File Messages=Standard Storage=File
561 Run = Level=Full Pool=File Messages=Standard Storage=File
573 Schedule = "30 minute cycle"
575 # Definition of file storage device
578 Address = XXXXXXXXXXX
580 Password = XXXXXXXXXXXXX
586 Include = signature=MD5 {
593 Use Volume Once = yes
604 Where you will need to replace the {\bf ffffffffff}'s by the appropriate files
605 to be saved for your configuration. For the FileSet Include, choose a
606 directory that has one or two megabytes maximum since there will probably be
607 approximately 8 copies of the directory that {\bf Bacula} will cycle through.
609 In addition, you will need to add the following to your Storage daemon's
617 Archive Device = /tmp
620 AutomaticMount = yes;
627 With the above resources, Bacula will start a Job every half hour that saves a
628 copy of the directory you chose to /tmp/File0001 ... /tmp/File0012. After 4
629 hours, Bacula will start recycling the backup Volumes (/tmp/File0001 ...). You
630 should see this happening in the output produced. Bacula will automatically
631 create the Volumes (Files) the first time it uses them.
633 To turn it off, either delete all the resources you've added, or simply
634 comment out the {\bf Schedule} record in the {\bf Job} resource.
636 \subsection*{Manually Recycling Volumes}
637 \label{manualrecycling}
638 \index[general]{Volumes!Manually Recycling }
639 \index[general]{Manually Recycling Volumes }
640 \addcontentsline{toc}{subsection}{Manually Recycling Volumes}
642 Although automatic recycling of Volumes is implemented in version 1.20 and
644 \ilink{Automatic Recycling of Volumes}{_ChapterStart22} chapter of
645 this manual), you may want to manually force reuse (recycling) of a Volume.
647 Assuming that you want to keep the Volume name, but you simply want to write
648 new data on the tape, the steps to take are:
651 \item Use the {\bf update volume} command in the Console to ensure that the
652 {\bf Recycle} field is set to {\bf 1}
653 \item Use the {\bf purge jobs volume} command in the Console to mark the
654 Volume as {\bf Purged}. Check by using {\bf list volumes}.
657 Once the Volume is marked Purged, it will be recycled the next time a Volume
660 If you wish to reuse the tape by giving it a new name, follow the following
664 \item Use the {\bf purge jobs volume} command in the Console to mark the
665 Volume as {\bf Purged}. Check by using {\bf list volumes}.
666 \item In Bacula version 1.30 or greater, use the Console {\bf relabel}
667 command to relabel the Volume.
670 Please note that the relabel command applies only to tape Volumes.
672 For Bacula versions prior to 1.30 or to manually relabel the Volume, use the
676 \item Use the {\bf delete volume} command in the Console to delete the Volume
678 \item If a different tape is mounted, use the {\bf unmount} command,
679 remove the tape, and insert the tape to be renamed.
680 \item Write an EOF mark in the tape using the following commands:
684 mt -f /dev/nst0 rewind
689 where you replace {\bf /dev/nst0} with the appropriate device name on your
691 \item Use the {\bf label} command to write a new label to the tape and to
692 enter it in the catalog.
695 Please be aware that the {\bf delete} command can be dangerous. Once it is
696 done, to recover the File records, you must either restore your database as it
697 was before the {\bf delete} command, or use the {\bf bscan} utility program to
698 scan the tape and recreate the database entries.