Backup & Restore of The Versiondog Server Archive: © Auvesy GMBH

Backup & restore of the
versiondog server archive

© AUVESY GmbH
Last updated: 01 June 2017
Fichtenstrasse 38 B
D-76829 Landau
Germany
TOC
Backup and restore of the versiondog server archive 3
Single server system 4
Parallel server system 8
Possible scenarios in practice 14
Scenario 1: Failure of a single server system 15
Scenario 2: Failure of one of the servers in a parallel server system 16
Scenario 3: Failure of the entire parallel system system 17
Location of server archive - local or remote 19
2
Backup and restore of the versiondog server archive
Loss of data or faulty data storage systems can lead to very substantial damage for any business.
Rapid restoration helps to reduce the resulting costs. Therefore, it is paramount that you make reg-
ular backups of your data so that disaster recovery can be performed quickly and with confidence.
You can backup data on a versiondog server system by making a copy of the server archive. A backup
copy enables rapid restoration if the need arises.
With the versiondog system, backups can be made either manually or automatically. Manual backups
can be made before certain events, such as system updates. Automatic backups (using a batch file for
example) can be used to secure your data at regular intervals.
With versiondog, you can perform backups for both single server and parallel server systems.
3
Single server system
Manual backups
With versiondog, you can manually back up data that is present on a versiondog single server system
by making a copy of the server archive.
While the backup is running, the availability of the system is limited. We recommend that backups
be made at off-peak times, e.g. overnight or on weekends.
Prerequisites
l The user who performs the backup must have administrative rights on the server system.
l There should be no synchronisation processes outstanding.
How to perform a backup
Step 1: Activate versiondog maintenance mode
l Open the versiondog AdminClient and click on maintenance mode. Maintenance mode will be
activated.
Maintenance mode ensures that the data in the versiondog server archive remains in a consistent
state while the backup is running. It does this by blocking write access (i.e. Check-In). Read access (i.e.
Check-Out) remains possible.
Step 2: Make a backup of the server archive
l Local archive
If you are working from a local archive (not from a remote server), data is stored on the same
computer as the one on which the versiondog server is running.
Copy the folder vdServerArchive to the desired location, e.g. an external hard drive.
l Remote archive
If you are working from a remote server archive, the folder vdServerArchive will be in two
places: in local directory on the server (on which the versiondog service is running), and it will
also be in the remote archive (to store the project data on the remote share)
The local server archive is NOT relevant when performing backups. This is because it does not
4
contain any project data. Only backup the remote archive. It contains all the important inform-
ation. It is NOT necessary to backup the local server archive in addition to the remote archive!
To backup the remote archive, copy the folder vdServerArchive of the remote share to the
desired location.
The folder VD_TMP_VD of the server archive contains only temporary files. If you
want to save space on your storage medium, backup the server archive without the
folder VD_TMP_VD.
Step 3: Deactivate versiondog maintenance mode
deactivated.
Automatic backup
As standard, there is no automatic backup function for the data on a versiondog single server system.
However, you can automate the process by creating a batch file and using the Windows Task Sched-
uler to make a copy of the data at a predetermined time.
The following describes how to implement a process that will make an automatic backup copy of the
data on a single server system. It is merely a recommendation and is intended for guidance purposes
only.
Prerequisites
l The user who performs the backup needs to have administrative rights to run batch files on the
server system.
How to perform a backup
The batch file needs to go through the following steps:
5
Maintenance mode ensures that the data in the versiondog server archive remains in a consistent
state while the backup is running. It does this by blocking write access (i.e. Check-In). Read access (i.e.
Check-Out) remains possible.
Step 2: Make a backup of the folder vdServerArchive
To save space on your storage medium, the folder vdServerArchive can be compressed before the
copy is made. To do this, a suitable ZIP utility must be installed.
Sample batch file
@echo off REM Maintenance Mode on
"%PROGRAMFILES(x86)%\vdogServer\VDogMasterService.exe" /at:s /rd:d:\vdServerArchive /main-

tenance:on
if ERRORLEVEL 1 ECHO "The attempt to put the versiondog server into maintenance mode has
failed." >> d:\vdServerBackupLog.txt
if ERRORLEVEL 0 ECHO "The versiondog server has been put into maintenance mode." >> d:\vdServer-
BackupLog.txt
REM Make a zipped backup copy of the versiondog local ServerArchive using a 7-zip
"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip d:\vdServerArchive\*
REM Make a backup copy of the versiondog local ServerArchive using a 7-zip
REM with the batch command "net use" connect to the remote ServerArchive (if necessary)
"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip \\stor-

