Hello,
the "client name" is only relevant in the logs, as long as you address
the client correctly (ip address or dns) that doesn't matter.
Consider it a "feature" as you can see in the logs on which client the
clustered instance backup ran
--Simone
On 30 July 2012 11:41, Carlo Filippetto <carlo.filippetto < at > gmail.com> wrote:
How can you create 4 istance? is this the problem
You install only 1 instance on every single node specifying 3 IP (1
for the host and 2 for the resources) with the use of "FDAddresses"?
For example:
If i need ot backup the "proxy" resource that is on node-A I need 2 jobs
1) with / FileSet
2) with /proxy FileSet
For those backup I need to set up 2 jobs that will points 2 different client
- CLIENT NAME = node-a (192.168.1.20)
- CLIENT NAME = proxy (192.168.1.22)
Is this correct?
the backup will not fails when found on the node-A server only one
"client name" that is "node-A"??
I hope you understood my question
---
Carlo
2012/7/30 Simone Caronni <negativo17 < at > gmail.com>:
Hello,
I had run Bacula clients on many clusters (Both Windows and RHEL), I
usually configure all the cluster nodes with the same password and in
the Director's config I treat the "virtual" instances as additional
nodes in Bacula. If I'm talking to the nodes, only local data is
backed up, if I point to virtual instnces only the clusterized data is
backed up.
This way I was able to backup anything and is especially handy with
clustered Microsoft services. For example, a clustered SQL server in
Active / Active configuration:
Node 1: Drive C: and D:
Node 2: Drive C: and D:
SQL Resource 1: Drive E:
SQL Resource 2: Drive F:
Will result in the director talking to 4 servers. This way, if the
resource moves from one node to the other even Incremental backups are
performed and no errors are returned for disappearing drives and
paths. Same config can be applied to Linux servers with shared paths
in active / standby configurations.
The only config requirement is to leave the client daemons listen on
all ip addresses, have the same password and make sure the filesets
are different.
Regards,
--Simone
On 30 July 2012 10:35, Carlo Filippetto <carlo.filippetto < at > gmail.com> wrote:
Hi all,
I have a cluster (node-A & node-B) with 2 partition "/proxy" & "/mail"
that are clusterized.
node-A is the default to owner of /proxy
node-B is the default to owner of /mail
everyone have a specific IP included the services es:
- node-A = 192.168.1.20
- node-B = 192.168.1.21
- proxy = 192.168.1.22
- mail = 192.168.1.23
I need to backup all in every case, expecially when the cluster is
degraded, so I image that I need 4 bacula-fd's istance, 2 for the
nodes, and 2 for the services.
In you opinion what is the best practise to configure this istances?
I need to clusterize the 2 istance connected with the services?
Thank you.
---
Carlo Filippetto
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
You cannot discover new oceans unless you have the courage to lose
sight of the shore (R. W. Emerson).
--
You cannot discover new oceans unless you have the courage to lose
sight of the shore (R. W. Emerson).
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Bacula-users mailing list
Bacula-users < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
