Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-25 Thread Miki
Hi Mariusz !

Welcome to the underrated migrating club ! :) I also tried to migrate 
between SDs to no avail. I supposed that migration for us bacula users 
using FILE storage systems would be implemented as well, but alas, it is 
not.

Why did you want to migrate the files ? Something connected to expanding 
a filesystem ? Because this is a feature of FILE based volumes, that 
they are not easily extendable (as opposed to tapes) and migration could 
be a good way to transfer data between old (let's say a 1TB LVM system) 
and new (4TB netapp) storage systems.

Finally, I moved the volumes themselves to the new storage server (10X 
400GB SATA disks), and "migrated" the old server's TCP/IP address to the 
new server. bacula picked up from there and it eventually worked quite 
well, except for the Intel 965 motherboard that is not well supported by 
linux.

Cheers,

Michael

Mariusz Czulada wrote:
> Hi,
> 
> Dnia 19-04-2007 o godz. 22:42 Arno Lehmann napisał(a):
>> Hi,
>>
>> On 4/19/2007 4:48 PM, Mariusz Czulada wrote:
>>> Hello,
>>>
>>> I have yet another problem to solve. I didn't find similar case in
>>> documentation.
>>>
>>> I have two separate systems in two locations (let's say "site1" and
>>> "site2"). In "site1" I have local DDS5 drive and TS3310 library. In
>>> "site2" server is only equiped with DDS5. Also, "Site1" is accesible
>>> from "Site2" via WAN. So, "Site1" configuration looks like this:
>>>
>>> [...]
>>>
>>> We could not buy a dedicated library for "Site2", OTOH TS3310 in "site1"
>>> is big enough to hold backups from both sites. So, I thought about
>>> migrating jobs stored in "localfiles-2" to a library via WAN connection.
>>> IHMO I should add such items:
>>>
>>> Site2:
>>> - Director2:
>>>   * storage: ts3310-1 (@StorageDaemon1)
>>>   * pool: tapelibrary-2
>>> +storage: ts3310-1
>>>
>>> So I could migrate locally stored jobs from "fileststem-2" to
>>> "tapelibrary-2" which resides on remote ("Site1") library.
>>>
>>> !!
>>>
>>> My question is: are there any weak points in this idea?
>> Yes...
>>
>>> I.e. is it
>>> possible to migrate between different storage daemons?
>> No, that's not possible. Perhaps it will be implemented some day - I
>> talked with Kern about this - but I'm quite sure nobody started
>> implementing this.
>>
> 
> Hmm... This highly complicates my idea :/ Have to 'redesign' the whole 
> concepts...
> 
> BTW. If it was mentioned previously - is it possible to add "multi SD 
> migration" to the TODO list (question to developers, I think)? I hope 
> I'm not the only one to use this feature. IMHO it could be very 
> important in backing up multiple/distributed systems, where it is much 
> easier and cheaper to have one big library for long term storage then 
> equip every system/site with dedicated, smaller libs.
> 
>>> Can [slow] WAN
>>> connection (some 2 Mb/s I think) affect backup reliability?
>> Not reliablility itself, but the duration of the jobs alone makes them
>> more easily affected by network problems.
>>
> 
> I keep it in mind, but was thinking rather about possibiliy of problems, 
> when "feeding SD with data" is [probably] slower then a library/drive 
> speed.
> 
>>> !!
>>>
>>> Any comments and suggestions are gratly appreciated.
>>>
>>> Regards,
>>>
>>> Mariusz Czulada
>> Arno
>>
> 
> Mariusz
> 
> 
> Książka Benedykta XVI "Jezus z Nazaretu" 
> napisana w I rocznicę śmierci Jana Pawła II
> już w księgarniach! Zobacz więcej!
> http://klik.wp.pl/?adr=http%3A%2F%2Fksiazki.wp.pl%2Fkatalog%2Fksiazki%2Fksiazka.html%3Fkw%3D35343&sid=1109
> 
> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/


-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-20 Thread Arno Lehmann
Hi,

On 4/20/2007 7:12 PM, Jeff Dickens wrote:
> Mariusz Czulada wrote:
>> Hello,
>>
>>   
> Rats.  I assumed it would work between two SDs.

The feature is kind of in the pipeline, it seems...

>  Major bummer.  In fact 
> I spent the last couple hours setting just such a system up, and was 
> surprised when if failed with the tape SD looking for the disk SD's 
> storage device. 
> 
> I then re-read the docs on migration, and it doesn't say anything about 
> it.  I'm sure anyone who was familiar with the code would not be 
> surprised by this limitation, but it probably should be made explicit in 
> the docs.

Possibly... Could you write up a paragraph to that effect?

> 
> The idea was to avoid slowing down my server waiting for a tape drive.  
> I guess I'll just have to depend on spooling and/or buy a big cheap hard 
> drive for my (Windows) SD system. 


Try the big disk... once migration between different SDs works you can 
use that for other stuff :-)

