Hello.
I am sorry, but this is actually not at all, what I want.
I took some time to think about how to explain all this better...
So I have two drives: and
I am using a shell script to create a new Volume on every
month. This script is executed by a bacula job.
has run out of space now,
Hello.
I see that I did not use "Purge Migration Job = yes", That should
explain, while the old volumes still exist fully.
Sorry for the very rough question.
I will try to make the scenario a bit more understandable:
On the hard drive we have on site, a new volume is created every month,
Hello, again.
As a quick additional question:
I used to create one volume per month, starting with a full backup. Is
there any way how I can migrate the data to create the exact same
structure?
E.g. 5 old volumes = 5 new volumes
Regards,
Florian S.
Am 19.05.2016 um 14:20 schrieb Florian
Hello.
After a lot of preparing the migration of the first set of data with
migration jobs went smoothly.
The size matches and when doing a restore the new volume is addressed.
I noticed that the old volumes still exist though.
Can I remove them now?
If so: Is the delete option okay (via bat)
Hello Ana and Kern
I know that migration Jobs can be used to move volumes to another Storage,
but I guess is a lost of time using it if I will just replace the old disk
for a new one with more capacity.
In my previous example I said I have 2 storages/disks, so I have volumes
in both disks and I
Hello Wanderei,
Well, you simply: "mv /old/path/ /new/path".
which will essentially do a cp followed by an rm if the old and
new paths are on different devices, otherwise it is a sort of
directory entry change.
If you start changing your
Hello Wanderlei and Patti,
I think that the migration jobs were designed to accomplish this also. You
can configure a migration job to migrate all your volumes from a pool
(associated to your old storage device) to another one (associated to your
new storage device).
Also, if dealing with disk
I concur with Wanderlei. Another aspect of moving volumes between storage
devices is the need to change the mediatype. Bacula bconsole does not provide
a command to change the mediatype.
Patti
From: Wanderlei Huttel
>
Date:
Hello Kern
I understand your concerns about make changes by hand in bacula database,
but it wouldn't be interesting create an option in update to move volumes
to another Storage?
An exemple: you can have 2 disks with 1TB (everyone with one storage) and
you will change for a new one of 4TB. In
Hello,
I strongly encourage users to use Bacula bconsole commands to
accomplish *all* modifications of the catalog database. Making
changes by hand using SQL will quite often lead to inconsistencies
in the catalog that can come back to haunt you. In
Hello and sorry for the late response.
I just wanted to thank you for all the information.
Definitely helped me decide on how to approach the issue.
Regards,
Florian S.
Am 28.04.2016 um 13:04 schrieb Wanderlei Huttel:
Hello Florian
2016-04-28 5:47 GMT-03:00 Florian Splett
Hello Florian
2016-04-28 5:47 GMT-03:00 Florian Splett :
> Hello, bacula community.
>
> The harddrive my bacula system is using to store its volumes is reaching
> its maximum capacity, so I had the following plan for my network:
>
> I want to manually move the old volumes
Hello, bacula community.
The harddrive my bacula system is using to store its volumes is reaching
its maximum capacity, so I had the following plan for my network:
I want to manually move the old volumes onto an external harddrive and
keep that somewhere else.
Now what i want to ask is: Does
13 matches
Mail list logo