On 08/31/10 16:30, Prashant Ramhit wrote:
> Hi All,
>
> I want to add 52 volume in a pool.
>
> Could someone please send me the sql to add a volume with the following
> parameters
Why would you want to use SQL to do this?
> Volume name= "week40" ( this is a variable and will be auto generated
Hi All,
I want to add 52 volume in a pool.
Could someone please send me the sql to add a volume with the following
parameters
Volume name= "week40" ( this is a variable and will be auto generated,
for the time being please consider week40)
Catalogue=weekly_offsite
Pool=weekly
Slot=6
InChanger
Marco Lertora wrote:
Il 31/08/2010 17.27, Bill Arlofski ha scritto:
On 08/31/10 08:44, Marco Lertora wrote:
Hi!
I've the same problem! anyone found a solution?
I have 3 concurrent jobs, which backup from different fd to the same
device on sd.
All jobs use the same pool and the po
Il 31/08/2010 17.27, Bill Arlofski ha scritto:
> On 08/31/10 08:44, Marco Lertora wrote:
>>Hi!
>>
>> I've the same problem! anyone found a solution?
>>
>> I have 3 concurrent jobs, which backup from different fd to the same
>> device on sd.
>> All jobs use the same pool and the pool use "Maxi
On 08/31/10 08:44, Marco Lertora wrote:
> Hi!
>
> I've the same problem! anyone found a solution?
>
> I have 3 concurrent jobs, which backup from different fd to the same
> device on sd.
> All jobs use the same pool and the pool use "Maximum Volume Bytes" as
> volume splitting policy, as sugg
On 8/31/2010 5:44 AM, Marco Lertora wrote:
>Hi!
>
> I've the same problem! anyone found a solution?
>
> I have 3 concurrent jobs, which backup from different fd to the same
> device on sd.
> All jobs use the same pool and the pool use "Maximum Volume Bytes" as
> volume splitting policy, as su
Hi!
I've the same problem! anyone found a solution?
I have 3 concurrent jobs, which backup from different fd to the same
device on sd.
All jobs use the same pool and the pool use "Maximum Volume Bytes" as
volume splitting policy, as suggested in docs.
All job has the same priority.
Everythin
A bit frustrating at the moment as I don’t have access to the host. We are
backing up Windows and Linux clients. The windows host seem to have no issues,
very curious.
-Original Message-
From: m...@free-minds.net [mailto:m...@free-minds.net]
Sent: 31 August 2010 11:15
To: Suhail Akhtar
Mh no but 144h run time sound like the process was hunging and then
killed...
On Tue, 31 Aug 2010 05:49:39 -0400, "Suhail Akhtar"
wrote:
> Hi,
>
> I was wondering if anyone has come across the following error message.
>
> 'Error: Watchdog sending kill after 518424 seconds to thread stalled
>
Hi,
I was wondering if anyone has come across the following error message.
'Error: Watchdog sending kill after 518424 seconds to thread stalled
reading Storage daemon'
I don't have access to the host generating the message as yet, but hope
to soon so I can have a snoop around. Not quite
10 matches
Mail list logo