Arno

> 
> 
> -
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> ___
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-- 
IT-Service Lehmann[EMAIL PROTECTED]
Arno Lehmann  http://www.its-lehmann.de

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-20 Thread Jeff Dickens
Mariusz Czulada wrote:
> Hello,
>
>   
Rats.  I assumed it would work between two SDs.  Major bummer.  In fact 
I spent the last couple hours setting just such a system up, and was 
surprised when if failed with the tape SD looking for the disk SD's 
storage device. 

I then re-read the docs on migration, and it doesn't say anything about 
it.  I'm sure anyone who was familiar with the code would not be 
surprised by this limitation, but it probably should be made explicit in 
the docs.

The idea was to avoid slowing down my server waiting for a tape drive.  
I guess I'll just have to depend on spooling and/or buy a big cheap hard 
drive for my (Windows) SD system. 



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-20 Thread Alan Brown
On Thu, 19 Apr 2007, Mariusz Czulada wrote:

> BTW. If it was mentioned previously - is it possible to add "multi SD
> migration" to the TODO list (question to developers, I think)?

Add it to the wishlist and wait.

> I hope I'm not the only one to use this feature. IMHO it could be very 
> important in backing up multiple/distributed systems, where it is much 
> easier and cheaper to have one big library for long term storage then 
> equip every system/site with dedicated, smaller libs.

The problem is that those who have time to work on features don't have 
enterprise-scale systems and so don't work on enterprise-scale related 
features. Those who do have such systems don't have the time (and/or 
programming ability) to try and write such code.

There is nothing stopping you from working on (or paying for someone to 
work on) the necessary code and then contributing it back into the feature 
pool.

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-19 Thread Arno Lehmann
Hi,

On 4/19/2007 11:30 PM, Mariusz Czulada wrote:
...
>>> I.e. is it
>>> possible to migrate between different storage daemons?
>> No, that's not possible. Perhaps it will be implemented some day - I
>> talked with Kern about this - but I'm quite sure nobody started
>> implementing this.
>>
> 
> Hmm... This highly complicates my idea :/ Have to 'redesign' the whole 
> concepts...

Looks like it.

> BTW. If it was mentioned previously - is it possible to add "multi SD 
> migration" to the TODO list (question to developers, I think)?

I'm not sure if this is already a feature request... take a look at the 
projects file, and if you don't see this particular project, fee free to 
prepare a feature request.


> I hope 
> I'm not the only one to use this feature.

Probably not.

> IMHO it could be very 
> important in backing up multiple/distributed systems, where it is much 
> easier and cheaper to have one big library for long term storage then 
> equip every system/site with dedicated, smaller libs.

Right.

> 
>>> Can [slow] WAN
>>> connection (some 2 Mb/s I think) affect backup reliability?
>> Not reliablility itself, but the duration of the jobs alone makes them
>> more easily affected by network problems.
>>
> 
> I keep it in mind, but was thinking rather about possibiliy of problems, 
> when "feeding SD with data" is [probably] slower then a library/drive 
> speed.

You should use spooling - as always with a decent tape drive IMO.

Arno

-- 
IT-Service Lehmann[EMAIL PROTECTED]
Arno Lehmann  http://www.its-lehmann.de

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-19 Thread Mariusz Czulada
Hi,

