ADSM-L

Re: [ADSM-L] Restore Individual File from NDMP COPYPOOL

2016-05-12 12:25:40
Subject: Re: [ADSM-L] Restore Individual File from NDMP COPYPOOL
From: Shawn DREW <shawn.drew AT US.BNPPARIBAS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 12 May 2016 16:21:48 +0000
You can figure out which tapes the backup occupies by looking at the backups 
and contents  tables.  Since NDMP backups are single objects it isn't as 
unpleasant as looking through the backups table for regular backup files. 

Just a quick overview:
- Get object IDs for the backup image(s) (Get filespace id from "q fi")
select NODE_NAME, FILESPACE_NAME, FILESPACE_ID, cast(BACKUP_DATE as date) as 
"Date", OBJECT_ID from backups where node_name='NDMP_NODENAME' and 
FILESPACE_ID=16 and BACKUP_DATE >= '2011-06-20' and BACKUP_DATE <= '2012-02-15' 
order by "Date" 
- select volume_name, object_id from contents where 
OBJECT_ID=NUMBERs_FROM_PREV_STEP

This will give you the volume names for both pools and TOC's if you have them. 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Plair, Ricky
Sent: Thursday, May 12, 2016 11:18 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Restore Individual File from NDMP COPYPOOL

The copy pool is  pushed offsite every day.  And, that is one of the problems, 
I don’t know what the tape number is in the copy pool. 

In the past, for different kinds of restores, if the primary pool media is not 
available it usually tells you a different tape number from the copy pool and 
you can recall it.


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray
Sent: Thursday, May 12, 2016 10:57 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Restore Individual File from NDMP COPYPOOL

Dumb question but is the copypool tape marked as offsite/offline (I know all of 
my offsite tapes are marked as such)

On Thu, May 12, 2016 at 10:52 AM, Plair, Ricky <rplair AT healthplan DOT com>
wrote:

> HELP PLEASE!
>
> I have an EMC Ision that I'm backing up with TSM 7.1.10.
>
> Using TSM I can restore a file back to the Isilon, with no problem.
>
> My problem is, if I take the tape media that TSM used during the 
> successful restore to the Isilon from the primary pool and change it 
> unavailable, TSM should call on the tape media from the copy pool, right?
>
> The restore fails with media not available.
>
> We are backing up the Isilon with data movers straight to tape with 
> schedules on the TSM server. We are not using EMC Backup Accelerator.
>
> I appreciate any help I can get.
>
>
>
>
> Ricky M. Plair
> Storage Engineer
> HealthPlan Services
> Office: 813 289 1000 Ext 2273
> Mobile: 813 357 9673
>
>
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ _ _ CONFIDENTIALITY NOTICE: This email message, including any 
> attachments, is for the sole use of the intended recipient(s) and may 
> contain confidential and privileged information and/or Protected 
> Health Information (PHI) subject to protection under the law, 
> including the Health Insurance Portability and Accountability Act of 
> 1996, as amended (HIPAA). If you are not the intended recipient or the 
> person responsible for delivering the email to the intended recipient, 
> be advised that you have received this email in error and that any 
> use, disclosure, distribution, forwarding, printing, or copying of 
> this email is strictly prohibited. If you have received this email in 
> error, please notify the sender immediately and destroy all copies of the 
> original message.
>



--
*Zoltan Forray*
TSM Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never 
use email to request that you reply with your password, social security number 
or confidential personal information. For more details visit 
http://infosecurity.vcu.edu/phishing.html

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
CONFIDENTIALITY NOTICE: This email message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information and/or Protected Health Information (PHI) subject to 
protection under the law, including the Health Insurance Portability and 
Accountability Act of 1996, as amended (HIPAA). If you are not the intended 
recipient or the person responsible for delivering the email to the intended 
recipient, be advised that you have received this email in error and that any 
use, disclosure, distribution, forwarding, printing, or copying of this email 
is strictly prohibited. If you have received this email in error, please notify 
the sender immediately and destroy all copies of the original message.

This message and any attachments (the "message") is intended solely for the 
addressees and is confidential. If you receive this message in error, please 
delete it and immediately notify the sender. Any use not in accord with its 
purpose, any dissemination or disclosure, either whole or partial, is 
prohibited except formal approval. The internet can not guarantee the integrity 
of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore 
be liable for the message if modified. Please note that certain functions and 
services for BNP Paribas may be performed by BNP Paribas RCC, Inc.


Unless otherwise provided above, this message was sent by BNP Paribas, or one 
of its affiliates in Canada, having an office at 1981 McGill College Avenue, 
Montreal, QC, H3A 2W8, Canada. To the extent this message is being sent from or 
to Canada, you may unsubscribe from receiving commercial electronic messages by 
using this link: www.bnpparibas.ca/en/unsubscribe/ 
<http://www.bnpparibas.ca/en/unsubscribe/>. See www.bnpparibas.ca 
<http://www.bnpparibas.ca> for more information on BNP Paribas, in Canada.
<Prev in Thread] Current Thread [Next in Thread>