Foo wrote:
> The important bit is, how do you handle the junction point? If Bacula
> doesn't understand it, like now, you can either back it up explicitly,
> which is redundant and quite possibly breaks any updates for apps that
> expect a junction point instead of a real directory (or updat
On Sun, 05 Apr 2009 06:20:29 +0200, Kevin Keane
wrote:
> Close, but not quite. The junction, and anything underneath, is simply
> disregarded. As John Drescher mentioned, you probably have to recreate
> it manually.
>
> The data itself actually doesn't even sit under the junction in the
> first
Erik P. Olsen wrote:
> On 03/04/09 21:19, Kevin Keane wrote:
>
>> Erik P. Olsen wrote:
>>
>>> On 03/04/09 18:56, Kevin Keane wrote:
>>>
>>>
Foo wrote:
> On Thu, 02 Apr 2009 17:57:32 +0200, John Drescher
> wrote:
>
>
>
> I think I need to understand it better. If I interpret it correctly then a
> file set including a junction will cause the actual data to be backed-up.
> But what happens if the data has to be restored? Will the actual data be
> restored together with the junction?
>
I do not believe the junction
On 03/04/09 21:19, Kevin Keane wrote:
> Erik P. Olsen wrote:
>> On 03/04/09 18:56, Kevin Keane wrote:
>>
>>> Foo wrote:
>>>
On Thu, 02 Apr 2009 17:57:32 +0200, John Drescher
wrote:
> On Thu, Apr 2, 2009 at 11:27 AM, Kevin Keane
> wrote:
>
Foo wrote:
> On Thu, 02 Apr 2009 17:57:32 +0200, John Drescher
> wrote:
>
>
>> On Thu, Apr 2, 2009 at 11:27 AM, Kevin Keane
>> wrote:
>>
>>> This actually is correct behavior. If you look carefully, you will see
>>> that these two directories are actually not directories at all, but
>
On Thu, 02 Apr 2009 17:57:32 +0200, John Drescher
wrote:
> On Thu, Apr 2, 2009 at 11:27 AM, Kevin Keane
> wrote:
>> This actually is correct behavior. If you look carefully, you will see
>> that these two directories are actually not directories at all, but
>> rather junction points that sim
On Thu, Apr 2, 2009 at 11:27 AM, Kevin Keane wrote:
> This actually is correct behavior. If you look carefully, you will see
> that these two directories are actually not directories at all, but
> rather junction points that simply reference other directories somewhere
> else. Windows junction poi
This actually is correct behavior. If you look carefully, you will see
that these two directories are actually not directories at all, but
rather junction points that simply reference other directories somewhere
else. Windows junction points are like a cross between Linux symlinks
and Linux mou
Hello everyone!
Since several weeks we have a problem on a Windows terminal server. Bacula
reports on two directories, namely
c:/WINDOWS/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a
and
c:/WINDOWS/assembly/GAC_MSIL/IEExecRemote/2.0.0.0__b03f5f7f11d50a3a,
that each of them "
10 matches
Mail list logo
