Backup Offsite

2014-03-11 Thread Kiran
Hi All, Is there a way to make the backup tapes offsite without copy pool tapes in TSM My daily backup window is around 1TB. So making copypool with the exisitng tape library is not possible. Disclaimer: http://www.dqentertainment.com/e-mail_disclaimer.html

Re: Backup Offsite

2014-03-11 Thread Grigori Solonovitch
No way for real tapes. You can use Data Domain VTL replication for primary pools, by the way. Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of

Moving Oracle and DB2 nodes between servers.

2014-03-11 Thread Steven Harris
Hi All I'm planning a slow, node-by-node migration from V5 to V6 for one of my customers. The database is too big to do anything else. For most types of node, this is not an issue, Move the node to the new server, wait for most of the data to expire and export/import the remainder (there is

Re: Moving Oracle and DB2 nodes between servers.

2014-03-11 Thread Rick Adamson
Have you considered performing an export node to the new version 6 TSM server. While the export is running disable the client's access so RMAN cannot purge the old data from its catalog. Once the export is done re-enable the client's access -Rick Adamson 904.783.5264 -Original Message-

Re: Moving Oracle and DB2 nodes between servers.

2014-03-11 Thread Loon, EJ van (SPLXM) - KLM
Hi Steve! This is exactly the reason why we decided for the hybrid migration scenario after all. It's a big bang method, but it saved a lot of people an enormous amount of work... The only thing I do not agree with is what your DBA tell you about how RMAN works. RMAN by default knows nothing about

Re: Backup Offsite

2014-03-11 Thread Stefan Folkerts
Kiran, What do you mean with My daily backup window is around 1TB. So making copypool with the exisitng tape library is not possible. ? Do you mean that you don't have enough time, or are you lacking temporary storage capacity in the library, please elaborate a bit more on your situation.

Upgrading Linux 6.1 server to new hardware/OS/TSM server scenario

2014-03-11 Thread Zoltan Forray
I am doing the above with the following steps and want to make sure I haven't missed anything. I already went through this process on a test server, working out all the gotchas (file permissions/ownership/locations, etc). 1. Stop all activity/access on old server. 2. Backup old server DB

Exchange restore

2014-03-11 Thread Geoff Gill
I have a question sent to me about restoring an exchange db. Having no access to the clients or experience it's difficult to do anything except ask questions here. I don't have any client side or exchange info to pass on either. I can only tell you the server level is 6.2.2. they tell me they

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Zoltan Forray
With the lack of replies, I am guessing I can't recover this server from what is left behind. I do have an old DB backups but for what this server does, it isn't worth bothering. I can rebuild it faster. I do have additional questions that somebody might have an answer to. 1. Any reason NOT

Re: Exchange restore

2014-03-11 Thread Del Hoobler
Hi Geoff, This looks like an Exchange environment issue. Google shows a few possibilities, for example:

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Chavdar Cholev
Zoltan, you can check db2diag log fir more info, I would start from there. I am nor sure about TSM6.1 to TSM7.1, my main concern here is different DB2 versions. If you thing to rebuild TSM 6.1 on new HW by mounting LUNs from old crashed TSM it may work, and after that to upgrade to TSM 7.1 I

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Zoltan Forray
The db2diag.log file was lost along with the root and /home partition. All I have is ghost messages from the activity log (TSMManager console saves a lot of the messages in its buffers) On Tue, Mar 11, 2014 at 12:21 PM, Chavdar Cholev chavdar.cho...@gmail.comwrote: Zoltan, if not you can

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Thomas Denier
-Zoltan Forray wrote: - 2. When doing postmortem on this failed server (still waiting for results from hardware diagnostics - my OS guy is head to the offsite location to check on the results and to start reinstalling the OS), I notice this message from my monitoring system: 3/6/2014

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Skylar Thompson
Encapsulating the term in quotes (-980) ought to do the trick. Looks like -980 is associated with a disk error, which unfortunately doesn't help Zoltan too much at this point... http://publib.boulder.ibm.com/infocenter/db2luw/v8/index.jsp?topic=/com.ibm.db2.udb.doc/core/rsql0900.htm On Tue, Mar

Tape Drive compatibility

2014-03-11 Thread George Huebschman
My question is: Is there a way to determine what tapes in a 3584 library have been written to by E05 or E06 3592 tape drives? Because: I have a library with two generations of drives. I discovered this morning that my DR Tape Library had no scratch tapes. I expected around 200. I found that I

Re: Tape Drive compatibility

2014-03-11 Thread Gee, Norman
From the TS 3500 web GUI, expand cartridges, click on Data Cartridges, click on mount history(.csv). This will list the last 100 mounts and on which drive. With ALMS, set up 2 different logical libraries. One for E05 and the other for E06. -Original Message- From: ADSM: Dist Stor

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Zoltan Forray
Thanks for finding that but, as you said, it doesn't help much. The disk filled to 100% due to DB2 taking dumps but that doesn't tell me what caused the dumping in the first place. We are still running Dell full diagnostics (started yesterday afternoon and was at 78% as of 2pm EDT). My OS guy

Re: Recovering Linux TSM server from partial filesystem failure

2014-03-11 Thread Skylar Thompson
Since you mentioned Dell, one thing to check would be PERC and hard drive firmware levels. There have been a number of updates to both over the past few years concerning silent data corruption under a variety of conditions. On Tue, Mar 11, 2014 at 03:07:24PM -0400, Zoltan Forray wrote: Thanks