age\share\vdServerArchive\*
REM Use the batch command "net use" to disconnect to the remote ServerArchive
REM Maintenance mode off
6
tenance:off
if ERRORLEVEL 1 ECHO "The attempt to take the versiondog server out of maintenance mode has
if ERRORLEVEL 0 ECHO "The versiondog server has been taken out of maintenance mode." >>
d:\vdServerBackupLog.txt
If you want to use this sample batch file, you will need to change the paths to match your system.
7
Parallel server system
Manual backup
With versiondog, you can manually back up the data on a versiondog parallel server system.
Prerequisites
l The user who performs the backup needs to have administrative rights on the server system.
How to perform the backup
activated.
When you activate maintenance mode on one server of a versiondog parallel server sys-
tem, then the other server, too, is automatically put into maintenance mode. Maintenance
mode ensures that the data in the versiondog server archive remains in a consistent state while
the backup is running by blocking write access (i.e. Check-In). Read access (i.e. Check-Out)
remains possible.
l Server A
l Local archive
If you are working with a local archive (not from a remote server), the project data will be
stored on the same computer on which versiondog is running.
l Remote archive
8
places: in local directory on the server (on which the versiondog service is running), and
it will also be in the remote archive (to store the project data on the remote share)
The local server archive is NOT relevant when making backups. It doesn't contain any
project data. Therefore, only backup the remote archive. It contains all the important
information. It is NOT necessary to backup the local server archive in addition to the
remote archive!
In order to backup the remote archive, copy the folder vdServerArchive of the remote
share to the desired location.
l Server B
l Local archive
l Remote archive
it will also be in the remote archive (to store the project data on the remote share).
remote archive!
The folder VD_TMP_VD on the server archive contains only temporary files. If you
folder VD_TMP_VD.
Step 3: Deactivate versiondog maintenance mode.
l Open the versiondog AdminClient and click on maintenance mode. Maintenance mode is now
deactivated.
9
Automatic backup of data
As standard, there is no automatic backup function for the data on a versiondog parallel server sys-
tem. However, you can automate the process by creating a batch file and using the Windows Task
Scheduler to make a copy of the data at a predetermined time.
The following describes how to implement a process that will make an automatic backup copy of the
data on a parallel server system. It is merely a recommendation and is intended for guidance pur-
poses only.
Prerequisites
l The user who performs the backup needs to have administrative rights to run batch files on the
server system.
The batch file needs to go through the following steps:
When you activate maintenance mode on one server of a versiondog parallel server system, then
the other server, too, is automatically put into maintenance mode. Maintenance mode ensures that
the data in the versiondog server archive remains in a consistent state while the backup is running by
blocking write access (i.e. Check-In). Read access (i.e. Check-Out) remains possible.
Step 2: Make a backup copy of the folder vdServerArchive
To save space on your storage medium, the folder vdServerArchive can be compressed before the
copy is made. To do this, a suitable ZIP utility must be installed.
Step 4: Repeat steps 1–3 for the second server system
10
Sample batch file
@echo off
REM Maintenance mode on

tenance:on
if ERRORLEVEL 1 ECHO "The attempt to put the versiondog server into maintenance mode has
if ERRORLEVEL 0 ECHO "The versiondog server has been put into maintenance mode." >> d:\vdServer-
BackupLog.txt
REM Make zipped backup copy of the local ServerArchive using 7-zip
"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip d:\vdServerArchive\*
REM Make zipped backup copy of the remote ServerArchive using 7-zip
REM with the batch command "net use" connect to the remote ServerArchive (if necessary)
"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip \\stor-

age\share\vdServerArchive\*
REM with the batch command "net use" disconnect to the remote ServerArchive (if necessary)
REM Maintenance mode off

tenance:off
if ERRORLEVEL 1 ECHO "The attempt to take the versiondog server out of maintenance mode has
if ERRORLEVEL 0 ECHO "The versiondog server has been taken out of maintenance mode." >>
d:\vdServerBackupLog.txt
11
Note: If you want to use this sample batch file, you will need to change the paths to match your
system.
Alternative backup method
We recommend that backups be made at off-peak times with the versiondog system in maintenance
mode. But if there are no off-peak times, for example in 24/7 production, it is still possible to make a
backup copy. The following describes how to make a backup copy during normal production.
Prerequisites
l The user who performs the backup needs to have administrative rights on the server system.
l The system is a parallel server system.
Step 1: Stop the service VDog MasterService on the first versiondog server
l Go to Start/Control Panel/System and Security/ Administrative Tools and double-click on Ser-

