virtual_drives = 1
slots_per_magazine = 1
magazine_bays = 1
automount_dir = /mnt/vchanger
magazine = UUID:ccefd56c-1537-48bf-b0e4-03dd58a7c4f9
magazine = UUID:e72ccd02-2c00-4d45-a43f-f53c37bb35c4
magazine = UUID:3c3a8772-c887-4023-8b24-95a1d0c4dc8a
#eof
Anyone who can help ?
Thanks,
Koenraad
Hi,
I have been messing around with vchanger. Now I would like to start from
zero. How do I do this ? Vchanger seems to remember how many removable
drive it already initialized. Where does it store this information ?
Or do I have to make a new config-file ?
Regards,
Koenraad Lelong
/
for every disk/partition used by vchanger
Michael
Hi Michael,
That seems to be working. I'm going to try more devices.
Many thanks,
Koenraad Lelong
--
Benefiting from Server Virtualization: Beyond Initial Workload
Op 21-04-11 16:38, Josh Fisher schreef:
On 4/21/2011 3:16 AM, Koenraad Lelong wrote:
Hi,
I have been messing around with vchanger. Now I would like to start from
zero. How do I do this ? Vchanger seems to remember how many removable
drive it already initialized. Where does it store
with -f -v -d 99, but I don't see anything meaningfull to me.
Thanks,
Koenraad Lelong.
bconsole says version 5.0.3.
This is my configuration :
vchanger's c2.conf :
### /etc/bacula/c1.conf
# work_dir=/var/spool/bacula
changer_name = c2
virtual_drives = 1
slots_per_magazine = 3
magazine_bays = 1
Op 25-04-11 17:43, Josh Fisher schreef:
On 4/22/2011 7:37 AM, Koenraad Lelong wrote:
Hi,
...
It looks like you either did not create the volumes using vchanger's
INITMAG command, or else you created them as root or some other user and
it is a permissions problem. The volume files must
Op 26-04-11 16:51, Josh Fisher schreef:
On 4/26/2011 5:10 AM, Koenraad Lelong wrote:
...
Hi,
I started from scratch again.
The partition itself must also have the correct owner and permissions.
It should look like:
# ls -la 49299ccc-6489-43f8-9536-d63dd3de9663
drwxrwx--- 3 bacula
Op 03-05-11 16:05, Josh Fisher schreef:
On 5/3/2011 5:55 AM, Koenraad Lelong wrote:
...
So, bacula:bacula cannot write, but bacula:disk can, yet all accessed
directories appear to be owned by bacula:bacula? What group does the
bacula-sd daemon run as? On Fedora, it is typical for bacula-dir
