I decided on bextract. I've found the file I need in the volume, but still
having problems...
#bextract -d99 -i databaselist.rest -V DatabaseF-0027 /data/bacula /data/tmp
bextract: stored_conf.c:698-0 Inserting director res: fatboy-dir
bextract: butil.c:282 Using device: "/data/bacula" for reading.
bextract: acquire.c:109-0 MediaType dcr= dev=File
bextract: acquire.c:228-0 opened dev "pool" (/data/bacula) OK
bextract: acquire.c:231-0 calling read-vol-label
Volume Label:
Id : Bacula 1.0 immortal
VerNo : 11
VolName : DatabaseF-0027
PrevVolName :
VolFile : 0
LabelType : VOL_LABEL
LabelSize : 186
PoolName : DatabaseF
MediaType : File
PoolType : Backup
HostName : foobar.mtadistributors.com
Date label written: 06-Sep-2010 02:23
bextract: acquire.c:235-0 Got correct volume.
24-Jun 11:16 bextract JobId 0: Ready to read from volume "DatabaseF-0027" on
device "pool" (/data/bacula).
bextract: attr.c:281-0 -rw-rw---- 1 pgsql pgsql 386091824 2011-06-09
08:51:47 /data/tmp/mnt/database/usr/home/pgsql/dumps/mta.dump.sql.gz-4
bextract JobId 0: -rw-rw---- 1 pgsql pgsql 386091824 2011-06-09
08:51:47 /data/tmp/mnt/database/usr/home/pgsql/dumps/mta.dump.sql.gz-4
I have one processor going @ 100%, a file touched in the restore location but O
bytes being written into the file.
Thoughts?
Troy
On 24,Jun 2011, at 2:28 AM, Graham Keeling wrote:
> On Thu, Jun 23, 2011 at 02:01:56PM -0700, Steve Ellis wrote:
>> On 6/23/2011 1:31 PM, Troy Kocher wrote:
>>> Listers,
>>>
>>> I'm trying to restore data from medicaid 27, but it appears there are no
>>> files. There is a file corresponding with this still on the disk, so I
>>> think it's just been purged from the database.
>>>
>>> Could someone help me thru the restore process when the files are no longer
>>> in the database.
>>>
>>> Thanks!
>>>
>>> Troy
>>>
>> There are really only 3 options here that I can think of:
>> 1) restore the entire job (probably to an temporary location), then
>> prune the bits you don't want.
>> 2) use bscan of the volume to recreate the file list in the db
>> (note that I have only used this when the job itself had been expired
>> from the DB)
>> 3) restore a dump of the catalog that contains the file entries
>> that you wanted that have been expired
>
> 4) Use bextract.
>
>> I'm pretty sure I've done both #1 and #2, #3 I'd be much more reluctant
>> to just try, as I would worry about clobbering more recent catalog data,
>> unless you used a separate catalog db for the restoration. Unless the
>> job is really huge, I'd probably do #1, because bscan is (slightly)
>> dodgy, especially for backups that span volumes (IMHO, note that it is
>> _much_ better than not having bscan at all). Sorry I can't provide more
>> detail, hopefully someone else will be able to help more.
>>
>> -se
>>
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense..
http://p.sf.net/sfu/splunk-d2d-c1 _______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
