Re: [Veritas-bu] KMS Setup and Restore setup Issue.
I don’t understand your question. If you want to restore an encrypted tape you need to have the exact same keys as it was made with. Say my prod site serverA is backed up encrypted. I can restore it from my prod site to serverB, because it is the same master server, which means it has the key to decrypt the tape. I also have a DR site. When I made my kms database, I made it exactly the same on my DR site master. (Easier way is to just copy the KMS database (directory) from my prod site to my DR site. Now my DR site has the same keys so it is also able to restore from the same tape to any server at my DR site. If you have more than one master, suggest you test backing up on one and restoring from the other. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Abhishek Dhingra1 Sent: Tuesday, September 07, 2010 9:16 AM To: Harpreet SINGH Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] KMS Setup and Restore setup Issue. Hi Harpreet I have done backup and restore testing using KMS encryption. I have a question here, is the customer want to restore the data on a different infrastructure or on a same infrastructure. Rgds A D Email : abhishek.dhin...@in.ibm.com Harpreet SINGH Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 09/01/2010 04:12 AM To "VERITAS-BU@MAILMAN.ENG.AUBURN.EDU" cc Subject [Veritas-bu] KMS Setup and Restore setup Issue. Hi, We are on Netbackup 7.0 and using KMS to encrypt the tape’s before we send them offsite. I have got a new requirement, where one of the department want to do there server’s backup via Netbackup Client with encryption option. But they don’t want to allow Veritas Netbackup Administrator to restore there backups. i.e. during the restore they will (want) enter the encryption key for restore. Please advise how I can achieve this. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana =-=-=-=-=-=-=-=-=-=-=-=-=- Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] KMS Setup and Restore setup Issue.
Hi Harpreet I have done backup and restore testing using KMS encryption. I have a question here, is the customer want to restore the data on a different infrastructure or on a same infrastructure. Rgds A D Email : abhishek.dhin...@in.ibm.com Harpreet SINGH Sent by: veritas-bu-boun...@mailman.eng.auburn.edu 09/01/2010 04:12 AM To "VERITAS-BU@MAILMAN.ENG.AUBURN.EDU" cc Subject [Veritas-bu] KMS Setup and Restore setup Issue. Hi, We are on Netbackup 7.0 and using KMS to encrypt the tape’s before we send them offsite. I have got a new requirement, where one of the department want to do there server’s backup via Netbackup Client with encryption option. But they don’t want to allow Veritas Netbackup Administrator to restore there backups. i.e. during the restore they will (want) enter the encryption key for restore. Please advise how I can achieve this. With Warm Regards =-=-=-=-=-=-=-=-=-=-=-=-=- Harpreet Singh Chana =-=-=-=-=-=-=-=-=-=-=-=-=- Please do not print this email unless it is absolutely necessary. Notice The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying or distribution of the message, or any action taken by you in reliance on it, is prohibited and may be unlawful. If you have received this message in error, please delete it and contact the sender immediately. Thank you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Understanding DSSU
What you are describing is the same behaviour I see across my environments. Not aware of any functional modification that 'fixes' this, either... Once NB assigns a resource to a job, it will wait on that resources availability. It does this for DSSUs, Tape heads, everything. i.e. as you are seeing, if a job is running against one DSSU, and that DSSU goes full during the job, it will wait on cleanup processes, until timing out. No spillover. Same with tape heads, if you have a job running against a tape head, and that tape goes full, and the only other available media is running jobs in another head, that job will never switch heads. I think someone mentioned disk pools, which would do what you want (configured through volume manager, or using nbdevconfig at CLI) - but i'm assuming you are using Basic Disk units currently, and Disk Pools are Advanced Disk (which has an additional license cost associated). Of course, if you switch to advanced disk, it means you can use SLPs instead of DSSUs as well... Additional/advanced functionality - theres always a cost :P Cheers, Nic -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders Sent: 03 September 2010 19:32 To: rusty.ma...@sungard.com Cc: Sanders, Nate; Veritas List; veritas-bu-boun...@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Understanding DSSU After checking all 6 DSSUs only one contained 6 images that were expired. This for sure does not explain why we continue seeing failed jobs, especially tiny failed jobs. So is my understanding of Storage Groups not correct? When one unit says its full, shouldn't the job proceed to the next unit in the group? This is certainly not the behavior we are seeing based on logs and errors. On 09/02/2010 02:43 PM, rusty.ma...@sungard.com wrote: > I first did an ls -l and grabbed the image ID of the images I thought were > too old and should have been destaged and expired off of the DSSU. > I then took those images and ran them through bpimagelist to see if they had > a copy on tape (or if it should have been expired). > Those that had a copy on tape or should have been expired were bpexpdate'd. > > If you aren't familiar with these commands, read up on them in the commands > guide and do some practicing with them. Especially with bpexpdate. > > Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪ SunGard Availability > Services ▪ 757 N. Eldridge Suite 200, Houston TX 77079 ▪ 281-584-4693 > Keeping People and Information Connected® ▪ http://availability.sungard.com/ > P Think before you print > CONFIDENTIALITY: This e-mail (including any attachments) may contain > confidential, proprietary and privileged information, and unauthorized > disclosure or use is prohibited. If you received this e-mail in error, > please notify the sender and delete this e-mail from your system. The information contained in this e-mail and its attachments is confidential. It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