Dnia 19-04-2007 o godz. 22:42 Arno Lehmann napisał(a):
> Hi,
> 
> On 4/19/2007 4:48 PM, Mariusz Czulada wrote:
> > Hello,
> > 
> > I have yet another problem to solve. I didn't find similar case in
> > documentation.
> > 
> > I have two separate systems in two locations (let's say "site1" and
> > "site2"). In "site1" I have local DDS5 drive and TS3310 library. In
> > "site2" server is only equiped with DDS5. Also, "Site1" is accesible
> > from "Site2" via WAN. So, "Site1" configuration looks like this:
> > 
> > [...]
> > 
> > We could not buy a dedicated library for "Site2", OTOH TS3310 in "site1"
> > is big enough to hold backups from both sites. So, I thought about
> > migrating jobs stored in "localfiles-2" to a library via WAN connection.
> > IHMO I should add such items:
> > 
> > Site2:
> > - Director2:
> >   * storage: ts3310-1 (@StorageDaemon1)
> >   * pool: tapelibrary-2
> > +storage: ts3310-1
> > 
> > So I could migrate locally stored jobs from "fileststem-2" to
> > "tapelibrary-2" which resides on remote ("Site1") library.
> > 
> > !!
> > 
> > My question is: are there any weak points in this idea?
> 
> Yes...
> 
> > I.e. is it
> > possible to migrate between different storage daemons?
> 
> No, that's not possible. Perhaps it will be implemented some day - I
> talked with Kern about this - but I'm quite sure nobody started
> implementing this.
> 

Hmm... This highly complicates my idea :/ Have to 'redesign' the whole 
concepts...

BTW. If it was mentioned previously - is it possible to add "multi SD 
migration" to the TODO list (question to developers, I think)? I hope 
I'm not the only one to use this feature. IMHO it could be very 
important in backing up multiple/distributed systems, where it is much 
easier and cheaper to have one big library for long term storage then 
equip every system/site with dedicated, smaller libs.

> 
> > Can [slow] WAN
> > connection (some 2 Mb/s I think) affect backup reliability?
> 
> Not reliablility itself, but the duration of the jobs alone makes them
> more easily affected by network problems.
> 

I keep it in mind, but was thinking rather about possibiliy of problems, 
when "feeding SD with data" is [probably] slower then a library/drive 
speed.

> > !!
> > 
> > Any comments and suggestions are gratly appreciated.
> > 
> > Regards,
> > 
> > Mariusz Czulada
> 
> Arno
> 

Mariusz


Książka Benedykta XVI "Jezus z Nazaretu" 
napisana w I rocznicę śmierci Jana Pawła II
już w księgarniach! Zobacz więcej!
http://klik.wp.pl/?adr=http%3A%2F%2Fksiazki.wp.pl%2Fkatalog%2Fksiazki%2Fksiazka.html%3Fkw%3D35343&sid=1109



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


Re: [Bacula-users] Migrating jobs between different SDs (servers)

2007-04-19 Thread Arno Lehmann
Hi,

On 4/19/2007 4:48 PM, Mariusz Czulada wrote:
> Hello,
> 
> I have yet another problem to solve. I didn't find similar case in 
> documentation.
> 
> I have two separate systems in two locations (let's say "site1" and 
> "site2"). In "site1" I have local DDS5 drive and TS3310 library. In 
> "site2" server is only equiped with DDS5. Also, "Site1" is accesible 
> from "Site2" via WAN. So, "Site1" configuration looks like this:
> 
> Site1:
> - StorageDaemon1:
>   * device: filesystem-1
>   * device: dds5-1
>   * autochanger: ts3310-1
> - Director1:
>   * storage: filesystem-1 (@StorageDaemon1)
>   * storage: dds5-1 (@StorageDaemon1)
>   * storage: ts3310-1 (@StorageDaemon1)
>   * pool: localfiles-1
> +storage: filesystem-1
>   * pool: localtape-1
> +storage: dds5-1
>   * pool: tapelibrary-1
> +storage: ts3310-1
> 
> I plan to backup backup hosts to pool "localfiles-1", then migrate it to 
> "tapelibrary-1". "localtape-1" will be used for backupserver itself. 
> Expect no problems with it. Then, "Site2" conf:
> 
> Site2:
> - StorageDaemon2
>   * device: filesystem-2
>   * device: dds5-2
> - Director2:
>   * storage: filesystem-2 (@StorageDaemon2)
>   * storage: dds5-2 (@StorageDaemon2)
>   * pool: localfiles-2
> +storage: filesystem-2
>   * pool: localtape-2
> +storage: dds5-2
> 
> Again, I plan to backup backup hosts from "Site2" to pool "localfiles-2" 
> and "localtape-2" will be used for backupserver itself. Expect no 
> problems with it, either.
> 
> We could not buy a dedicated library for "Site2", OTOH TS3310 in "site1" 
> is big enough to hold backups from both sites. So, I thought about 
> migrating jobs stored in "localfiles-2" to a library via WAN connection. 
> IHMO I should add such items:
> 
> Site2:
> - Director2:
>   * storage: ts3310-1 (@StorageDaemon1)
>   * pool: tapelibrary-2
> +storage: ts3310-1
> 
> So I could migrate locally stored jobs from "fileststem-2" to 
> "tapelibrary-2" which resides on remote ("Site1") library.
> 
> !!
> 
> My question is: are there any weak points in this idea?

