Designing a solution - Domains & Schedules & Client Options

[lipi]

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:

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?

 

[lipi]

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:

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?

There's not any recommendation about this? Is the best way to do what I am trying to achieve?

What's your experience?

Best regards

 

[moon-buddy]

There's not any recommendation about this? Is the best way to do what I am trying to achieve?

What's your experience?

Best regards

I believe you maybe on your own as I don't think that anyone does backups this way. Personally, I think this is too complicated. I also don't understand why you need to do FULL backups during the business times. This can slow down your environment. I haven't encountered a requirement like this for the longest time I have worked with TSM.

Having said these, the idea looks sound. There is only one way to find out if this works - try it!

 

[lipi]

I believe you maybe on your own as I don't think that anyone does backups this way. Personally, I think this is too complicated. I also don't understand why you need to do FULL backups during the business times. This can slow down your environment. I haven't encountered a requirement like this for the longest time I have worked with TSM.

Having said these, the idea looks sound. There is only one way to find out if this works - try it!

When I referred to FULL backup, I intended to mean "backup all filesystem, not only home", sorry for the misunderstanding!.

All my backups are INCREMENTAL!, but of different subsets of files, this is the reason of such configuration, I want some servers to backup everything, and some to backup only /home.

How would you do this backups taking into account that I don't do FULL backups, only Incremental, and that my requeriment is to backup different subsets of data in different operating systems?

 

[moon-buddy]

Even if the backups are incremental (TSM truly do incremental forever by default), why do it during business hours?

Is a simple end-of-business day backup not enough?

If you are concerned for the DB backups, why not use TDP? TDP will backup logs files on the fly and allows restores via these LOG backups.

If you need to backup files as they change continuously, consider another way like using CDP - Continuous Data Protection.

 

[lipi]

Even if the backups are incremental (TSM truly do incremental forever by default), why do it during business hours?

Is a simple end-of-business day backup not enough?

If you are concerned for the DB backups, why not use TDP? TDP will backup logs files on the fly and allows restores via these LOG backups.

If you need to backup files as they change continuously, consider another way like using CDP - Continuous Data Protection.

For one simple reason, 13h is lunch time here. Most of the computers that will be in this 13h schedule will be regular workstations or laptops. Laptops will be shut off at the end of the day, so backups must be done around lunch time.

For other cases contained in D_SERVER_CRITICAL, D_SERVER_STANDARD or D_SERVER_BIGDATA, some servers have an average load of 0.1 during the day. There are other servers that works at night (batch jobs, computing, etc.) , and there are others that works 24h at a high load, so nothing changes if you choose the backup time in "bussines office" time. Of course most of the "common" servers will be backed up during the night.

The point here is that I will be able to select manually the best window time for each client based on its functionality.

I am at a High Performance Computing center, and there are hundreds of users, servers, R&D projects, and each one has specific requirements. I think that my design is the one that's more general in my environment, and at the same time the most flexible for this particular case, but I may be wrong.

I think I'll give it a try and see what fails (if something fails), but first I wanted to hear of you for design alternatives since I am self-learning everything.

pd. In respect to TDP, Continuous data protect, etc. it's another war.

Best regards!,
Felip M