TDP for Exchange error code

I use 7.1. With /PREFERDAGPASSIVE set it correctly skips the mailboxes on the active node but the return code is 1829. Could this safely be ignored that is if the backup command has RC=1829 I can force the script to return with RC=0? Another thing, should /PREFERDAGPASSIVE not be used when doing

Re: TDP for Exchange error code

Hello Hans Chr., RC=1829 means nothing to back up... so yes, in this case, the backup should be performed using one of the passive copies, assuming you have backups running on the servers with the passive copies. The incremental backup can be done from the active copy or any passive copy. You

V7 Stable?

We are thinking of upgrading to 7.1 from 6.2. I have not seen much chatter about problems. Is 7.1 reliable? I did not see any patches, are any out? AIX and Windows. Andy Huebner

Re: V7 Stable?

Don't, just don't do 7.1 just yet. Op 3 apr. 2014 15:09 schreef Huebner, Andy andy.hueb...@novartis.com: We are thinking of upgrading to 7.1 from 6.2. I have not seen much chatter about problems. Is 7.1 reliable? I did not see any patches, are any out? AIX and Windows. Andy Huebner

Re: V7 Stable?

On Thu, Apr 3, 2014 at 12:01 PM, Karel Bos tsm@gmail.com wrote: Don't, just don't do 7.1 just yet. Op 3 apr. 2014 15:09 schreef Huebner, Andy andy.hueb...@novartis.com: Well THAT'S a cliff-hanger -- could you describe your experiences with 7.1 and why we shouldn't? Mike

Re: V7 Stable?

I just did an update to 7.1 from 6.2 on a small Windows-based TSM server. No drama or issues here. Matthew McGeary Technical Specialist PotashCorp - Saskatoon 306.933.8921 From: Ryder, Michael S michael_s.ry...@roche.com To: ADSM-L@VM.MARIST.EDU Date: 04/03/2014 10:06 AM Subject:

SV: [ADSM-L] V7 Stable?

We have been running 7.1 for a while now, Windows-based. No issues at all. Operations center is nice too.. Dan -Ursprungligt meddelande- Från: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] För Matthew McGeary Skickat: den 3 april 2014 18:08 Till: ADSM-L@VM.MARIST.EDU Ämne: Re:

TSM 7.1 upgrade path(s) on Windows

Hello Folks: I'm preparing to upgrade our TSM 6.2.3 server to TSM 7.1 -- both are on Windows. It's a side-by-side upgrade, and if possible I'd like to leave the existing TSM 6.2.3 environment alone during the upgrade, so that I can easily halt the upgrade if I run into any problems. I've been

Re: TSM 7.1 upgrade path(s) on Windows

It's more easy install TSM V7.1 in new TSMserver , and then make the upgrade by the upgrading using tape. You will never touch the TSM server V6.x to do it, make a dbbackup to disk, copy files and then try to do the upgrade to TSM 7.x 2014-04-03 10:24 GMT-06:00 Ryder, Michael S

Re: TSM 7.1 upgrade path(s) on Windows

You're much better off to simply do a dr prepare and do the upgrade in-place. If the upgrade fails for whatever reason, reinstall 6.2.3 and do a db restore. Matthew McGeary Technical Specialist PotashCorp - Saskatoon 306.933.8921 From: Francisco Parrilla francisco.parri...@gmail.com To:

Re: TSM 7.1 upgrade path(s) on Windows

Francisco, I'm sorry for this naive question, but do you have a document you can point me at? I did not want to have to connect a tape library right from the start, but maybe that's the only option? Best regards, Mike, x7942 RMD IT Client Services On Thu, Apr 3, 2014 at 12:33 PM, Francisco

Re: TSM 7.1 upgrade path(s) on Windows

Certainly I never did , I hope do on few time. To do backup database, check this command set dbrecovery Check out this document: http://publib.boulder.ibm.com/infocenter/tsminfo/v6/topic/com.ibm.itsm.srv.upgrd.doc/b_srv_upgrade_guide.pdf 2014-04-03 10:55 GMT-06:00 Ryder, Michael S

Re: TSM 7.1 upgrade path(s) on Windows

What I would recommend instead, since you have hardware available: Install 6.2.3 on the new box, load your DB as a DR exercise. Then upgrade 7.1 over it. You can do that at your leisure, without impacting your production at all, or having to shut production down. If you have no problems, then

FW: [ADSM-L] TSM 7.1 upgrade path(s) on Windows

Oh, reminder: If you are using TIP, you should upgrade that first. You can do that now, as a 6.2 TSM can be managed by a 6.4/7.1 TIP. If you are using TSMManager, check on whether you need to upgrade that and can do it first. If you are using OC, you will have to upgrade that when you upgrade

Re: TSM 7.1 upgrade path(s) on Windows

Op 3 apr. 2014, om 19:40 heeft Francisco Parrilla francisco.parri...@gmail.com het volgende geschreven: Certainly I never did , I hope do on few time. To do backup database, check this command set dbrecovery Check out this document:

Re: V5-V6 conversion failed on INSERTDB with File system full

Added another 1TB file system to the database on the V6 server. Still failed, but for a different reason. Turns out I should have been at 6.3.4.300. The 6.3.4.0 insertdb code has a problem with volumes that are EMPTY, volumes with 0% utilization and Q CONTENT shows nothing. APAR IC97407: