Restoring VZRESTORE to a different IP

[KrazyBob]

A migration from Plesk 8.6 to 10.4.4 has gone miserably. It has now been 8 days be we're not on solid footing. Certain files are needed by the client on their old server but their IP's were already moved on. I have assigned temporary IP's to the old container and that's when it gets weird.

Starting restore VE 321(2012-06-10T023002-0700@hw007.xxxxx.xxx) on node xx.xx.xx.xx.
Doing exec - /usr/share/vzbackup-3.0.0-17.swsoft/vzrestore1 -t 2012-06-10T023002-0700@hw007.xxxxx.xxx 321 -.
Created /vz/private/321-tmpG23354
Restoring VE...
Turn quota on
-...
tar: 321/root/root/.ssh: time stamp 2035-04-08 12:44:22 is 719845424 s in the future
tar: 321/root/.mysql_history: time stamp 2035-01-19 17:50:01 is 713041726 s in the future
tar: 321/root/etc/psa/psa.key.~10~: time stamp 2035-01-19 10:26:47 is 713015129 s in the future
tar: 321/root/etc/psa/psa.key.~11~: time stamp 2035-01-19 16:55:33 is 713038455 s in the future
tar: 321/root/etc/psa/psa.key.~12~: time stamp 2035-01-19 16:55:52 is 713038474 s in the future
tar: 321/root/etc/psa/psa.key.~13~: time stamp 2035-01-19 17:49:18 is 713041680 s in the future
tar: 321/root/etc/psa/psa.key.~3~: time stamp 2035-01-19 09:21:42 is 713011223 s in the future

Weird question, I know. I'm stumbling along...

[faris]

hells bells that's damn wierd. I take it that it falls over at that point?

So the old Container isn't just shut down -- it is deleted? If it wasn't deleted and is still there then why not just copy the files directly from /vz/private/[CTID]?

Note that vzbackup backups are tar-based. You should be able to untar them manually in some way, I think. I don't know how, though.

I'm really sorry not to be very useful to you right now. Personally I'd be paying Parallels their $75 right now, as it will be the quickest solution to the problem.

[KrazyBob]

Well, as you know inside the TAR are SSL certifiates which did not migrate over. Parallels came and got them and said that they were expired. Our client records show that they are not. I triewd to change the default IP of the old server with a new IP, and then assign dedicated IP's to those sites as needed. I used:

vzrestore -d xxx.xxx.xxx.xxx -e <CTID>

and suddenly it was the year 2035.

[KrazyBob]

The worst part of all of this is that I have 25 servers to migrate. Parallels in their usual arrogant fashion demands one issue per ticket. They expected us to pay the SUS fee to upgrade Plesk and Virtuozzo and now expect us to pay $75 per issue where we locate bugs in THEIR software.

For over a week I've tried to migrate one server and only have partial success. Topping it off I have a a$$hat at Parallels that demands one issue per ticket even if the issue overlaps. we said one of three things that failed was SSL cert. migration. He made us open a new ticket just for SSL certs., and another and another.

I cannot recommend to any web host Virtuozzo.

I tried running a backup on the same server, since one cannot backup to a Virtuozzo 3 server. This is what I have trying to backup to the same server as the source and I know it isn't right:

Code: Select all

[root@hw006 ~]# vzbackup hw006..net -e 113
2012-06-16T20:02:09-0700 vzbackup(37510): Starting backup. Nodes - hw006.net.
2012-06-16T20:02:09-0700 vzbackup(37510): Starting node hw006..net backup...
2012-06-16T20:02:09-0700 vzbackup(37510): Checking backup version on hw006..net ... use vzbackup 4.7.0-2
2012-06-16T20:32:59-0700 vzbackup(37510): Node hw006..net archived containers: 113(2012-06-16T200210-0700@hw006..net)
2012-06-16T20:32:59-0700 vzbackup(37510): Cleaning up...

-rw-r--r-- 1 root root 2.0G Jun 16 20:32 113-2012-06-16T200210-0700@hw006..net-I-04.tar
-rw-r--r-- 1 root root 2.0G Jun 16 20:06 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0001
-rw-r--r-- 1 root root 2.0G Jun 16 20:07 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0002
-rw-r--r-- 1 root root 2.0G Jun 16 20:09 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0003
-rw-r--r-- 1 root root 2.0G Jun 16 20:11 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0004
-rw-r--r-- 1 root root 2.0G Jun 16 20:13 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0005
-rw-r--r-- 1 root root 2.0G Jun 16 20:14 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0006
-rw-r--r-- 1 root root 2.0G Jun 16 20:16 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0007
-rw-r--r-- 1 root root 2.0G Jun 16 20:17 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0008
-rw-r--r-- 1 root root 2.0G Jun 16 20:19 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0009
-rw-r--r-- 1 root root 2.0G Jun 16 20:21 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0010
-rw-r--r-- 1 root root 2.0G Jun 16 20:23 113-2012-06-16T200210-0700@hw006.net-I-04.tar.v0011
-rw-r--r-- 1 root root 2.0G Jun 16 20:24 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0012
-rw-r--r-- 1 root root 2.0G Jun 16 20:26 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0013
-rw-r--r-- 1 root root 2.0G Jun 16 20:27 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0014
-rw-r--r-- 1 root root 2.0G Jun 16 20:29 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0015
-rw-r--r-- 1 root root 2.0G Jun 16 20:30 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0016
-rw-r--r-- 1 root root 1.9G Jun 16 20:32 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0017

[faris]

Nightmare!

I take it that the keys didn't come direct from Parallels, so you can't make use of the free migration assistance? I also assume whoever did sell them to you can't provide support. All this adds up to extremely annoying and stressful for you.

Regarding the SSL, can't the customer just get it reissued? Then you wouldn't have this horror to deal with. Alternatively, how about purchasing and installing one yourself, again just to make the problem go away? Sorry if this isn't useful to you -- I'm just trying to suggest something in case it helps.

One thing I can tell you is that you won't have this horror with all your migrations. I've done three 8.6 to 10.4.4 and one 8.4 to 10.4.4 now with no unsolvable problems. So it won't be like this each time.

[faris]

Just going back to your vzbackup output when you do it on the same node...I may be missing something but I'm not seeing anything wrong?

While you are at it, why not do a vzabackup too, for good luck?

[KrazyBob]

You've made broad, and sweeping and incorrect assumptions. I own every key and no, Plesk does not provide free migration assistance.

This looks normal to you? I've been doing backups since 2007 and never had output like this,

Code: Select all

-rw-r--r-- 1 root root 2.0G Jun 16 20:32 113-2012-06-16T200210-0700@hw006..net-I-04.tar
-rw-r--r-- 1 root root 2.0G Jun 16 20:06 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0001
-rw-r--r-- 1 root root 2.0G Jun 16 20:07 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0002
-rw-r--r-- 1 root root 2.0G Jun 16 20:09 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0003
-rw-r--r-- 1 root root 2.0G Jun 16 20:11 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0004
-rw-r--r-- 1 root root 2.0G Jun 16 20:13 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0005
-rw-r--r-- 1 root root 2.0G Jun 16 20:14 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0006
-rw-r--r-- 1 root root 2.0G Jun 16 20:16 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0007
-rw-r--r-- 1 root root 2.0G Jun 16 20:17 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0008
-rw-r--r-- 1 root root 2.0G Jun 16 20:19 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0009
-rw-r--r-- 1 root root 2.0G Jun 16 20:21 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0010
-rw-r--r-- 1 root root 2.0G Jun 16 20:23 113-2012-06-16T200210-0700@hw006.net-I-04.tar.v0011
-rw-r--r-- 1 root root 2.0G Jun 16 20:24 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0012
-rw-r--r-- 1 root root 2.0G Jun 16 20:26 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0013
-rw-r--r-- 1 root root 2.0G Jun 16 20:27 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0014
-rw-r--r-- 1 root root 2.0G Jun 16 20:29 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0015
-rw-r--r-- 1 root root 2.0G Jun 16 20:30 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0016
-rw-r--r-- 1 root root 1.9G Jun 16 20:32 113-2012-06-16T200210-0700@hw006..net-I-04.tar.v0017

Code: Select all

Processing file "/etc/hspc/licenses/vzlicense"...
HW
         owner_name="Krazy Bob (XXXXX.com)"
         target_OS="Linux"
         status="ACTIVE"
         version=2.5
         owner_id=1404933.366511

Faris, your accusations are unwarranted. I own 15 Virtuozzo and 30 Plesk keys.

Nightmare!

I take it that the keys didn't come direct from Parallels, so you can't make use of the free migration assistance? I also assume whoever did sell them to you can't provide support. All this adds up to extremely annoying and stressful for you.

Regarding the SSL, can't the customer just get it reissued? Then you wouldn't have this horror to deal with. Alternatively, how about purchasing and installing one yourself, again just to make the problem go away? Sorry if this isn't useful to you -- I'm just trying to suggest something in case it helps.

One thing I can tell you is that you won't have this horror with all your migrations. I've done three 8.6 to 10.4.4 and one 8.4 to 10.4.4 now with no unsolvable problems. So it won't be like this each time.

[KrazyBob]

To put two points to rest, 1) Plesk migrations support is only free if you cannot find a knowledge base article. If it's in the KB (and you can never find it) they charge $75 per issue.

2) My keys are all legitimate. My current open ticket on SSL certs. is:

[Parallels #1399366] SSL certificates issue after migration in ticket #1398305

[faris]

Total misunderstanding here. No insult intended. Full apology from me.

Yes, the output looks normal to me. Backup split into lots 2Gb chunks. If there's something strange about it, I'm just missing it - which is easy enough! What is it that looks abnormal, exactly? If you point it out then I'll bet I'll be going "oh! Yes. Of course. You are right" but I can't see it

Regarding the keys, I mean if you buy them from parallels you get free migration/upgrade assistance when going to 10.x. If you obtain them from elsewhere (e.g. third party, like I do - 4PSA), you don't. Not sure what the situation is when you are a Parallels partner in this situation.

https://www.parallels.com/support/plesk ... ssistance/

This direct from Parallels thing caused me problems. I didn't know it had to be a Parallels-supplied key when I filled out the form the first time, and the key I was using wasn't, so I wasted loads of time

So, as I was typing this you'lve just mentioned about the "if it isn't in the KB". Well, yes, it is hard to find stuff sometimes. But they can't charge you without prior-permission, can they? With the free support thing they don't ask for money in advance, right?

And surely your problem isn't in the KB?

[KrazyBob]

The KB states that the SSL issue was solved in version 10.3.

I have never had chunks for a backup. I've always had one file under Virtuozzo 3.

Code: Select all

vzbackup -I <destination> - e CT_ID

Are you saying that in Virtuozzo 4 this is a backup? They don't even add up to the size of the container and I haven't specified compression. They look like this in Virtuozzo 3:

Code: Select all

107-2012-06-13T220111-0700@hw003.xxxxx.net-I.tar.gz

[faris]

Just to underline what I'm saying -- complete and utter apologies from me to KrazyBob!

When I say keys not from parallels, I mean from a third party. e.g. 4psa. Not for a moment did I think it could be misread as being "keys not legitmately obtained" (I didn't think that was even possible?).

I did NOT mean to imply that KrazyBob had obtained any keys in any way that was not correct.

EDIT: I missed the bloody NOT out of my original post. Sorry! It is 1am here. Please forgive me.

[faris]

Well the KB is wrong, or the cause is different, because you are having the problem you are having in 10.4.4! QED, as they say (IMHO!!!) But it could be a struggle to get the support peeps to take my view, I suppose.

Regarding the backup being split up, there's a setting somewhere that says "split into XMb/YGb chunks". I'll be damned if I can remember where it is -- somewhere in the VZ configuration file related to backups.

I found that this setting was totally ignored at some point due to something...but I honestly can't remember what exactly. Please remember that I've not used vzbackup in years - not since I used VZ 3, I don't think. Ever since VZ4 I've used vzabackup, which always creates one single file.

EDIT: the same file specified the default compression, if I remember correctly.

[KrazyBob]

yzAbackup. Maybe that's the difference. VZ3 defaults to one file. I assumed vzbackup. It works but it splits into chunks. Now it makes a little sense.

[KrazyBob]

!Faris: Back on topic. Faris, you seem to know VZ4 best. All of my system is VZ3 except one server just converted. I need (must) get to Xend 3.3.x ASAP but have no backup. It seems that One cannot backup VX4 containers to VZ3 servers. As expected.

Do you know if one can backup to the same sever and later restore the the same servcer if need be?

@All: I need to update just Zend and IONCube. PHP is already in place at 5.3.3 and there are already prob;ems with legacy scripts. How can I just upgrade Zend and IONCube? I don'ty see a titorial for this. Usually the PHP upgrade brings them. (php-zend, etc.)

Thanks for your help Guys!

[faris]

php answer first:

Code: Select all

yum install php-ioncube-loader php-zend-guard-loader

Note that possibly unlike previous php installs you may have had, you won't see any reference to them in php.ini - they are loaded via their own little includes in /etc/php.d/something.conf sort of thing.

So if you have referenced to ioncube or zend at the bottom of your php.ini you you need to remove them.

There are other defaults that are different in 5.3, but just the usual stuff- magic quotes, register globals, long arrays, that sort of thing.