Yes...

> I.e. is it 
> possible to migrate between different storage daemons?

No, that's not possible. Perhaps it will be implemented some day - I 
talked with Kern about this - but I'm quite sure nobody started 
implementing this.


> Can [slow] WAN 
> connection (some 2 Mb/s I think) affect backup reliability?

Not reliablility itself, but the duration of the jobs alone makes them 
more easily affected by network problems.

> !!
> 
> Any comments and suggestions are gratly appreciated.
> 
> Regards,
> 
> Mariusz Czulada

Arno

-- 
IT-Service Lehmann[EMAIL PROTECTED]
Arno Lehmann  http://www.its-lehmann.de

-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users


[Bacula-users] Migrating jobs between different SDs (servers)

2007-04-19 Thread Mariusz Czulada
Hello,

I have yet another problem to solve. I didn't find similar case in 
documentation.

I have two separate systems in two locations (let's say "site1" and 
"site2"). In "site1" I have local DDS5 drive and TS3310 library. In 
"site2" server is only equiped with DDS5. Also, "Site1" is accesible 
from "Site2" via WAN. So, "Site1" configuration looks like this:

Site1:
- StorageDaemon1:
  * device: filesystem-1
  * device: dds5-1
  * autochanger: ts3310-1
- Director1:
  * storage: filesystem-1 (@StorageDaemon1)
  * storage: dds5-1 (@StorageDaemon1)
  * storage: ts3310-1 (@StorageDaemon1)
  * pool: localfiles-1
+storage: filesystem-1
  * pool: localtape-1
+storage: dds5-1
  * pool: tapelibrary-1
+storage: ts3310-1

I plan to backup backup hosts to pool "localfiles-1", then migrate it to 
"tapelibrary-1". "localtape-1" will be used for backupserver itself. 
Expect no problems with it. Then, "Site2" conf:

Site2:
- StorageDaemon2
  * device: filesystem-2
  * device: dds5-2
- Director2:
  * storage: filesystem-2 (@StorageDaemon2)
  * storage: dds5-2 (@StorageDaemon2)
  * pool: localfiles-2
+storage: filesystem-2
  * pool: localtape-2
+storage: dds5-2

Again, I plan to backup backup hosts from "Site2" to pool "localfiles-2" 
and "localtape-2" will be used for backupserver itself. Expect no 
problems with it, either.

We could not buy a dedicated library for "Site2", OTOH TS3310 in "site1" 
is big enough to hold backups from both sites. So, I thought about 
migrating jobs stored in "localfiles-2" to a library via WAN connection. 
IHMO I should add such items:

Site2:
- Director2:
  * storage: ts3310-1 (@StorageDaemon1)
  * pool: tapelibrary-2
+storage: ts3310-1

So I could migrate locally stored jobs from "fileststem-2" to 
"tapelibrary-2" which resides on remote ("Site1") library.

!!

My question is: are there any weak points in this idea? I.e. is it 
possible to migrate between different storage daemons? Can [slow] WAN 
connection (some 2 Mb/s I think) affect backup reliability?

!!

Any comments and suggestions are gratly appreciated.

Regards,

Mariusz Czulada


To miały być wakacje jego marzeń. Ale jak dotrzeć nad
morze, gdy jest się Jasiem Fasolą? Rewelacyjna komedia
WAKACJE JASIA FASOLI - w kinach od 20 kwietnia.
http://klik.wp.pl/?adr=http%3A%2F%2Fadv.reklama.wp.pl%2Fas%2Fjas_fasola.html&sid=1104



-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users