cancel
Showing results for 
Search instead for 
Did you mean: 

disk staging and volume pools

Graeme_Welsh
Level 5
when using disk staging, is it possible to use differing volume pools as destination volume pool? e.g. when staging from disk to tape on mon-->thur, copy to volume pool daily, or to volume pool weekly etc
7 REPLIES 7

AKopel
Level 6
Not with the same DSSUl...
The only way you could do this is to create 2 Disk Staging storage units assigned to your 2 vol pools, and then create 2 different schedules assigned to each DSSU.

Example:
Friday FULL: WEEKLY with DSSU weekly
Mon-Thur : DAILY with DSSU daily

Stumpr2
Level 6
No automatic process is available, but you could manually change the final destination unit every week for the weekly. Not something I would like to do.

However, the data will already be put on different tapes if the retention is different between the dailys and weeklys.

Stumpr2
Level 6
Aarons solution is good but I would hesitate to do this until you are at 5.1_MP4 or greater as the migration is much more flexible for the number of jobs created and the sizing of the jobs is also configurable.

Graeme_Welsh
Level 5
mmmm,
ok, if for instance, both DSSUS were folders on say, D:\
called
D:\DailyStaging
D:\WeeklyStaging

if the disk filled up during the 'weekly staging' job, Netbackup be clever enough to delete images from d:\dailystaging that had already been committed to tape? (since low watermark dosent work in NBU 6.0...)..

Graeme_Welsh
Level 5
would it then be easy enough to find which tapes had been used in each staging process?

AKopel
Level 6
Yes,
as long as you stage to tape daily (which is what we do) the dailystaging images will remove from disk automatically when space is needed.

As for finding the tapes, You can do your normal search of the catalog to find which ones were written to.

Stumpr2
Level 6
One fine point that may help you understand a little bit more, is that the staging creates a second copy on tape. The original copy also remains on the staging unit. If a restore request is issued then the image will be pulled from the disk as it is the primary copy. When the disk staging unit becomes full it will then expire the image on the disk and promote the image that is on tape to become the primary copy.

I guess what I am trying to relay is that the expiration of the oldest image on the disk is done immediately when the disk becomes full (5.x) or when the threshold has been exceeded (6.x). There is virtually no wait time for availabiulity of space on the disk. It does not have to wait for the image to be copied to tape since that migration already occurred ...days ago. well hopefully :-)Message was edited by:
Bob Stump