lipi
ADSM.ORG Member
- Joined
- Jan 14, 2015
- Messages
- 46
- Reaction score
- 0
- Points
- 0
Hello!,
In my environment I have this kind of clients:
t.1) Standard Servers
t.2) Critical Servers
t.3) Big data Servers
t.4) Users
And this kind of O.S.
o.1) Windows
o.2) MacOS
o.3) Linux
I want this kind of backups:
b.1) Full backup
b.2) Home backup
And I need to apply some sets of restrictions:
r.1) Restricted: exclude *.wmv, *.mp3, *.avi, *.vmdk, /home/*/.cache
r.2) Allow everything: Exclude only garbage, i.e. /home/*/.cache
Also, I want backups to be done, for each client type (t.1, t.2, t.3, t.4), at night and at day.
My plan is to include, for b.2 and every o.1, o.2 and o3:, into the schedule parameter "object=":
sch_b.2_o.1) object="C:/Users"
sch_b.2_o.2) object="/Users"
sch_b.2_o.3) object="/home"
From this requirements I obtain this:
What do you think about this design?
Any suggestion to improve or simplify it?
In my environment I have this kind of clients:
t.1) Standard Servers
t.2) Critical Servers
t.3) Big data Servers
t.4) Users
And this kind of O.S.
o.1) Windows
o.2) MacOS
o.3) Linux
I want this kind of backups:
b.1) Full backup
b.2) Home backup
And I need to apply some sets of restrictions:
r.1) Restricted: exclude *.wmv, *.mp3, *.avi, *.vmdk, /home/*/.cache
r.2) Allow everything: Exclude only garbage, i.e. /home/*/.cache
Also, I want backups to be done, for each client type (t.1, t.2, t.3, t.4), at night and at day.
My plan is to include, for b.2 and every o.1, o.2 and o3:, into the schedule parameter "object=":
sch_b.2_o.1) object="C:/Users"
sch_b.2_o.2) object="/Users"
sch_b.2_o.3) object="/home"
From this requirements I obtain this:
Code:
DOMAINS AVAILABLE:
D_SERVER_STANDARD
D_SERVER_CRITICAL
D_SERVER_BIG
D_USER
CLIENTOPT:
CLOPT_MAC_EVERYTHING
CLOPT_WIN_EVERYTHING
CLOPT_LIN_EVERYTHING
CLOPT_MAC_RESTRICTED
CLOPT_WIN_RESTRICTED
CLOPT_LIN_RESTRICTED
Schedules for D_USER:
SCH_MAC_HOME_13h
SCH_LIN_HOME_13h
SCH_WIN_HOME_13h
SCH_MAC_FULL_13h
SCH_LIN_FULL_13h
SCH_WIN_FULL_13h
SCH_MAC_HOME_01h
SCH_LIN_HOME_01h
SCH_WIN_HOME_01h
SCH_MAC_FULL_01h
SCH_LIN_FULL_01h
SCH_WIN_FULL_01h
Schedules for D_SERVER_CRITICAL:
SCH_MAC_HOME_04h
SCH_LIN_HOME_04h
SCH_WIN_HOME_04h
SCH_MAC_FULL_04h
SCH_LIN_FULL_04h
SCH_WIN_FULL_04h
SCH_MAC_HOME_16h
SCH_LIN_HOME_16h
SCH_WIN_HOME_16h
SCH_MAC_FULL_16h
SCH_LIN_FULL_16h
SCH_WIN_FULL_16h
Schedules for D_SERVER_STANDARD:
SCH_MAC_HOME_05h
SCH_LIN_HOME_05h
SCH_WIN_HOME_05h
SCH_MAC_FULL_05h
SCH_LIN_FULL_05h
SCH_WIN_FULL_05h
SCH_MAC_HOME_17h
SCH_LIN_HOME_17h
SCH_WIN_HOME_17h
SCH_MAC_FULL_17h
SCH_LIN_FULL_17h
SCH_WIN_FULL_17h
Schedules for D_SERVER_BIG:
SCH_MAC_HOME_08h
SCH_LIN_HOME_08h
SCH_WIN_HOME_08h
SCH_MAC_FULL_08h
SCH_LIN_FULL_08h
SCH_WIN_FULL_08h
SCH_MAC_HOME_20h
SCH_LIN_HOME_20h
SCH_WIN_HOME_20h
SCH_MAC_FULL_20h
SCH_LIN_FULL_20h
SCH_WIN_FULL_20h
What do you think about this design?
Any suggestion to improve or simplify it?