vices. Services will be displayed.
l Right-click on the service VDog MasterService and select Stop.
l Server A
l Local archive
l Remote archive
it will also be in the remote archive (to store the project data on the remote share).
12
remote archive!
The folder VD_TMP_VD on the server archive contains only temporary files. If you
folder VD_TMP_VD.
Step 3: Restart the service VDog MasterService on the first server
l Go to Start/Control Panel/System and Security/ Administrative Tools and double-click on Ser-

vices. Services will be displayed.
l Right-click on the VDog MasterService and select Start.
Step 4: Repeat steps 1 – 3 for server B
13
Possible scenarios in practice
The value of having made a backup copy quickly becomes apparent if data is lost or if a storage
medium fails. The copy can be used to immediately restore the data.
The following describes real-world scenarios where a backup copy of the versiondog server archive
would be required to restore data. The word 'failure' refers here to either a hardware malfunction or a
loss of data due to operator error. These scenarios are described for systems running Microsoft Win-
dows as the operating system.
14
Scenario 1: Failure of a single server system
The value of having made a backup copy quickly becomes apparent if data is lost or if a storage
medium fails. The copy can be used to immediately restore the data.
Following a hardware malfunction in a single server system, server function has been compromised.
Normal server operation needs to be restored with the minimum possible loss of data.
Restore data
Prerequisites
l The single server system has been returned to a sufficiently operable condition for versiondog
Server to be installed.
l The user who performs the restoration of data needs to have administrative rights on the
server system.
l There should be no synchronisation processes due.
How to restore the versiondog server archive
Step 1: Unzip (if necessary) your backup copy of the versiondog server archive and copy it to its nor-
mal location on the server
Step 2: Run the versiondog setup, specifying this newly-replaced server archive as 'existing server
archive'
l Install the versiondog server applications using Setup.exe, which you can find in the versiondog
setup directory. During the installation, select the option Server with existing server archive.
Now specify the newly-replaced Server B server archive.
15
Scenario 2: Failure of one of the servers in a parallel server system
During operation, a defect causes the failure of one of the servers. Let's say that Server B is down, but
server A is still fully functional. We want to resume parallel server operation with the minimum pos-
sible loss of data. In order to do this, Server B needs to be reintegrated into the system, ideally
without any loss of data at all.
Restore data
Prerequisites
l Server B has been returned to a sufficiently operable condition for versiondog Server to be
installed.
server system.
Step 1: Unzip (if necessary) your backup copies of the versiondog ServerArchive and copy them to
their normal locations on the servers
Step 2: Run the versiondog setup on Server B, specifying the newly-replaced server archive as 'existing
server archive'
Now specify the newly-replaced server archive.
Step 3: Use the versiondog parallel server utility to synchronise all project data and metadata between
Server A and Server B
l On Server A, run VDogParallelServerUtil.exe (you can find this in <Drive:>\Program Files\v-

dogServer\). In the case of the failure of ONE server in a parallel server system, it is important
that this utility is run on the server that did NOT experience the failure.
16
Scenario 3: Failure of the entire parallel system system
All data has been lost from both servers of a parallel server system. Normal server operation needs to
be restored with the minimum possible loss of data, ideally without any loss of data at all.
Restore data
Prerequisites
l Server A and Server B have both been returned to a sufficiently operable condition for ver-
siondog Server to be installed.
server system.
Step 1: Unzip (if necessary) your backup copies of the versiondog ServerArchive and copy them to
their normal locations on the servers
Step 2: Run the versiondog setup on Server A, specifying the newly-replaced Server A server archive as
'existing server archive'
Now specify the newly-replaced Server A server archive.
Step 3: Run the versiondog setup on Server B, specifying the newly-replaced Server B server archive as
'existing server archive'
Now specify the newly-replaced Server B server archive.
Step 4: Use the versiondog parallel server utility to synchronise all project data and metadata between
Server A and Server B
17
l On Server A, run VDogParallelServerUtil.exe (you can find this in <Drive:>\Pro-
gramFiles\vdogServer\). In the case of the failure of ONE server in a parallel server system, it is
important that this utility is run on the server that did NOT experience the failure.
18
Location of server archive - local or remote
The versiondog server archive contains important information. We recommend that you make reg-
ular backups of the versiondog server archive to reduce the likelihood of data loss and help with rapid
restoration.
The versiondog server archive can be stored in a local directory or in a directory on a remote share:
l Server archive in a local directory
If the server archive is in a local directory, the project data is stored on the same com-
puter on which versiondog is running. Make sure to backup the local server archive, so
that data can be quickly restored. It contains all the important information.
l Server archive on a remote share
If the server archive is on a remote share, the project data is NOT stored on the same
computer on which versiondog is running. In this case, the versiondog service and the
versiondog projects are separate. The versiondog service is available on one computer
and the project data is available from a remote share.
19
For technical reasons, the computer (on which the versiondog service is running) is
started from a server archive in a local directory. However, it doesn't contain any project
data. Project data is only contained in the server archive on a remote share. The local
server archive is NOT relevant when making backups. Therefore, only backup the remote
archive! It contains all the important information. It is NOT necessary to backup the local
server archive in addition to the remote archive!
20

