configuration management

Service management systems are IT’s online face to the business. Although employees rely on enterprise applications and personal productivity tools to get their jobs done, they turn to the IT service system for fulfillment when they run into problems. This article defines the top five reasons for choosing orchestrated ITSM systems, then compares and contrasts these systems to the other classes of ITSM systems in use today.

Bob Aiello explains that ALM and ITIL provide considerable guidance that can help you implement a comprehensive software and systems development lifecycle. Your organization would benefit from implementing these best practices, especially if you need to meet regulatory requirements or perhaps pass an internal audit once in a while.

We're going to have to move our VOBs from one location on our server to another larger filesystem on the same computer. (in Linux, though there is a Windows box used for ease of administration)

Will we need to re-register or otherwise mess with our views to point to the right place, or will it be able to 'follow' the move, since it's only on the same computer?

My understanding of the operation is this:

1. Everyone checks everything in
2. Lock VOBs
3. Back Up VOBs
4. Unregister VOBs
5. Copy VOBs to new area, preserving permissions
6. Reregister VOBs
7. Unlock VOBs
8. Test

I shouldn't need to rmtag, or run fixprot or do a SIDwalk, right?

It's the same registry region, the same domain, the same server, just a different under-the-hood filesystem location on the server.

I need to move my current svn repo to a new domain/server.

When I looked through the documentation, 'svnadmin dump' and 'svnadmin load' will do the job for moving a repo to a new server. My question here is what else I need to do/consider when moving to a new "domain".

The current repo is enabled with ldap and needs to work the same fashion after the migration. Any help would much appreciated. Thanks,
Dani