Re: TDPO and different Management Class

Muthu, As the other guys have pointed out, there should be a single management class with the well-known set-in-stone backup copygroup retention policies as a destination for DP for Oracle backups. Take a look in the IBM Redbook Backing Up Oracle using Tivoli Storage Management

Active Directories on 2003 SP1

Hi, I have been asked to backup a Active Directories Domain Controller, 2003 Server Standard Edition - Sp1. ( TSM Backup client 5.3.0.0) Are there known issues regarding restoring Active Directories with 2003 SP1 ? Do we need upgrade to SP2 ? (TSM Server fow Windows 5.2.2 on 2003

Re: ASR backup failed

Hi Richard! Thank you very much for your reply! I deleted c:\adsm.sys, but the error remains. Even stranger is that when I run a backup ASR through the command line interface manually, it finishes without errors! The scheduled backup during the next evening fails again... Guess I will have to

Re: ASR backup failed

Hi Adam! Thank you very much for your reply! I checked the disk through Disk Management, everything looks good here... Thanks again! Kindest regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: Crosskey, Adam - Resources, ICT Services [mailto:[EMAIL PROTECTED] Sent:

Re: ASR backup failed

Please share with the list if you find the solution for this. I've also seen this problem with one Win2K3 server. Played around with it for several hours before giving up. I never did open up a PMR with IBM because it wasn't all that important at the time. __ John

AW: [ADSM-L] ASR backup failed

Please download the most current version of the 5.3 message manual. My edition (october 2005) shows the following explanation: ANS1468E Backing up Automated System Recovery (ASR) files failed. No files will be backed up. Explanation: An error occurred while backing up the files needed for

Re: AW: [ADSM-L] ASR backup failed

On Dec 16, 2005, at 11:39 AM, Thomas Rupp wrote: Please download the most current version of the 5.3 message manual. ... Hi, Thomas - Good point. Unfortunately, IBM has royally confused the customer base with really poor, confusing identification of the manuals... The seeming 5.3 version of

AW: [ADSM-L] AW: [ADSM-L] ASR backup failed

Hi Richard, I second that. I recently was looking for a message number, I couldn't find it in my downloaded edition so I re-downloaded the manual and voilà. I don't know why I did it - it's simply intuition when beeing in IT for more than 25 years ;-) Thomas -Ursprüngliche Nachricht-

lto2's and TSM 5.3

I'd like to ask those who are using the LTO2 drives with TSM 5.3 a few questions and some advice. I'm in the process of building a system to replace the one I have. It will run AIX5.3 and TSM 5.3. My plan is to keep the old system around and let the data expire off but lets talk about the new

REMOVAL OF TDP BACKUPS

Dear All, I have an old 4.1 TSM Server that is backing up Notes TDP databases and logs. There are currently about 15 weeks worth of backups on this server, as we have moved the Notes backups to a new server TDP is no longer telling TSM when the backups can be removed. This means

Re: lto2's and TSM 5.3

Gill, It is always hard to give general 'specific' advise but here I go. Concerning the collocation. There is a new feature in TSM 5.3 called a c'collocation group'. So you can define a set of nodes that will use the same tapes. By making a trade off between the number of servers and the

Re: lto2's and TSM 5.3

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 12/16/2005 11:07:42 AM: I'd like to ask those who are using the LTO2 drives with TSM 5.3 a few questions and some advice. I'm in the process of building a system to replace the one I have. It will run AIX5.3 and TSM 5.3. My plan is to keep

Re: REMOVAL OF TDP BACKUPS

Here is the lazy man's method. Rename the current node in TSM to something else. Create a new node for TDP notes. When you have enough backups to cover your retention period under your new notes node, delete the old notes file spaces and node. From: ADSM: Dist