Re: [Veritas-bu] Backup Policy - Responsibility for adding client intoNBU
2009-02-17 16:03:51
We've basically got three layers of control on
this. First, before any server is handed over to an application group the
person who builds / preps the server (via check sheet) must verify that backups
are configured. Then again, before any server gets transferred
into production the person transferring the server into production (again a
check sheet) must verify backups are configured and running. Finally, we
run a biannual review of the asset sheets versus the backup records and
manually address any discrepancies. (Server A with Asset Tag 12345 but no
backups etc..) We have similar procedures for adding storage to any
server.
-Jonathan
What we have done is to have the SA
submit a Change Record to have servers added, removed, or if the backup has
volume changes to the server environment, since they regularly work with the
business clients and know about 'most' changes to the server. There have
been times, however, where the business client has changed things on the server
and not informed the SA. In this case, the business contact takes
responsibility for the lost data as they generally have access to the server for
application maintenance, but never let the SA know about the changes that were
performed.
We have also had the
experience where the SA forgot to add the Change Record. On multiple
occasions, we have had to go back to our Change Control system and verify that
there was no Change Record, which prevented any finger pointing.
At first, the SA's balked at the little bit
of extra work, but this has been included into all of our processes and is not
an issue now. We will occasionally do an addition before a Change Record
has been created, but in these cases, we hound the SA's until they cannot stand
it anymore and create the needed record.
Mike
----- Message from "WEAVER, Simon \(external\)"
<simon.weaver AT astrium.eads DOT net> on Tue, 17 Feb 2009 16:01:40 -0000
-----
To:
|
<veritas-bu AT mailman.eng.auburn DOT edu>
|
Subject:
|
[Veritas-bu] Backup Policy -
Responsibility for adding client into NBU |
All A
general chit -chat question really. I discovered a project where it holds 500mb
Data and was NOT backed up !
The only reason this came to light was due
to a problem on the Server, when the NBU Admin realised it had not been backed
up (but should have been).
Looking at the history, it was backed up,
but somehow its been removed from a Policy. Luckily, the fault was rectified and
all data was recovered intact.
Question is this - who is responsible for
ensuring any new Servers get backed up into your Backup Environment? Sometimes I
think its easy to blame the NBU admin, but how do they know what should or
should not be backed up.
Does anyone have any process or routine in
place or regular checks with their System Admins to make sure the backup client
lists have not changed or need new servers backed up?
Regards
Simon
This email (including any attachments)
may contain confidential and/or privileged information or information
otherwise protected from disclosure. If you are not the intended
recipient, please notify the sender immediately, do not copy this
message or any attachments and do not use it for any purpose or
disclose its content to any person, but delete this message and any
attachments from your system. Astrium disclaims any and all liability
if this email transmission was virus corrupted, altered or
falsified. -o- Astrium Limited, Registered in England and Wales No.
2449259 Registered Office: Gunnels Wood Road, Stevenage,
Hertfordshire, SG1 2AS, England |
-----
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|