Re: question about command line backup syntax
Hello Andy Thank You for the information. I will use your suggestion. Regards Michael Devenney -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Andrew Raibeck Sent: November-04-15 11:25 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] question about command line backup syntax Hi Michael, You can only use wildcard characters on the file name portion of a backup specification; not directories. One approach, as others have mentioned, is to use INCLUDE/EXCLUDE statements to handle this. For example, you could add these to the dsm.opt file: include D:\Folders\...\* exclude D:\Folders\* exclude.dir D:\Folders\[$0-9b-z]* and then back up like this: dsmc incremental D:\Folders\ -subdir=yes The exclude.dir statement will prevent traversal and backup of all directories immediately below D:\Folders with names that begin wtih '$', the digits 0 - 9, and the letters b - z. If this directory happens to have subdirectories that begin with characters I did not mention, then you can just add them to the character class between the '[' and ']'. The exclude statement for D:\Folders\* will prevent backup of file objects that live directly in the D:\Folders directory, e.g., D:\Folders \somefile.txt. The include statement will process all files and directories in D:\Folders except for the ones excluded as above. Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2015-10-29 09:03:58: > From: Michael Devenney > To: ADSM-L@VM.MARIST.EDU > Date: 2015-10-29 09:04 > Subject: question about command line backup syntax Sent by: "ADSM: > Dist Stor Manager" > > Hello > > I have a Windows server with the following file structure D:\Folders\ > > In this folder are A1folder, A2folder, A3folder, B1folder, C1folder > > I am trying to backup only the folders starting with the letter "A" > and their subfolders using the command line backup dsmc backup > d:\folders\A* -subdirs=yes > > This is not backing up the folders starting with "A". > > Can someone help with the correct syntax. > > Thanks > > Michael Devenney CNE, MCTS, A+, Server+ Service Administrator River > East Transcona School Division > > > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient(s), and may > contain confidential and privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply e-mail and destroy all copies of the original message. > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s), and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
Re: question about command line backup syntax
Hi Michael, You can only use wildcard characters on the file name portion of a backup specification; not directories. One approach, as others have mentioned, is to use INCLUDE/EXCLUDE statements to handle this. For example, you could add these to the dsm.opt file: include D:\Folders\...\* exclude D:\Folders\* exclude.dir D:\Folders\[$0-9b-z]* and then back up like this: dsmc incremental D:\Folders\ -subdir=yes The exclude.dir statement will prevent traversal and backup of all directories immediately below D:\Folders with names that begin wtih '$', the digits 0 - 9, and the letters b - z. If this directory happens to have subdirectories that begin with characters I did not mention, then you can just add them to the character class between the '[' and ']'. The exclude statement for D:\Folders\* will prevent backup of file objects that live directly in the D:\Folders directory, e.g., D:\Folders \somefile.txt. The include statement will process all files and directories in D:\Folders except for the ones excluded as above. Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: http://www.ibm.com/support/knowledgecenter/SSGSG7/welcome Product Wiki: https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%20Storage%20Manager "ADSM: Dist Stor Manager" wrote on 2015-10-29 09:03:58: > From: Michael Devenney > To: ADSM-L@VM.MARIST.EDU > Date: 2015-10-29 09:04 > Subject: question about command line backup syntax > Sent by: "ADSM: Dist Stor Manager" > > Hello > > I have a Windows server with the following file structure D:\Folders\ > > In this folder are A1folder, A2folder, A3folder, B1folder, C1folder > > I am trying to backup only the folders starting with the letter "A" > and their subfolders using the command line backup > dsmc backup d:\folders\A* -subdirs=yes > > This is not backing up the folders starting with "A". > > Can someone help with the correct syntax. > > Thanks > > Michael Devenney CNE, MCTS, A+, Server+ > Service Administrator > River East Transcona School Division > > > CONFIDENTIALITY NOTICE: This e-mail message, including any > attachments, is for the sole use of the intended recipient(s), and > may contain confidential and privileged information. Any > unauthorized review, use, disclosure or distribution is prohibited. > If you are not the intended recipient, please contact the sender by > reply e-mail and destroy all copies of the original message. >
Get rid of old encryption key on tapes.
Need a lot of help with this one. We have changed from using IBM Encryption Key Management to IBM Security Key Lifecycle Manager for encrypting tapes in our TS3310 library using TSM 7.1.1 on a Linux system. The problem is all the tapes have been encrypted by the old EKM and now we are using SKLM. TSM rejects the tape because it already has a encryption key from EKM. I don't need the data that is on any of the tapes I just need to be able to use them with SKLM. I have used the LABLE command with the OVERWRITE option and that seems to work on some but not many. How can I get rid of the old EKM encryption key on each tape so it will get a new encryption key from SKLM? Thanks for any help this is a doozy 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.
Re: Activate SKLM on existing TS3500 partition
Hello Kevin, Thanks for your answer. It entered in my spambox, so it took a while before I noticed it :-) So if I understand well, we can safely activate encryption on our existing library partition. But do we need to use "relabel scratch" on the library definition in TSM? Or does the robot recognise the use of normal scratch tapes without relabel as well? Thanks, Maurice 2015-10-21 22:34 GMT+02:00 Kevin Boatright : > Once you enable encryption on the tape library, it will encrypt the data > as it mounts the scratch tapes. > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Plair, Ricky > Sent: Wednesday, October 21, 2015 3:45 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Activate SKLM on existing TS3500 partition > > Hey Maurice, > > Did anyone reply to your email? > > We are performing about the same thing. We have the SKLM server built and > we are migrating from EKM. > > Rick > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > Maurice van 't Loo > Sent: Wednesday, October 14, 2015 8:29 AM > To: ADSM-L@VM.MARIST.EDU > Subject: [ADSM-L] Activate SKLM on existing TS3500 partition > > Friends, > > We currently have TSM 7.1.1.3 with TS3500's and LTO6 drives in use. > SLKM server is build and tested successfully. > > Now we want to activate tape encryption. > > Can we just activate it on the library partition that is already in use? > Will it start using encryption when a new scratch tape is used? Or when we > relabel a volumes? (relabel scratch) > > Thanks, > Maurice van 't Loo > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > _ 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 electronic mail message contains information which may be > confidential, privileged and protected from further disclosure. Such > information relates to and is used for all purposes outlined in the > statutes below, including Peer Review, Performance Improvement, Quality > Assurance and Claims Management and Handling functions and/or > Attorney-Client Communications. It is being produced within the scope of > all Georgia and Federal laws governing record confidentiality, including > (but not limited to) Official Code of Georgia Annotated Sections 31-7-15; > 31-7-130; 31-7-131; 31-7-132; 31-7-133; 31-7-140; 31-7-143. If you are not > the intended recipient, please be aware that any disclosure, photocopying, > distribution or use of the contents of the received information is > prohibited. If you have received this e-mail in error, please reply to the > sender immediately and permanently delete this message and all copies of > it. Thank you. Communication of electronic protected health information > (ePHI) is protected under the Health Insurance Portability and > Accountability Act (HIPAA) Act of 1996. Electronic mail (e-mail) > communication is not encrypted or secure. The HIPAA Security Rule allows > for patients to initiate communication of personal health information over > this medium and for providers to respond accordingly with the understanding > that privacy of communication is not guaranteed." >
