Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Justin Derrick

Pages: 1 ... 115 116 117 118 119 [120] 121 122 123 124 125 ... 133
1786
Other / Re: Does OD support storing encryted documents?
« on: July 26, 2011, 08:55:58 AM »
Hi Curtis.

Just as a follow up, data in the cache and TSM is stored with a proprietary compression method.  Even an advanced user with non-CMOD-specific knowledge would have difficulty in successfully decompressing an entire stream of data.  (Heck, even I have trouble with it some days.)

Now, this is not truly secure, as there is no authentication or encryption, but you don't have to worry so much about the data being stored 'in the clear'.

The database information, however, IS stored in a format that could be parsed by an advanced-level adversary.  There is a database encryption product (formerly known as "Vormetric") that encrypts data at the filesystem level.

While application security is important, more straightforward methods at other levels (strict firewalls, restricting available network services, hardening the operating system) will work as far more effectiveness against hackers.

1787
MP Server / Re: Netbackup and CMOD Linux
« on: July 15, 2011, 10:38:33 AM »
As far as I know, TSM is the only supported archive solution for CMOD.  I haven't reviewed the manuals for CMOD 8.5 yet, but I don't remember it being in the announcement.

How exactly do you want to use NetBackup?

-JD.

1788
General / Re: IBM Certified Solution Expert CMOD multiplatform
« on: July 14, 2011, 07:04:33 AM »
I believe it's available worldwide.

If you get the chance to go to the IOD 2011 Conference, you'll have the opportunity to take many certification tests.

-JD.

1789
MP Server / Re: DB2 LOCKTIMEOUT
« on: July 11, 2011, 08:09:30 AM »
If you truly suspect a deadlock, then yes, reducing the LOCKTIMEOUT parameter in DB2 is the way to go.  But I'd investigate further, since the only reason I can think of that might cause a deadlock in CMOD is that a long-running load locked the table before a query was run -- but it's hard to imagine the insertion of rows into the database would take more than 10 minutes on your system.

1790
MP Server / Re: Inaccurate Time() parameter in Msg Num 87?
« on: July 11, 2011, 07:57:00 AM »
There doesn't appear to be any mention of this being fixed in any of the patches to 8.4.1.0, and there's no mention of the issue being fixed up to 8.5.0.2 -- so it's likely a bug. 

1791
MP Server / Re: Multiple TSM Servers
« on: July 10, 2011, 06:23:42 AM »
Hi Alessandro.

I don't have any customers that are using this feature in 8.5 -- but I'd imagine that a failure situation would be the same regardless of the number of TSM servers that are defined, especially if your Application Group is configured to migrate on load.  (Of course, the best alternative would be to migrate after loading if you were concerned about this situation.)

1792
MP Server / Re: DB2 LOCKTIMEOUT
« on: July 06, 2011, 07:42:06 AM »
Hey Tim.

The LOCKTIMEOUT parameter is for deadlocks -- where two operations are reliant on the other's results to complete, which is extremely unlikely with CMOD, since it's not really an OLTP system.

You can help prevent crazy queries from jamming up DB2 by changing the defaults (like the date range in the client), using query restrictions, adding indexes, or limiting the number of hits returned.

-JD.

1793
General / Re: IBM Certified Solution Expert CMOD multiplatform
« on: July 05, 2011, 06:56:10 AM »
There really isn't a study guide -- just make sure you review the manuals, and understand the relationships between Storage Sets/AG/App/Folder/Groups, etc.

I'm not sure if the certification exam has been updated for 8.5 yet, so I'd focus on 7.2.1.x and 8.4.x.

1794
Other / Re: TSM Reclaim Process
« on: June 17, 2011, 05:03:13 AM »
Hi Russell.

Reclamation of a tape only happens if it's more than a pre-configured amount empty.  Check the deviceclass and storagepool configuration.  Once a tape falls below this 'reclamation threshold' (usually 60%) the data gets moved onto an existing non-full tape.  Then freshly emptied tape is 'pending' for re-use, which is generally 30 days.

-JD.

1795
General / Re: RSS Feed Function Add to forum
« on: June 15, 2011, 05:26:58 AM »
Hi.

I simply bookmark the "Show unread posts since your last visit", and load that up every morning with a dozen or so other websites I check every day.

ODUG didn't write the software that runs the forum, so our ability to add features is limited.

Hope this helps!

1796
MP Server / Re: Help with migrating data to a new server CMOD
« on: May 19, 2011, 04:44:39 AM »
Yes, if you're cache only, then skip the TSM steps.

And unless you want to consolidate the cache filesystems, you'll want to create identical filesystems to your existing configuration.

Many customers I've worked with in the past want to do things like combine cache filesystems, or change database ownerships -- that's the tricky part, but it's a great way to kill two birds with one stone.

-JD.

1797
MP Server / Re: Help with migrating data to a new server CMOD
« on: May 18, 2011, 04:52:25 AM »
Hi Jose.

It's tricky, but it's possible to 'transplant' entire CMOD servers across hardware (even across platforms, but you didn't ask about that).

Without giving away too many of my "secrets", the steps I follow are this:

 - Install CMOD at the software levels you want to be at on the new hardware.
 - Duplicate the cache filesystem onto the new system.
 - Backup & restore your (DB2?) database data.
 - Backup & restore your TSM database data.
 - Move any TSM devices (Optical/Tape) to the new server.

In most cases, migrations like this only take 10 to 14 days to complete, and downtime is limited to just a couple hours over the weekend.

1798
Your process is good.  Depending on the size of the AG, it may take a long time.

-JD.

1799
MP Server / Re: SSAM and arsload
« on: April 28, 2011, 04:24:54 AM »
Well, to start with, TSM and SSAM are really the exact same thing.  The only difference is licensing and a configuration switch.

When 'ArchiveRetentionProtection' is enabled on the TSM server (ie, TSM becomes SSAM), you cannot delete archived documents before their expiration period from within TSM.  SSAM on the DR550 goes a little further by preventing you from deleting files at the operating system level as well -- but you can get identical functionality by combining TSM (with Archive Retention Protection on) and a write-once technology like SnapLock or Centera.

So, the same situation applies as before -- if arsload begins providing files to TSM/SSAM, and half way through, the load fails for some reason, that space is lost until the documents naturally expire.  For problematic Application Groups, I recommend storing in Cache for 1 day before migrating to your DR550/WORM storage.  You're exposed for that 24 hours (from a data security perspective) so you need to weigh the benefits and risks and come to a compromise your management can live with.

-JD.


1800
Report Indexing / Re: Storage object error
« on: April 27, 2011, 01:18:01 PM »
Hi Pankaj.

If your individual documents are 300k, and your object is 1.5G, there is likely a problem with your indexing as well.  Except in very special circumstances, objects should always be in the 10-Megabyte range.

-JD.

Pages: 1 ... 115 116 117 118 119 [120] 121 122 123 124 125 ... 133