Backup Central

Typically one may 'touch No.Restrictions' to allow any DB to restore to
any other DB host, but in a world of SOX/security and as environments
grow, you probably do not want to be doing that.

Does anyone here use the altnames/<hostname> feature to allow specific DB
hosts to restore to certain/selected hosts only? How does this feature
work for you and have you encountered any problems with it?

Justin.
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

We've used it (6.0MP4), and it pretty much works as advertised
except that we have not had to change the target's client name
to read the source's backups (yay!). You could probably still
initiate restores from the master and direct them wherever you
wanted, but it is more convenient to be able to do it directly
in RMAN.

altnames are one more thing to remember when you rename a client,
and I always have to look up which way the restrictions work when
updating them. For our test DB box to be allowed to read backups
of the production DB, we have something like this:

# cat /opt/openv/netbackup/db/altnames/test-db-box.ua.edu
prod-db-box.ua.edu

Note this has no effect on which media server reads the media
during a restore, just which clients can have the data. If your
DB servers are also SAN media servers you may find it useful to
reassign media.

Robert Griffin
Unix Systems Administrator
OIT, Enterprise Technology
The University of Alabama
<rmg < at > ua.edu> | 205-348-0177

On Mar 13, 2008, at 08:28, veritas-bu-request < at > mailman.eng.auburn.edu
wrote:

Message: 3
Date: Thu, 13 Mar 2008 07:53:43 -0400 (EDT)
From: Justin Piszcz <jpiszcz < at > lucidpixels.com>
Subject: [Veritas-bu] Re-directed Oracle RMAN restores.
To: veritas-bu < at > mailman.eng.auburn.edu
Message-ID: <alpine.DEB.1.00.0803130752270.30811 < at > p34.internal.lan>
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

Typically one may 'touch No.Restrictions' to allow any DB to
restore to
any other DB host, but in a world of SOX/security and as environments
grow, you probably do not want to be doing that.

Does anyone here use the altnames/<hostname> feature to allow
specific DB
hosts to restore to certain/selected hosts only? How does this
feature
work for you and have you encountered any problems with it?

Justin.

_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Typically one may 'touch No.Restrictions' to allow any
DB to restore to any other DB host, but in a world of
SOX/security and as environments grow, you probably do
not want to be doing that.

Does anyone here use the altnames/<hostname> feature
to allow specific DB hosts to restore to certain/selected
hosts only? How does this feature work for you and have
you encountered any problems with it?

Works as advertised for (at least) Oracle and Sybase restores; no
issues.


_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

ditto, Been using the altnames since 4.5,

We have dev db servers that routinely get "refreshed" from the prod db,
so we have the altnames setup so the dev servers can only restore images
from the prod db server.

Use it for RMAN, SAP & Exchange. For file stuff, we just use the admin
console.

From our internal Wiki:
Altnames AKA Restoring backups to Alternate Clients
First point, From the Netbackup Admin GUI (With Backup/Recovery
Privilages) ANy Admin can restore to Any server.

To Restore From The Client, an Image created from a different host, You
need to enable Altnames (Full Details in NBU 6.5 Admin Guide 1 Pg673)

Basically, Create a touch file in /db/altnames/ named with the client
name (as configured in dns and bp.conf file on the client). This lets
that client restore any images from any server. For more security you
can put into the file the client names for backups that client will need
to restore.

* Generally we do not like doing this, so, when possible remove any
of these touch files you can.
o Some Exceptions are the test/dev Database boxes as the DBA's
reguarly perform "refreshes" of the production databases.
* Do Not, where possible allow any Production Database server have a
file left in this location. we do not want to "allow" production
databases to be overwritten with test data.

Adam.

-----Original Message-----
From: veritas-bu-bounces < at > mailman.eng.auburn.edu
[mailto:veritas-bu-bounces < at > mailman.eng.auburn.edu] On Behalf Of bob944
Sent: Friday, 14 March 2008 8:50 AM
To: veritas-bu < at > mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Re-directed Oracle RMAN restores.

Typically one may 'touch No.Restrictions' to allow any DB to restore
to any other DB host, but in a world of SOX/security and as
environments grow, you probably do not want to be doing that.

Does anyone here use the altnames/<hostname> feature to allow specific

DB hosts to restore to certain/selected hosts only? How does this
feature work for you and have you encountered any problems with it?

Works as advertised for (at least) Oracle and Sybase restores; no
issues.


_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

NOTICE: This email and any attachments are confidential.
They may contain legally privileged information or
copyright material. You must not read, copy, use or
disclose them without authorisation. If you are not an
intended recipient, please contact us at once by return
email and then delete both messages and all attachments.


_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

On Thu, 13 Mar 2008, bob944 wrote:

Typically one may 'touch No.Restrictions' to allow any
DB to restore to any other DB host, but in a world of
SOX/security and as environments grow, you probably do
not want to be doing that.

Does anyone here use the altnames/<hostname> feature
to allow specific DB hosts to restore to certain/selected
hosts only? How does this feature work for you and have
you encountered any problems with it?

Works as advertised for (at least) Oracle and Sybase restores; no
issues.


Thanks for the confirmation!
_______________________________________________
Veritas-bu maillist - Veritas-bu < at > mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu