03-08-2012
Key Points when Moving from Server A to Server B??
Hi Everyone,
I'm still learning daily about UNIX (specifically Solaris 10).
I'm tasked with moving my current application and database from Datacenter A to Datacenter B.
There will be no updates and no changes other than a new server and new location.
So far, I have Solaris installed and patched on the target to equal the patch level of the source.
My question is, what are key files or directories I should directly copy (or perhaps rsync) to do this as smooth as possible?
I will probably be frowned upon for this, but it may help explain my question a bit better.
So if this was Windows XP (for example) and I was giving someone a new pc. The OS would be installed and patched. Then the key folders I'd need to be sure to copy would be basically the user profile, favorites, mydocs, etc. I'm looking for a similar answer but in Unix terms.
I know right now the .profiles are not there and that is definatley one thing.
Can anyone maybe give me direction or a handy dandy guide "when moving to a new box...."?
Thanks for your time.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
Thanks for taking the time to read and respond to my post.
I am a Unix neophyte. I can install scripts, move around some and perform basic functions - mostly related to websites and alway with a resource guide in front of me.
I currently have 12 websites hosted on a VPS and I would... (2 Replies)
Discussion started by: lcurrie
2 Replies
2. AIX
I'm moving an application from an old RS6000 running 4.3.2 to a p5 running 5.3.
Could someone point me a the direction on docs to perform such a function? Critical OS files, moving of printers and print queues especially.
thanks (5 Replies)
Discussion started by: sullivjp
5 Replies
3. Shell Programming and Scripting
HI All,
I am trying to automate my stuff to make 'to-do-easier'.
I am new to shell scripting. I need help to you regarding the below problem.
I have one directory in my server, frequently files will store in that directory. I want to move that files into another server on every 5... (5 Replies)
Discussion started by: ravvamohan
5 Replies
4. Shell Programming and Scripting
I hope I'm posting this in the correct section.
I'm trying to move a database from one server to another. This is the code I'm using...
tar czf - vbdatabase.sql | ssh username@full.domain.com 'cat > /home/cpanelusername/vbdatabase.tar.gz
... but all I'm getting is a ">" and then nothing... (4 Replies)
Discussion started by: Chimpie
4 Replies
5. Solaris
Hi, I've used the following way to set ssh public key authentication and it is working fine on Solaris 10, RedHat Linux and SuSE Linux servers without any problem. But I got error 'Server refused our key' on Solaris 8 system. Solaris 8 uses SSH2 too. Why? Please help. Thanks.
... (1 Reply)
Discussion started by: aixlover
1 Replies
6. Linux
I currently have a web server its on a small harddrive I didn't know my site would grow so fast but now I need a bigger hard drive. Instead of adding another harddrive (host charge monthly of how many hard drives connected to server) is there anyway to just move the whole os to a bigger hard drive... (2 Replies)
Discussion started by: awww
2 Replies
7. Programming
I have a Perl script that worked fine before moving it to justhost.com. It was on a Windows/Apache server. Just host is using UNIX. Other Perl scripts on other sites that were also moved work fine so I know Perl is functioning.
The script is called cwrmail.pl and is located in my cgi-bin.
When I... (9 Replies)
Discussion started by: BigBobbyB
9 Replies
8. Linux
How to generate public key to connect from one ftp server to other server to use in scripting. (0 Replies)
Discussion started by: sridhardwh
0 Replies
9. UNIX for Advanced & Expert Users
How to generate public key to connect from one ftp server to other server to use in scripting. (1 Reply)
Discussion started by: sridhardwh
1 Replies
10. Red Hat
Hi all,
We have a disk array that has the boot drive on an OCZ SSD on a PCIe card. Well, the motherboard died and we got a new motherboard. We moved the controllers, NICs, etc, to the exact same slots on the new motherboard, except now it won't boot. I guess it doesn't recognize the OS on the... (1 Reply)
Discussion started by: glowe57
1 Replies
yumdb(8) yumdb(8)
NAME
yumdb - query and alter the Yum database
SYNOPSIS
yumdb [command] [packages ...]
DESCRIPTION
This command is used to query and alter the yum database, which is a simple key value store used in conjunction with the rpm database. Any
installed package can have arbitrary data in the yum database, however the main use case is to store extra data about packages as they are
installed.
yumdb commands are:
yumdb get <key> [pkg-wildcard]...
This command will get the value for the given key, limiting to any specified packages.
yumdb set <key> <value> [pkg-wildcard]...
This command will set the value for the given key, to the given value, limiting to any specified packages.
yumdb del <key> [pkg-wildcard]...
This command will delete the given key, limiting to any specified packages.
yumdb rename <old-key> <new-key> [pkg-wildcard]...
This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, noth-
ing happens.
yumdb rename-force <old-key> <new-key> [pkg-wildcard]...
This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-
key is deleted.
yumdb copy <old-key> <new-key> [pkg-wildcard]...
This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, nothing
happens.
yumdb copy-force <old-key> <new-key> [pkg-wildcard]...
This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-key
is deleted.
yumdb search <key> <wildcard>...
This command will search all packages for the given key, against any of the given wildcard values.
yumdb exist <key> [pkg-wildcard]...
This command will print any packages which have the given key, limiting to any specified packages.
yumdb unset <key> [pkg-wildcard]...
This command will print any packages which do not have the given key, limiting to any specified packages.
yumdb info [pkg-wildcard]...
This command will display all the data stored in the yumdb, limiting to any specified packages.
yumdb sync [pkg-wildcard]...
This command will add any missing data to the yumdb from the repositories, limiting to any specified packages. This is useful to run if you
have had any aborted transactions (and thus. missing yumdb data). Note that "yumdb sync" cannot know all the information that would have
been put into the yumdb at the time.
yumdb sync-force [pkg-wildcard]...
This command will replace any data in the yumdb from the repositories, limiting to any specified packages.
EXAMPLES
List all the packages which don't have a from_repo key/value:
yumdb unset from_repo
List all the packages which were installed as dependencies:
yumdb search reason dep
WELL KNOWN KEYS
Note that there is no limit to the number of keys that can be created or what they may contain (for installed packages only). However this
is a list of well known keys, and what they store.
checksum_data
checksum_type
These keys store the createrepo checksum, and it's type, of the available
package yum installed. Note that these are used by "yum version" to calculate
the rpmdb version.
command_line
This key stores the entire command line, of the yum command (if it was called).
from_repo
from_repo_revision
from_repo_timestamp
These keys take values from the available package yum installed, and store the
repo id, it's revision and timestamp.
reason
This key stores either "user" or "dep", currently. To mark if the user requested
the package to be installed, or if it was brought in automatically as a
dependency. Note that this is kept over updates.
releasever
This key stores the value of releasever, when the package was installed.
installonly
If this attribute has the value "keep" then this package will not be
removed automatically by the installonly process (and does not count towards
the installonly_limit).
SEE ALSO
yum (8)
rpm (8)
AUTHORS
James Antill <james.antill@redhat.com>.
James Antill 8 April 2010 yumdb(8)