On 03/30/2015 03:50 PM, Chris Dos wrote: > I've just set up Bareos recently, so I'm pretty green regarding this software > though I've been doing unix backups since '91 using one form of software and > media during that time. > > I'm running Bareos using vchanger and autofs to backup to seven Seagate 8TB > shingled drives. I'm currently backing up 20TB of data on the primary server > along with a couple of windows computers. > > vchanger is configured to use two magazines with two virtual drives in each > magazine. I'm currently only plugging in one physical hard drive at a time > in order to try and diagose my problem. > > Error in question: > 30-Mar 14:48 windwalker-fd JobId 304: Fatal error: dir_cmd.c:2169 Bad > response to Append Data command. Wanted 3000 OK data > , got 3903 Error append data > 30-Mar 14:48 windwalker-sd JobId 304: Fatal error: 3992 Bad autochanger "load > slot 58, drive 0": ERR=Child exited with code 1. > Results=invalid slot number 58 > > I'm running Debian on Nightlies. I upgraded to Nightlies after reading about > the "Missing 64K in zip-file" thread and from what I gathered, this affected > everyone that was using vchanger. Maybe someone could clarify if that was > necessary or not. > > Chris
Seems that I have stumbled upon the issue myself. Another bit of the backup job log: 30-Mar 14:48 windwalker-dir JobId 304: Using Device "vchanger_3tb_drive_0" to write. The backup job was set on using vchanger_3tb instead of vchanger_8tb. I had no mounted drives listed under vchanger_3tb.conf file. But if you ran "update slots storage=vchanger_3tb" it found the volumes listed under the vchanger_3tb. Is it not possible to have multiple vchangers listed? I was planning over time to have a mixture of drives. And since I found out that you cannot over subscribe the space on a drive or vchanger will no longer work on that magazine(drive). So I created two different vchanger configurations and made the appropriate configuration changes in bareos-sd.conf. Originally I had each job use "Storage = vchanger_3tb,vchanger_8tb". But somehow a 8TB volume showed up under the 3TB vchanger. I was planning on making use of multiple vchangers as larger drives came out. Supposed to see 20TB drives in a few years. Have I ran into some kind of bug with using vchangers? Googling, it seems that Bacula 7.0.5 is also having this problem: http://goo.gl/6iMDRj A reply in that thread: Also, you *must* use a unique (different) MediaType = xxx for each autochanger or you will ultimately have Bacula asking for Volumes in an autochanger that are not there or are not to be loaded Is the Mediatype name arbitrary? According to the docs I just read, that would be a yes. Time to update my configuration and have another go. Chris -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
