On Thu, Sep 22, 2011 at 2:15 PM, tscollins
<bacula-forum AT backupcentral DOT com> wrote:
> Here is what I have done on the server
> 1. Stop the service - /sbin/bacula stop
> 2. Delete the database - /etc/bacula/drop_bacula_database
> 3. Remove any working files - rm -rf /var/bacula/working/*
> 4. Since I am using a NAS device to do my backups I then do - rm -rf 
> /mnt/nas-backup/*
> 5. Now redo all database stuff - /etc/bacula/create_bacula_database and 
> /etc/bacula/make_bacula_tables
> 6. Restart the service - /sbin/bacula start
> On the clients (my clients are Apple Macintosh systems running 10.6.8)
> 1. Stop the client/file daemon - sudo launchctl unload -w 
> /Library/LaunchDaemons/org.bacula.bacula-fd.plist
> 2. Remove any working files (check the bacula-fd.conf file for 
> WorkingDirectory location) - sudo rm -rf 
> /private/var/bacula/working/bacula-fd.9102.state
> 3. Restart the computer
> 4. Restart the service - sudo launchctl load -w 
> /Library/LaunchDaemons/org.bacula.bacula-fd.plist and sudo launchctl start 
> org.bacula.bacula-fd
>

Looks fine to me.


John

------------------------------------------------------------------------------
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-d2dcopy1
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users