plesk backup error: HELP

[mircea_hosteur]

"PLESK DOES NOT SUPPORT BACKING UP DATABASES THAT ARE NOT LOCATED ON CURRENT MACHINE"


but all MSSQL databases are located on the same machine that I try to make the backup

how can I fix that ?

it's quite urgently

 

[sergius]

Unfortunatly Plesk for Windows cannot backup MS SQL databases located on remote server yet... SWsoft development team are working on this issue.

 

[mircea_hosteur]

no, it's not like that !!!!!!!

it is the same machine

all is on the same machine: plesk, sites, plesk internal database, mssql express ...all I am tring to backup is on the same machine !

there is no remote server !!!

I try to make the plesk backup using the same machine , msde (in fact it's mssql express) is running on the same machine

the main problem is that plesk reports mssql server as a remote machine and not like local machine

how can I fix that please ?!
It's urgently

I have already canceled the server and I need urgently make the full backup and restore on another server

Please advise how could I fix tell to Plesk that MSSQL is on the same machine

waiting for urgently reply,

thanks

 

[Dmitry Drozdov]

Hello,
MS SQL has the Enterprise Manager tool. Using this soft you can backup your DBs and restore them to remote server. Whereupon, you should reconfigure Plesk for using this DB.
On the other hand, you can wait for one or two weeks because we are going to release PMM DB Agent. Alternatively, you might be our beta tester.

Thanks.

 

[zubin]

Why not have an option to proceed with the backup without the MSSQL databases but only save their entries (database name/user/password) in the Plesk database backup.

 

[zubin]

was this issue ever addressed?

 

[Dmitry Drozdov]

Of course, yes.
We will add this feature to PMM in future.
Thanks.

 

[zubin]

any suggestions on how to backup without mssql since the backup tool does not work for mssql?

 

[zubin]

cant be too hard adding a "skip mssql databases" option, right?

where can i see more details on "PMM" ?

 

[Dmitry Drozdov]

For more details about PMM, you should look at "Plesk Migration Manager User's Guide". http://www.swsoft.com/en/products/plesk76win/docs/
Thanks.

 

[zubin]

the requirement is not to migrate but simply take a backup of data on a secondary disk or remote FTP server. The Plesk backup utility fails to do that if SQL databases are hosted on another server. A resolution would either be to update the backup utility to backup remote databases or skip them and backup all the other data of the websites.

 

[Dmitry Drozdov]

a) The main goal of Plesk Backup/Restore Tool is to execute action for saving and recovering customers data. There are not goals to do migration from one environment to other by using Backup/Restore Tool, it is out of scope.
b) If you have a little server/db administrators experience it is not so difficult to migrate one or two databases from one server to another. We are going to release DB agent for PMM in nearest time. It will have a simple behavior, simple UI, and simple scenario to collect DB content on source server and restore it on destination server. It will help people who wants migrate his own DBs. If you need this feature, you should wait.
c) PMM has migration archive. It consists of Web content + DB dumps + mail content + Host Settings/Descriptions, and etc. You can reuse it for your aims.

 

[zubin]

i am not trying to achieve a migration, just a simple backup. But plesk backup does not backup websites when MSSQL databases are not on localhost. It simply throws up an error that remote SQL is not supported and exits rendering the backup tool useless.

 

[Dmitry Drozdov]

I know about it. With time the PMM will replace this tool because of flexible. Plesk is Control Panel and gives you convenience for working with server. Unfortunately not all features have been done yet.

In your situation I might get advice, you should:
1) Dump DB by your hands
2) Exclude remote DB from domain in Plesk. (If Plesk does not have record about DB, B/R tool will not try to do DB dumps.)
3) Backup Client or Domain
4) …..
5) Restore Client or Domain
6) Restore DB
7) Include DB to domain.
In this case you can escape this error.
Please don’t forget to do Server Backup before you experiments.