Attachments: Message as HTML
Hi all --
=20
I am trying to use the Windows servers which I know aren't completely suppo=
rted but I have had decent successes with tem thus far. My problem now is =
I am trying to use a network attached storage device which I have mapped as=
a persistent drive on the Windows 2003 box as my Archive Location. I have=
tried every combination of UNC paths, to shared folders, to the mappeded n=
etwork drive itself and no matter what I do I get the following on doing a =
"status storage":
=20
Device status:
Device "NASFileStorage" is not open or does not exist.
=20
and when trying to mount:
=20
../../stored/dev.c:126 Unable to stat device Z:\Backups\Bacula: ERR=3DThe s=
ystem cannot find the path specified.
=20
Device "NASFileStorage" requested by DIR could not be opened or does not ex=
ist.
3999 Device "NASFileStorage" not found or could not be opened.
=20
My initial though was to do a junction/linkd/mountvol/subst to map the shar=
e to a local folder but no luck, doing that is not supported in Windows for=
network\shared drives.
=20
Is using a network drive just not supported by Bacula or is there some crea=
tive way to mount one that I am just not thinking of?
=20
Thanks,
=20
Mike
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=3D7+wonders+world&mkt=3Den-US&form=3DQ=
BRE=
[Bacula-users] Multiple Clients Using Disk Example From: Kyle Marsh
For some reason this didn't post the first time, so here it is again.
In the Bacula manual there is a wonderful example of how to set up
pools for backups to disk using the default three level schedule.
However, the example configuration file only uses one client. I was
wondering if the same configuration works for multiple clients, or if
there is something else to consider. For example, the sample file has
one job per volume for each of 6 volumes in the differential pool, one
for each week in a month (with some slack). If I were to try to run
10 clients on this would it fill that pool on the first week after 6
had backed up? What would happen to the other four; would baucla die
horribly, or overwrite the volumes it just created, or create more
volumes?
Similarly, I seem to need a new client entry and a new job entry for
every machine I want to back up. Many of the machines to be backed up
will change every 4 months or so, and they all will have the same
configuration, so is there any way to condense the amount of
configuration that needs to change? i know about JobDefs, but is
there any BatchJob, say, or a similar ClientDefs?
Thanks,
Kyle Marsh
