Re: LTO4 Tape Volumes with diferent Estimated Capacity
Hello all Thank you for your all answers. Regarding to your experience what is more efficiency regarding to tape usage capacity (increase tape amount of data stored)? Compression on client or compression on Drive(HW)? Cumprimentos / Best regards Tiago Botelho -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Botelho, Tiago (External) Sent: quarta-feira, 18 de Janeiro de 2012 15:27 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity Hello I have several tape volumes (LTO4) with different Estimated Capacity. What can cause this situation? Ex: A00035L4 WIN_SRV_T TS3310 629.5 G 95.4 Full A00039L4 WIN_SRV_T TS3310 1.1 T 98.2 Full A00101L4 WIN_SRV_T TS3310 884.8 G 84.4 Full A00113L4 WIN_SRV_T TS3310 1.0 T 93.7 Full A00118L4 WIN_SRV_T TS3310 1.0 T 73.6 Full A00128L4 WIN_SRV_T TS3310 1.0 T 99.2 Full A00129L4 WIN_SRV_T TS3310 969.1 G 93.7 Full A00133L4 WIN_SRV_T TS3310 934.8 G 96.1 Full All tapes and Drives are LTO4, TSM Server 553 for AIX. The devc are configured as: Device Class Name: TS3310 Device Access Strategy: Sequential Storage Pool Count: 16 Device Type: LTO Format: ULTRIUM4C Est/Max Capacity (MB): Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 60 Label Prefix: ADSM Library: TS3310 Directory: Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Off Scaled Capacity: Last Update by (administrator): ADM Last Update Date/Time: 07/27/09 17:32:05 Cumprimentos / Best regards Tiago Botelho
Low level tape drives for TSM
Hello Everybody, We are using disk pools at Head Office and Disaster Site connected by fiber optics links (DS8100 online mirroring and 1GB Ethernet). We are using SCSI tape drives 3590 only for out-of-country copies with daily amount less than 1TB. We need to replace 3590 drives by something newer. We are looking for tape drives: 1) supported by TSM 5.5 and 6.X; 2) supported by AIX on Power6 and Power7 logical partitions; 3) connected via fiber optics switch (at least 2Gb/s) or via network (at least 1Gb/s); 4) with volume capacity 128GB or more (not compressed); 5) just drive or manual library like 3590. I will deeply appreciate any suggestions or links to documents. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw Please consider the environment before printing this E-mail CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email.
Ang: Low level tape drives for TSM
Hi I'm taking it as if you'd like to have standalone tape drive which are connected through your SAN/network environment. Most standalone tape drives I know of use SAS or LVD interfaces. FC is most commonly used in tape libraries since FC is aimed at larger, centralized environments. I dont know of any tape drives that are utilizing a network connection, since the network connection would require intelligent hardware to utilize (standalone tape drives usually dont have an TCP/IP stack built in to them). If you tried explaining what you are trying to accomplish having the standalone tape drives, perhaps it would be easier to help you out. As far as I know, TSM cant utilize a network-attached tape drive so I'm assuming you're planning something else. Best Regards Daniel Sparrman Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30 daniel.sparr...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Grigori Solonovitch Sänt av: ADSM: Dist Stor Manager Datum: 01/19/2012 11:25 Ärende: Low level tape drives for TSM Hello Everybody, We are using disk pools at Head Office and Disaster Site connected by fiber optics links (DS8100 online mirroring and 1GB Ethernet). We are using SCSI tape drives 3590 only for out-of-country copies with daily amount less than 1TB. We need to replace 3590 drives by something newer. We are looking for tape drives: 1) supported by TSM 5.5 and 6.X; 2) supported by AIX on Power6 and Power7 logical partitions; 3) connected via fiber optics switch (at least 2Gb/s) or via network (at least 1Gb/s); 4) with volume capacity 128GB or more (not compressed); 5) just drive or manual library like 3590. I will deeply appreciate any suggestions or links to documents. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw Please consider the environment before printing this E-mail CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email.
Re: Low level tape drives for TSM
Sounds like you are looking for something in the 3592 class. We are using ts1120 drives. 300 gB uncompressed, fibrechannel connection 2 gb, tsm 5 and 6 support them, usable in a manual library. Don't know about the AIX questions, but don't know why they wouldn't be supported. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Thursday, January 19, 2012 5:23 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Low level tape drives for TSM Hello Everybody, We are using disk pools at Head Office and Disaster Site connected by fiber optics links (DS8100 online mirroring and 1GB Ethernet). We are using SCSI tape drives 3590 only for out-of-country copies with daily amount less than 1TB. We need to replace 3590 drives by something newer. We are looking for tape drives: 1) supported by TSM 5.5 and 6.X; 2) supported by AIX on Power6 and Power7 logical partitions; 3) connected via fiber optics switch (at least 2Gb/s) or via network (at least 1Gb/s); 4) with volume capacity 128GB or more (not compressed); 5) just drive or manual library like 3590. I will deeply appreciate any suggestions or links to documents. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw Please consider the environment before printing this E-mail CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email.
Re: compression
I always use compression at the drive level. No need to have the client doing all that work. However, if you have particularly slow network connections, client compression might be useful. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Botelho, Tiago (External) Sent: Thursday, January 19, 2012 4:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity Hello all Thank you for your all answers. Regarding to your experience what is more efficiency regarding to tape usage capacity (increase tape amount of data stored)? Compression on client or compression on Drive(HW)? Cumprimentos / Best regards Tiago Botelho -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Botelho, Tiago (External) Sent: quarta-feira, 18 de Janeiro de 2012 15:27 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity Hello I have several tape volumes (LTO4) with different Estimated Capacity. What can cause this situation? Ex: A00035L4 WIN_SRV_T TS3310 629.5 G 95.4 Full A00039L4 WIN_SRV_T TS3310 1.1 T 98.2 Full A00101L4 WIN_SRV_T TS3310 884.8 G 84.4 Full A00113L4 WIN_SRV_T TS3310 1.0 T 93.7 Full A00118L4 WIN_SRV_T TS3310 1.0 T 73.6 Full A00128L4 WIN_SRV_T TS3310 1.0 T 99.2 Full A00129L4 WIN_SRV_T TS3310 969.1 G 93.7 Full A00133L4 WIN_SRV_T TS3310 934.8 G 96.1 Full All tapes and Drives are LTO4, TSM Server 553 for AIX. The devc are configured as: Device Class Name: TS3310 Device Access Strategy: Sequential Storage Pool Count: 16 Device Type: LTO Format: ULTRIUM4C Est/Max Capacity (MB): Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 60 Label Prefix: ADSM Library: TS3310 Directory: Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Off Scaled Capacity: Last Update by (administrator): ADM Last Update Date/Time: 07/27/09 17:32:05 Cumprimentos / Best regards Tiago Botelho
Re: Drive and Path Definition
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/18/2012 06:28:41 PM: In the past we've never had to restart TSM to add a new drive. As long as the drive was discovered and available at the AIX layer, we could define the new drive. Has this changed with v6.2.x? It's my experience that any change to the library (adding slots or drives) requires cycling TSM before it can access the new resource. Seriously? Is this behavior due to changes in TSM 6.x, or has it always been this way for SCSI-style (smcX) libraries? I've never had this issue with my 3494 library and any TSM version from ADSM 2.1 through TSM 5.5. Our libraries are 3584 scsi libraries, which are different animals from 3494 libraries. Sorry, I should have said that. Any time we have changed the physical library it has required us to bounce TSM so the new slots EA and/or drive EA are available to TSM. In our case, that's our library manager tsm instance. We are still on v5.5, but I've seen nothing that would indicate that v6+ is any different. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
EXPORT command help
Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: EXPORT command help
I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: Drive and Path Definition
On Jan 19, 2012, at 8:19 AM, Richard Rhodes wrote: ... Our libraries are 3584 scsi libraries, which are different animals from 3494 libraries. Sorry, I should have said that. Any time we have changed the physical library it has required us to bounce TSM so the new slots EA and/or drive EA are available to TSM. In our case, that's our library manager tsm instance. We are still on v5.5, but I've seen nothing that would indicate that v6+ is any different. Rick - Have you tried Audit Library as part of the change procedure? It should perform a reconciliation with the reality of the library, using the same functionality that occurs when TSM restarts and checks the library. Richard Sims
Re: EXPORT command help
You could use filedata=allactive which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: Re: Drive and Path Definition
On 01/18/2012 06:28 PM, David Bronder wrote: Richard Rhodes wrote: In the past we've never had to restart TSM to add a new drive. As long as the drive was discovered and available at the AIX layer, we could define the new drive. Has this changed with v6.2.x? Seriously? Is this behavior due to changes in TSM 6.x, or has it always been this way for SCSI-style (smcX) libraries? I've never had this issue with my 3494 library and any TSM version from ADSM 2.1 through TSM 5.5. Me too; 3494 and 3584 both, I've not needed to restart TSM to begin accessing new devices. - Allen S. Rout
Re: EXPORT command help
This is probably why, notice it does say the export was a success however there is a ONE file difference 01/18/12 19:30:03 ANR0673W EXPORT NODE: Data storage retrieve or restore failed - error detected. (SESSION: 782588, PROCESS: 75573) 01/19/12 05:58:38 ANR0611I EXPORT NODE started by admin1 as process 75573 has ended. (SESSION: 782588, PROCESS: 75573) 01/19/12 05:58:38 ANR0986I Process 75573 for EXPORT NODE running in the BACKGROUND processed 458,221 items for a total of 483,947,840,323 bytes with a completion state of SUCCESS at 05:58:38. (SESSION: 782588, PROCESS: 75573) thanks -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, January 19, 2012 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT command help You could use filedata=allactive which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: EXPORT command help
Thanks Rick, What happen was this node was exported from one TSM server to another and 1 file apparently did go over but wait can't afford to lose 1 file from this node so I just need to get that 1 file. Will the filedata=allactive command just get that 1 file only? TSMSERVER A BOVSRV3CC Bkup \\Bovsrv3- 3 LTO64POOL409,136 455,041.4 453,092.4 \d$ 1 1 TSMSERVER B BOVSRV3CC Bkup \\Bovsrv3- 3 LTO3POOL 409,135 452,932.4 452,920.9 \d$ 4 1 Thanks again -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, January 19, 2012 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT command help You could use filedata=allactive which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: Drive and Path Definition
On 01/19/2012 01:37 AM, Roger Deschner wrote:
Pay attention to the fact that typically rmtN, mtN, and TSM driveN
device numbers will be different. Make sure the serial numbers in TSM Q
DRIVE F=D are correct.
... This, a whole bunch.I'll drop a few scripts here I use to
automate the process.
First, I've got a file which associates TSM drive names with serial
numbers. In my scripts it's referenced as
'/var/tsm/base/etc/device-correspondence.csv', but of course you can
store it anywhere. It looks like this:
DRIVE0,07892730,460,new
DRIVE1,07892835,470,new
DRIVE2,07892870,480,new
The third field there is me keeping track of how the 3494 sees the
drive. Useful to communicate with SE, who'll tell you that drive 300
had an intervention. My scripts only use the first two fields;
unfinished plans, et. alia.
Then I've got the attached script 'tape-config', which looks at all of
your tape devices and ties them, through the serial number, to your TSM
drive label. It drops a bunch of files in ., each one of which holds
all the lsdev output for devices attached to that serial.
The last step is the attached script 'tape-paths', which takes all the
collected devices, and then dumps path updates (or if you tell it to,
defines) to stdout. It expects to be run in the directory where you
collected tape-config. Its output looks something like this:
root@tsm4 tapes-2011-12 # ./tape-paths -server foo -define
define path foo DRIVE9 srct=server destt=drive libr=3592lib
device=/dev/rmt8
define path foo DRIVE6 srct=server destt=drive libr=3592lib
device=/dev/rmt4
define path foo DRIVE8 srct=server destt=drive libr=3592lib
device=/dev/rmt9
[...]
or
root@tsm4 tapes-2011-12 # ./tape-paths -server foo
update path foo DRIVE9 srct=server destt=drive libr=3592lib
device=/dev/rmt8
update path foo DRIVE6 srct=server destt=drive libr=3592lib
device=/dev/rmt4
update path foo DRIVE8 srct=server destt=drive libr=3592lib
device=/dev/rmt9
[...]
All in all, it's sufficiently easy that I approach even broad
renumbering and fabric changes with equanimity. We recently split our
fiber into two independant fabrics, and I basically:
+ set all drives offline.
+ recabled the last few links.
+ rmdev -d -l every rmt device
+ cfgmgr
+ instAtape -a to get multipath data in place
+ run tape-config
and then at the bash prompt:
# for server in int ext glmail01 glmail02 whole list of servers; \
tape-paths -server $server
which gives output you can just paste into your library manager.
- Allen S. Rout
#!/usr/local/bin/perl
use FileHandle;
use Data::Dumper;
my $verbose =1;
my $in = new FileHandle;
my $drives = {};
my $out = {};
$in-open(/var/tsm/base/etc/device-correspondence.csv);
while ($in)
{
#print;
chomp;
my ($tsm,$sn) = split(/,/);
$drives-{$sn} = $tsm;
}
# print Dumper($drives);
$in-open(/usr/sbin/lscfg | grep rmt |);
while ($in)
{
my ($junk,$rmt,@junk) = split;
#print $rmt,\n;
my (@tape) = `/usr/sbin/lscfg -vl $rmt`;
my ($snline) = grep{/Serial Number\.+(\d+)$/} @tape;
#print $snline;
my ($sn) = $snline =~ /Serial Number\.+(\d+)$/;
my $drive = $drives-{$sn};
$verbose print $rmt:\tNew entry for '$drive'\n;
$out-{$sn} = new FileHandle(./serial-$sn-$drive) unless
defined($out-{$sn});
$out-{$sn}-print(@tape);
$out-{$sn}-print( `/usr/sbin/lsdev -l $rmt` );
}
#!/usr/local/bin/perl
use FileHandle;
use Data::Dumper;
use Getopt::Long;
my $verbose =1;
my $in = new FileHandle;
my $drives = {};
my $rmts = {};
my $define = undef;
my $server = [];
my @servers;
my $script = 0;
my $libr=3592lib;
$result = GetOptions
(
verbose = \$verbose,
server=s = $server,
define! = \$define,
script!= \$script,
);
if ($#{$server} -1 ) {@servers = @{$server} ;} else {@servers = ( CTRL ) }
my $out = {};
$in-open(/var/tsm/base/etc/device-correspondence.csv);
while ($in)
{
#print;
chomp;
my ($tsm,$sn,$lib) = split(/,/);
$drives-{$sn} = {
'TSM' = $tsm,
'LIB' = $lib,
};
}
$in-close; $in-open(/usr/sbin/lsdev -Cc tape|);
while ($in)
{
chomp;
#print;
my ($rmt,$stat,$loc,@crap) = split(/\s+/);
my @junk = split(/-/,$loc);
$rmts-{$rmt} = { pri = pop(@junk) };
}
# print Dumper($rmts);
foreach $drive (keys %$drives)
{
my @lines = `/usr/local/bin/grep rmt ./serial-$drive-*`;
my $pri = ;
foreach $line (@lines)
{
my ($crap,$dev,@crap) = split(/\s+/,$line);
my $p = $rmts-{$dev}-{pri};
if ($p eq PRI)
{
if ($pri ne ) { die Multiple primay devices for '$drive' ?? }
$pri = $dev;
}
}
if ($pri eq ) { die No primary device for '$drive' ?? }
#print $drive: $pri \n;
$drives-{$drive}-{pri} = $pri;
}
# print Dumper($drives);
if (0)
{
foreach $drive ( keys %$drives)
{
Re: Re: Drive and Path Definition
I'm with Allen. In 10 years of TSM work with both SCSI and FC Libraries and drives, I've never had to restart TSM on AIX to add drives and paths one by one. I also don't mess with TSM Devices since TSM 4.2 on AIX either. I just run cfgmgr, then define the drives and paths. I have used an Exabyte Library (well, that's using the term used loosely, it stunk), and several 3584's. Something isn't getting adjusted right in the TSM database, or it's having a hard time picking up the device serial number and/or WWN (at least that's what I would suspect). See Ya' Howard Coles Jr. John 3:16! -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen S. Rout Sent: Thursday, January 19, 2012 8:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Re: Drive and Path Definition On 01/18/2012 06:28 PM, David Bronder wrote: Richard Rhodes wrote: In the past we've never had to restart TSM to add a new drive. As long as the drive was discovered and available at the AIX layer, we could define the new drive. Has this changed with v6.2.x? Seriously? Is this behavior due to changes in TSM 6.x, or has it always been this way for SCSI-style (smcX) libraries? I've never had this issue with my 3494 library and any TSM version from ADSM 2.1 through TSM 5.5. Me too; 3494 and 3584 both, I've not needed to restart TSM to begin accessing new devices. - Allen S. Rout DISCLAIMER: This communication, along with any documents, files or attachments, is intended only for the use of the addressee and may contain legally privileged and confidential information. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of any information contained in or attached to this communication is strictly prohibited. If you have received this message in error, please notify the sender immediately and destroy the original communication and its attachments without reading, printing or saving in any manner. Please consider the environment before printing this e-mail.
Re: EXPORT command help
If you want ALL data that is stored by the target node use the option filedata=all, allactive would only export the latest versions of each file the node has in storage. If you want to re-run the export I would add the merge=yes option which should only update the data on the target TSM server with any data that was not included in the first process. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 9:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help Thanks Rick, What happen was this node was exported from one TSM server to another and 1 file apparently did go over but wait can't afford to lose 1 file from this node so I just need to get that 1 file. Will the filedata=allactive command just get that 1 file only? TSMSERVER A BOVSRV3CC Bkup \\Bovsrv3- 3 LTO64POOL409,136 455,041.4 453,092.4 \d$ 1 1 TSMSERVER B BOVSRV3CC Bkup \\Bovsrv3- 3 LTO3POOL 409,135 452,932.4 452,920.9 \d$ 4 1 Thanks again -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, January 19, 2012 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT command help You could use filedata=allactive which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: EXPORT command help
Thanks Rick, I think I will try the merge=yes command (see below) export node Bovsrv3cc filedata=all toserver=tsmcore4 merge=yes Hopefully It will only get the 1 file that is missing. Fyi- the Node on the source server actually hasn't been backing up for awhile but we need to move the data to another TSMserver and then do a generated backup set on it to keep the data. Thanks again -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, January 19, 2012 9:47 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT command help If you want ALL data that is stored by the target node use the option filedata=all, allactive would only export the latest versions of each file the node has in storage. If you want to re-run the export I would add the merge=yes option which should only update the data on the target TSM server with any data that was not included in the first process. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 9:09 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help Thanks Rick, What happen was this node was exported from one TSM server to another and 1 file apparently did go over but wait can't afford to lose 1 file from this node so I just need to get that 1 file. Will the filedata=allactive command just get that 1 file only? TSMSERVER A BOVSRV3CC Bkup \\Bovsrv3- 3 LTO64POOL409,136 455,041.4 453,092.4 \d$ 1 1 TSMSERVER B BOVSRV3CC Bkup \\Bovsrv3- 3 LTO3POOL 409,135 452,932.4 452,920.9 \d$ 4 1 Thanks again -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Rick Adamson Sent: Thursday, January 19, 2012 8:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: EXPORT command help You could use filedata=allactive which would only export the active (most recent) versions of each file. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hughes, Timothy Sent: Thursday, January 19, 2012 8:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] EXPORT command help I believe I am missing something the command syntax is coming up invalid From: Hughes, Timothy Sent: Thursday, January 19, 2012 8:24 AM To: ADSM-L@VM.MARIST.EDU Subject: EXPORT command help Hi, I am trying to export only Newer files (should be only one) is this command correct? export node Bovsrv3cc filedata=all toserver=tsmcore4 -IFNewer Thanks
Re: Drive and Path Definition
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/19/2012 08:42:26 AM: ... Our libraries are 3584 scsi libraries, which are different animals from 3494 libraries. Sorry, I should have said that. Any time we have changed the physical library it has required us to bounce TSM so the new slots EA and/or drive EA are available to TSM. In our case, that's our library manager tsm instance. We are still on v5.5, but I've seen nothing that would indicate that v6+ is any different. Rick - Have you tried Audit Library as part of the change procedure? It should perform a reconciliation with the reality of the library, using the same functionality that occurs when TSM restarts and checks the library. Richard Sims This is interesting discussion. Here's my story . . . Our 3584 libraries started out witn 3 frames. They are now at 8 frames. Sometimes a slot-only frame was added, other times a frame with slots+drives. The first time we added a frame I took the drives offline while IBM worked, but didn't bounce the library manager. I loaded up the new frame with new tapes assigned to the Logical Lib. Running checkin would not see the new tapes. I also brought the new drives in the new frame into AIX, created TSM drives, but failed on the paths. Now, it was a long time ago and I don't exactly remember, but I believe I did an audit (but maybe I didn't). I also didn't know about show slots and show libr cmds.I opened a case with support and was told I needed to bounce the library manager. That worked, all was good. Since then after making any physical change I bounce the library manager. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: Drive and Path Definition
The only other option to restarting the library manager is removing and redefining all drives, library and paths. This would technically leave the TSM server up and would still reprobe the library. The Audit libr command never worked for me on a scsi library for these updates. Regards, Shawn Shawn Drew Internet rrho...@firstenergycorp.com Sent by: ADSM-L@VM.MARIST.EDU 01/19/2012 09:57 AM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Drive and Path Definition ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/19/2012 08:42:26 AM: ... Our libraries are 3584 scsi libraries, which are different animals from 3494 libraries. Sorry, I should have said that. Any time we have changed the physical library it has required us to bounce TSM so the new slots EA and/or drive EA are available to TSM. In our case, that's our library manager tsm instance. We are still on v5.5, but I've seen nothing that would indicate that v6+ is any different. Rick - Have you tried Audit Library as part of the change procedure? It should perform a reconciliation with the reality of the library, using the same functionality that occurs when TSM restarts and checks the library. Richard Sims This is interesting discussion. Here's my story . . . Our 3584 libraries started out witn 3 frames. They are now at 8 frames. Sometimes a slot-only frame was added, other times a frame with slots+drives. The first time we added a frame I took the drives offline while IBM worked, but didn't bounce the library manager. I loaded up the new frame with new tapes assigned to the Logical Lib. Running checkin would not see the new tapes. I also brought the new drives in the new frame into AIX, created TSM drives, but failed on the paths. Now, it was a long time ago and I don't exactly remember, but I believe I did an audit (but maybe I didn't). I also didn't know about show slots and show libr cmds.I opened a case with support and was told I needed to bounce the library manager. That worked, all was good. Since then after making any physical change I bounce the library manager. Rick - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete 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.
Re: LTO4 Tape Volumes with diferent Estimated Capacity
Tiago, Generally speaking hardware compression (tape drive) will always yield better results than software based compression. I would only use the client compression when bandwidth issues come into play, like remote offices with limited WAN bandwidth or a slow congested LAN segment. In these cases compressing at the client would reduce the data that has to traverse the network. ~Rick -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Botelho, Tiago (External) Sent: Thursday, January 19, 2012 4:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity Hello all Thank you for your all answers. Regarding to your experience what is more efficiency regarding to tape usage capacity (increase tape amount of data stored)? Compression on client or compression on Drive(HW)? Cumprimentos / Best regards Tiago Botelho -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Botelho, Tiago (External) Sent: quarta-feira, 18 de Janeiro de 2012 15:27 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] LTO4 Tape Volumes with diferent Estimated Capacity Hello I have several tape volumes (LTO4) with different Estimated Capacity. What can cause this situation? Ex: A00035L4 WIN_SRV_T TS3310 629.5 G 95.4 Full A00039L4 WIN_SRV_T TS3310 1.1 T 98.2 Full A00101L4 WIN_SRV_T TS3310 884.8 G 84.4 Full A00113L4 WIN_SRV_T TS3310 1.0 T 93.7 Full A00118L4 WIN_SRV_T TS3310 1.0 T 73.6 Full A00128L4 WIN_SRV_T TS3310 1.0 T 99.2 Full A00129L4 WIN_SRV_T TS3310 969.1 G 93.7 Full A00133L4 WIN_SRV_T TS3310 934.8 G 96.1 Full All tapes and Drives are LTO4, TSM Server 553 for AIX. The devc are configured as: Device Class Name: TS3310 Device Access Strategy: Sequential Storage Pool Count: 16 Device Type: LTO Format: ULTRIUM4C Est/Max Capacity (MB): Mount Limit: DRIVES Mount Wait (min): 60 Mount Retention (min): 60 Label Prefix: ADSM Library: TS3310 Directory: Server Name: Retry Period: Retry Interval: Shared: High-level Address: Minimum Capacity: WORM: No Drive Encryption: Off Scaled Capacity: Last Update by (administrator): ADM Last Update Date/Time: 07/27/09 17:32:05 Cumprimentos / Best regards Tiago Botelho
Re: Low level tape drives for TSM
Thank you very much for information. You are right, IBM proposed us 3592 libraries as a solution, but we found this proposal too expensive for daily amount less than 1TB. I will check ts1120 as an alternative solution. Maybe it will be more suitable for us. From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] On Behalf Of Lee, Gary [g...@bsu.edu] Sent: Thursday, January 19, 2012 4:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Low level tape drives for TSM Sounds like you are looking for something in the 3592 class. We are using ts1120 drives. 300 gB uncompressed, fibrechannel connection 2 gb, tsm 5 and 6 support them, usable in a manual library. Don't know about the AIX questions, but don't know why they wouldn't be supported. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Grigori Solonovitch Sent: Thursday, January 19, 2012 5:23 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Low level tape drives for TSM Hello Everybody, We are using disk pools at Head Office and Disaster Site connected by fiber optics links (DS8100 online mirroring and 1GB Ethernet). We are using SCSI tape drives 3590 only for out-of-country copies with daily amount less than 1TB. We need to replace 3590 drives by something newer. We are looking for tape drives: 1) supported by TSM 5.5 and 6.X; 2) supported by AIX on Power6 and Power7 logical partitions; 3) connected via fiber optics switch (at least 2Gb/s) or via network (at least 1Gb/s); 4) with volume capacity 128GB or more (not compressed); 5) just drive or manual library like 3590. I will deeply appreciate any suggestions or links to documents. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Ahli United Bank Kuwait www.ahliunited.com.kw Please consider the environment before printing this E-mail CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email. CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
Re: Offsite copypool question
-Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Xav Paice - Paul_Dudley pdud...@anl.com.au wrote: On the SQL servers I have included the SQL database folder in the Exclude-Include configuration of the normal TSM backup setup. (these databases are backed up using TDP for SQL) As well as that, SQL is running all the time so the normal TSM backup client would never be able to get a lock on these database files. I already have a backup of these SQL databases in the SQLDB_LTO4 storage pool and therefore a copy is in the SQLDB_COPYPOOL storage pool so I don't need another copy in BKPLTO4POOL and COPYPOOL_LTO3 Any idea how I can work out why a backup copy of these SQL database backups are ending up in BKPLTO4POOL and stop this from happening? It's likely you're getting the files captured by the client even with the db open. Try to exclude them in the inclexcl, or associate them with the right management class. 'Query occupancy' for the TDP node should list everything in the right storage pool. Take a look in the BA client gui and hunt down the database files - that will tell you if they are being stored. If you can see them as individual files, and you've not made a cold backup of the database, then that's the issue. You can delete them from the ba client if you wish and are sure they're not wanted. I checked the BA GUI and the database files are not being backed up. However when I ran q occupancy I can see that these node names for these SQL database backups are in the wrong storage pool - BKPLTO4POOL. When I query these node names the platform is TDP MSSQL Win32, and the Optionset is SQL_SERVERS. Note that it is not all of the SQL servers that are this way, some show the correct Storage Pool via the q occupancy command. How can I change the SQL Servers that are incorrect to be backed up into the correct storage pool? Thanks Paul ANL - Regional Carrier of the Year 2011 - Containerisation International ANL DISCLAIMER This e-mail and any file attached is confidential, and intended solely to the named add ressees. Any unauthorised dissemination or use is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by return e-mail from your s ystem. Please do not copy, use or make reference to it for any purpose, or disclose its contents to any person.
