Re: Removing client node from copypool
2003-05-08 10:00:00
unless someone knows another way, the only way I can see to fix this is to
create a storage pool just for that node or better yet group of nodes which
you don't want there data to go offsite, and then just make sure there
storage pool is not included in the backup storage pool script, or however
you may run it...
--Justin Richard Bleistein
Unix/TSM Systems Administrator (Sungard eSourcing)
Desk: (856) 566 - 3485
Cell: (856) 912 - 0861
Email: justin.bleistein AT sungard DOT com
Zlatko
Krastev/ACIT To: ADSM-L AT VM.MARIST
DOT EDU
<[email protected] cc:
ET> Subject: Re: Removing client
node from copypool
Sent by: "ADSM:
Dist Stor
Manager"
<[email protected]
.EDU>
05/07/2003 09:50
PM
Please respond to
"ADSM: Dist Stor
Manager"
Better ask first your management "Is this the most unimportant data for
the company?"
What should you do when you need to restore and media is corrupt? Install
it from scratch and call the consultants to implement it again?
Zlatko Krastev
IT Consultant
Raminder Braich <Raminder.Braich AT DAVEY DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
05.05.2003 18:19
Please respond to "ADSM: Dist Stor Manager"
To: ADSM-L AT VM.MARIST DOT EDU
cc:
Subject: Removing client node from copypool
Hi All,
We have SAP R/3 backup every night using TDP. It takes about 8 hrs
to back it up. It takes about the same amount of time to make copypool
tapes to go offsite. A request has been made that we make a change so that
this client does not make copypool or offsite tapes. However, the primary
pool tapes have to be identified and sent offsite instead of copypool
tapes for this particular client. The idea is that it would save time and
free up some tape drives to do some other backups.
Is it at all possible to have this client not make copypool tapes.
Also, how can I identify and eject the primary pool tapes for this client
to go offsite.
Thanks,
Raminder Braich
|
|
|