Backup & Restore of The Versiondog Server Archive: © Auvesy GMBH

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Backup & Restore of The Versiondog Server Archive: © Auvesy GMBH

Загружено:

Авторское право:

Доступные форматы

Backup & restore of the

versiondog server archive

Last updated: 01 June 2017

Backup and restore of the versiondog server archive 3

Single server system 4

Parallel server system 8

Possible scenarios in practice 14

Scenario 1: Failure of a single server system 15

Scenario 2: Failure of one of the servers in a parallel server system 16

Scenario 3: Failure of the entire parallel system system 17

Location of server archive - local or remote 19

be made at off-peak times, e.g. overnight or on weekends.

l There should be no synchronisation processes outstanding.

How to perform a backup

Step 1: Activate versiondog maintenance mode

Step 2: Make a backup of the server archive

Step 3: Deactivate versiondog maintenance mode

be made at off-peak times, e.g. overnight or on weekends.

l There should be no synchronisation processes outstanding.

How to perform a backup

The batch file needs to go through the following steps:

Step 1: Activate versiondog maintenance mode

Step 2: Make a backup of the folder vdServerArchive

copy is made. To do this, a suitable ZIP utility must be installed.

Step 3: Deactivate versiondog maintenance mode

Sample batch file

@echo off REM Maintenance Mode on

"%PROGRAMFILES(x86)%\vdogServer\VDogMasterService.exe" /at:s /rd:d:\vdServerArchive /main-

"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip d:\vdServerArchive\*

"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip \\stor-

REM Maintenance mode off

be made at off-peak times, e.g. overnight or on weekends.

l There should be no synchronisation processes outstanding.

How to perform the backup

Step 1: Activate versiondog maintenance mode

Step 2: Make a backup of the server archive

Step 3: Deactivate versiondog maintenance mode.

be made at off-peak times, e.g. overnight or on weekends.

l There should be no synchronisation processes outstanding.

How to perform the backup

The batch file needs to go through the following steps:

Step 1: Activate versiondog maintenance mode

Step 2: Make a backup copy of the folder vdServerArchive

copy is made. To do this, a suitable ZIP utility must be installed.

Step 3: Deactivate versiondog maintenance mode

Step 4: Repeat steps 1–3 for the second server system

REM Maintenance mode on

"%PROGRAMFILES(x86)%\vdogServer\VDogMasterService.exe" /at:s /rd:d:\vdServerArchive /main-

"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip d:\vdServerArchive\*

"%PROGRAMFILES(x86)%\7-Zip\7z.exe" u -t7z -r d:\vdServerBackup.zip \\stor-

REM Maintenance mode off

"%PROGRAMFILES(x86)%\vdogServer\VDogMasterService.exe" /at:s /rd:d:\vdServerArchive /main-

Alternative backup method

l There should be no synchronisation processes outstanding.

l The system is a parallel server system.

How to perform the backup

l Go to Start/Control Panel/System and Security/ Administrative Tools and double-click on Ser-

l Right-click on the service VDog MasterService and select Stop.

Step 2: Make a backup of the server archive

Step 3: Restart the service VDog MasterService on the first server

l Go to Start/Control Panel/System and Security/ Administrative Tools and double-click on Ser-

l Right-click on the VDog MasterService and select Start.

Step 4: Repeat steps 1 – 3 for server B