Hi Bobby
One past employer had a requirement to do monthly archives and I found,
as you have that the admins would change the filesystems on nodes
without notifying anyone.
My solution was a perl script that went through the filesystems table
for all BA client nodes and checked the last backup d
.edu] On Behalf
> Of bobby
> Sent: Thursday, June 25, 2009 8:32 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [ADSM-L] Managing TSM Schedules
>
> The TSM admin configures the backups as per the requirements recieved
> from the system admins. I am doing the task in absence of
On Jun 25, 2009, at 9:32 AM, bobby wrote:
The TSM admin configures the backups as per the requirements
recieved from the system admins. I am doing the task in absence of
the TSM admin.
TSM consists of a client side and a server side, where there are
administrators (often, separate) for each si
The TSM admin configures the backups as per the requirements recieved from the
system admins. I am doing the task in absence of the TSM admin.
The issue is that our archives are not consistent with the incremental backups.
The archive and the incremental are not necessarily backing up the same d
The approach to architecting client schedules often depends upon the
structure of the organization in which you work. The computer systems
within an organization may be exclusively within the purview of the
administrators of those machines, where they should be the only ones
formulating TSM clien
Hi all,
Our TSM server runs on AIX and backs up 100+ window server(client nodes).
These clients have different drives configured (depending on the servers
functionality) and we need to back them up accordingly.
Incremental backups are scheduled to run daily by attaching 10 nodes to a
'Schedule
