return false;
}
+#endif
if (!start_storage_daemon_job(jcr, jcr->rstorage, jcr->wstorage,
/*send_bsr*/true)) {
return false;
}
What would be involved in having this patch accepted into the code base?
Regards,
--
--
Jim Barber
DDI Health
-
re to get the fixes?
Or will that just be too hard?
Sort of a related question.
If I upgraded to 3.1.6 and found that it went badly, would it be easy enough to
revert back to 3.0.3 again?
Or will the structure of the database have changed too much? (if at all?)
Thanks,
------
Jim Barber
DDI H
0
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Volume name(s): 18L3
Volume Session Id: 123
Volume Session Time:1258521062
Last Volume Bytes: 369,888,777,216 (369.8 GB)
SD Erro
ation in my configuration is helping to crash
the storage
daemon or not.
If it all goes well, I'll test some other scenarios and submit a patch for your
consideration.
> Regards,
>
> Kern
Regards,
--
Jim Barber
DDI Health
---
s it could be handy to override the NextPool though.
Maybe instead of overriding NextPool in the Schedule, how about in the Job
definition itself?
That way you just reference the appropriate jobs in your schedule to achieve
your Copy or VirtualFull backups.
Regards
Item ?: Allow Schedule Resource to override NextPool
Date: 18 November 2009
Origin: Jim Barber. jim.bar...@ddihealth.com
Status: New request
What: Allow the Schedule resource to define a NextPool= statement
to override the NextPool statement of the pool defined in the job.
Why
