On Mon, Jan 10, 2011 at 18:18, Phil Stracchino wrote:
> On 01/10/11 16:49, Mike Ruskai wrote:
> > So simply having the catalog backup be a different priority ensures that
> > no other job can run at the same time, provided mixed priorities are
> > disallowed (that would allow the higher-priority
On 01/10/11 16:49, Mike Ruskai wrote:
> So simply having the catalog backup be a different priority ensures that
> no other job can run at the same time, provided mixed priorities are
> disallowed (that would allow the higher-priority backup jobs to start
> while the catalog backup is under way)
>
> So simply having the catalog backup be a different priority ensures
that
> no other job can run at the same time, provided mixed priorities are
> disallowed (that would allow the higher-priority backup jobs to start
> while the catalog backup is under way). Which is just as well, since
I
> do
On 1/10/2011 4:20 PM, Phil Stracchino wrote:
> On 01/10/11 15:48, Mike Ruskai wrote:
>
>> I know how to backup the database. That's not my question. My question
>> is how to create a schedule, in an environment with multiple concurrent
>> jobs, that guarantees that the catalog backup runs aft
On 01/10/11 15:48, Mike Ruskai wrote:
> I know how to backup the database. That's not my question. My question
> is how to create a schedule, in an environment with multiple concurrent
> jobs, that guarantees that the catalog backup runs after all other
> scheduled jobs, and by itself.
>
> So
On 1/8/2011 2:07 PM, Dan Langille wrote:
> On 1/7/2011 3:03 PM, Mike Ruskai wrote:
>> Right now, I'm backing up to a drive array with one concurrent job. I'd
>> like to increase that, and really need to for a new backup environment
>> I'm creating soon.
>>
>> With the single concurrent job, gettin
On 1/7/2011 3:03 PM, Mike Ruskai wrote:
> Right now, I'm backing up to a drive array with one concurrent job. I'd
> like to increase that, and really need to for a new backup environment
> I'm creating soon.
>
> With the single concurrent job, getting a consistent catalog backup is
> trivial - I j
