Hi everyone,
I'm currently using BE 2010R3 and i wonder to upgrade to 2014 but... I have script in BEMCLI that automatically create and run restore job from previous day. Is this possible in BE 2014? Can i create restore job by BEMCLI script as i can in BE 2010?
Thanks for any replays.
Best Regards
You can use this BEMCLI cmdlet to do your file system restore
Submit-BEFileSystemRestoreJob
You can use this BEMCLI cmdlet to do your file system restore
Submit-BEFileSystemRestoreJob
yes, but the main problem is that i want to restore previosly backedup SQL Database to different server.
I have production database (ERP system) and after full backup i want to restore it on warehouse database.
That's my main case....
Thanks
If you have a script in BE 2010 R3 it will have used BEMCMD so no your script will not work in BE 2014 BEMCLI
Also Backup Exec is not really designed as a replication tool for SQL databases as such if your intention is to maintain regular updates between the two SQL instances it is probably a better idea to look at tools specifically designed for the job (possibly even forms of Log Shipping configurations that SQL itself can offer)
Yes i have script that is working in BE2010 R3. It was not working in BE2012 ....
my script look like this:
1. I need to check JobHistoryID (JOBHISTORY_GUID) for my backup job.
2. i run this script:
bemcmd.exe -o90 -v -f C:\Scripts\res.txt
res.txt look like this:
[General]
JOB_TYPE=Restore
JOB_PRIORITY=HIGH
USERNAME=BEUser
PASSWORD=password
[Restore_Options]
SQL_REDIRECT_SERVER=dest sql server name
SQL_REDIRECT_SERVER_ACCOUNT={10011001-1001-1001-0101-010101010101}
SQL_REDIRECT_ACCOUNT={10011001-1001-1001-0101-010101010101}
SQL_REPLACE_DATABASE=1
SQL_DEFAULT_DRIVE=E
SQL_POSTRESTORE_DBCC=0
COMMAND_RUN_POST_IF_JOB_FAILS=0
COMMAND_RUN_OPTION = 0
[Selections]
JOBHISTORY_GUID={b264b8ea-efce-4344-89ae-15ac46d96964}
[Schedule]
DELETE_JOB_AFTER=2
My goal is that after full backup of production database i need this data on second sql server for reporting system (data warehouse). It's not a replication scenario.
I trayed this in BE2012 withou success, now it's BE2014 - maybe it will work.
Did you have any experience with this?
Thanks for replays!
BE is never designed for SQL database replication.
You need to do a bit of manual work. Get a copy of the SQL backup.
and then use SQL Studio to restore this copy to your other database.
but in BE 2010 R3 i can do full backup and then restore it by BEMCLI (create new restore job) to different server.
It's not replication solution.
You might want to look at the log shipping function of SQL Server to solve your problem.
