Automated backup options

Bokk

We are a new NSC and are looking at the options for doing an automated backup. We have done it using hotCopy, but this makes quite a large file because it does an actual copy of the whole DB. The backup function off the Tools menu creates a much smaller file. Is there a way to call that backup function in a batch file so it could run at night? (We are using the Navision database.)

Any alternatives or suggestions are welcome.

Thanks!

ld

Try to look at "www.expandit.com". Look at the menu utilities.

Lars

BGI

You could also change youre batch file to include an automatic zipping of the file created thru hotcopy.
If you zip the file, its a BIGGG difference.

Rgds
Benny

GoMaD

If you use WinRAR on the fbk file, it will be even smaller then a ZIP file (if you select the best possible compression method)

tvandongen

We are just using the open file option inside Veritas backup software, because we are using navision (2.60) 24 hours a day/7 days a week we can't afford to stop the database to make a backup using the default way.

http://www.veritas.com/products/categor ... uctId=bews

Jeff_Fierce

hotcopy.bat:

path=M:\path\Attain370;E:\AttainServer370
hotcopy.exe source=M:\path\Attain370.fdb destination=M:\path\Attain370-hc.fdb.

hotcopy.exe located in E:\AttainServer370, Batch called from there.

Result is always M:\path\Attain370-hc.fdb is not a valid path, whatever path i choose. I tried shorter names and extension fbk. I don't understand why the path is not valid. Gimme a hint, please.

Luc_VanDyck

Hint: use the backup description file to configure your backup schedule:

[Backup Files]

d:\Appl\MBS-NavisionW1370\database.fdb=d:\Data\Backup

[Options]

description="Backup of MBS-Navision W1 3.70 database"

dbtest=normal

cc=yes

email=youremail@domain.com

servername=SERVER1

osauthentication=no

nettype=tcp

Jeff_Fierce

I don't get it. It stumbles across the invalid destination path. Any other switches after that are ignored. I cannot find a backup description file. If i create one called "descr.txt" and call it with description=descr.txt the path is still invalid.


I've found the description in the reference and devote myself to RTFM. Now it works as it should. Thx.

Luc_VanDyck

This can be read in the w1w1ism.pdf manual:

The following example only uses the mandatory parameters. The database is stored in the same directory as the server based backup program and the backup is stored on another computer:

hotcopy source=database.fdb destination=\\backupcomputer\backup\Monday

Try the \\-notation for the destination path.

kine

hotcopy - attention to Case (upper lower...) :-) hotcopy is sometime too sensitive... 8)

Jeff_Fierce

Thanks all, now it works, i rtfm..

guenther

I want to use hotcopy from NA 3.60. Server: win2k server

this is my hotcopy.bat:

hotcopy.exe source=T:\Datenbank\Database360.fdb destination=\\server\d$\DaSi description="Backup" cc=yes servername=attain osautentication=no user=user password=password dbtest=normal

I get the error message:

The following message came from the server:

The operating system cannot gain access to the file .
Please check taht the file typ and attributes are correct.


I also used the description file with no success.

Anyone can help me?

Jelias1

We use a mixture of HotCopy and in-house software similar to Expand-IT that invokes Navision's standard back-up. The reason we use both is that our database is quite large (28 gb), and doing a restore takes over 22 hours, which is down-time we cannot afford.

By doing both during off-hours:

1. HotCopy provides a totally functional database, as of the prior evening. After the HotCopy backup, this file is copied over to a mirrored server. This means that in case of a catastrphic crash, users can be up and running as of the prior evening by just switching servers.

2. The standard Navision backup provides database integrity checking. Therefore, if the data integrity has been compromised, the Backup fails, and an EMail is sent to IT management. In this way, you instantly know that the database is corrupt and can (hopefully) fix the problem before the next backup cycle.

kine

We have problem with the

The operating system cannot gain access to the file .

I cant remember the solution, but we used config file instead of parameters on commandline and I think that there was problem with network drivers mapped under some letter (try UNC name \\servername\...)

aliennav

ld wrote:

Try to look at "www.expandit.com". Look at the menu utilities.

Lars

Thanx ma'an it's cool site.