Important: If you are upgrading from a previous version of StarTeam Server, you MUST review the upgrade instructions in the StarTeam 2009 Installation Guide (ST_Install_en.pdf). There are some steps that you must complete in order for the upgrade to complete successfully. Failure to complete these steps can cause the upgrade to fail.
StarTeam VaultVerify Utility version 10.11.0Copyright (c) 2005-2009 Borland Software Corporation. All rights reserved.VaultVerify: Perform archive verification on a StarTeam Native-II vault.Usage: VaultVerify [options] Based on the default or given '-check' option, integrity checks are performedon the vault archive files for the specified StarTeam . If'-repair' is specified, an attempt is made to correct problems found. Theconfiguration's database is opened but not modified.Valid options are:-check stray Determines which integrity checks to perform: missing: Checks for missing files by comparing the database against archive files actually present. corrupt: Checks the integrity of existing archive files (MD5, name, directory, and .gz file format). stray: Checks for extraneous files based on the database. This option cannot be used if the is in use. all: Performs all integrity checks. Multiple '-check' options can be specified. Also, see the '-repair' option.-cf Path name of the 'corrupt file folder', where problem files found by the 'corrupt' check are moved when '-repair' is specified. The default 'corrupt file folder' is: c:\temp\VVCorruptFiles\-dbhost Specifies the host name of the database server for the specified . On Windows, it is only meaningful when '-dbinstance' is also provided. On Windows and Linux, use this option only when the database server executes on a different host than this one.-dbname Specifies the database name for the specified . On Windows, this parameter is only meaningful when '-dbinstance' is also specified, and it is only needed when the database name is different than the ODBC DSN. On Linux, use this option only if -dbinstance is not used and the Oracle service name is different than the TNS name.-dbinstance This option is only meaningful on Windows. When used, it causes VaultVerify to open the database directly instead of via the ODBC DSN specified in the configuration file. For SQL Server, the must be the instance name (e.g. 'SSE2005_ST'). Note that the default Instance name for SQL Server is 'MSSQLSERVER' and for SQL Server Express, it is 'SQLEXPRESS'. For Oracle, should be the service name, (e.g. 'ORCL'). -dbinstance must be used with -dbhost when the database server executes on a different host. For SQL Server, -dbname should also be used if the database name is different than the ODBC DSN. For Oracle, -dbname is ignored if -dbinstance is specified.-dbpassword Specifies the database logon password. If not specified, a blank password is used. (The password stored in the configuration is encrypted and cannot be used by Vault Verify.) On server configurations running against Oracle, this option must be specified since the Oracle password is never empty.-dbport Specifies the TCP/IP port to use to connect to the database server. This parameter is only used on non-Windows platforms when a different port is used than the vendor's default database port (for example, 1521 for Oracle).-dbuser Specifies the logon ID used to connect to the database. If specified, this parameter overrides the user specified in the StarTeam . The only valid user to use with this option is the user that owns the StarTeam tables.-help (or -h or -?) Display this usage information.-path Specifies the folder path of the starteam-server-configs.xml file. This file must exist and contain the specified . By default, this file is opened in the parent folder of the current working directory if it is not found in the current working directory.-nosharereport Suppress the reporting of share information. Normally, all share paths of each corrupt file is reported. This option suppresses the share path information, which can speed up application execution and substantially reduce the report size.-repair Specifies that an attempt should be made to correct archive file problems. 'Corrupt' archives are moved to the 'corrupt file folder' (see the '-cf' option). If they correspond to valid file revisions, they are then treated as missing. 'Missing' archive recovery is attempted from other vault files and, if the '-useca' option is specified, from a Cache Agent. 'Stray' archives are moved to the 'stray file folder' (see the '-sf'option). Note: '-repair' is ignored if the StarTeam is in use.-sf Path name of the 'stray file folder', where extraneous files found by the 'stray' check are moved when '-repair' is specified. The default 'stray file folder' is: c:\temp\VVStrayFiles\-t Display elapsed time information when the verification finishes.-useca : If '-repair' is specified, this option enables attempts to recover missing files from the specified MPX Cache Agent. The and must designate a remote Cache Agent because it maintains an independent cache.-verbose Display additional status information as the verification proceeds.
FULL Vault Basic 2009 [32-64Bit]
OpenMediaVault is a Debian based special purpose Linux Distribution to build a Network Attached Storage (NAS) System. It provides an easy to use web-based interface, Multilanguage support, Volume Management, Monitoring and a plugin system to extend it with LDAP, Bittorrent, and iSCSI capabilities. This tutorial describes the installation and configuration of OpenMediaVault.if(typeof ez_ad_units!='undefined')ez_ad_units.push([[728,90],'howtoforge_com-box-3','ezslot_9',106,'0','0']);__ez_fad_position('div-gpt-ad-howtoforge_com-box-3-0');Prerequisites for this tutorialPC with 32 or 64Bit Intel processor.Min. 1GB RAM.2 Harddisks (or one hard disk with 2 partitions). OpenMediaVault requires a separate disk or partition for the OS install and a separate disk or partition for the data.1) Download OpenMediaVaultThe first step is to download the OpenMediaVailt ISO file from Sourceforge. if(typeof ez_ad_units!='undefined')ez_ad_units.push([[728,90],'howtoforge_com-medrectangle-3','ezslot_8',121,'0','0']);__ez_fad_position('div-gpt-ad-howtoforge_com-medrectangle-3-0'); software exists in flavors for 32- and 64Bit Intel/AMD processors and for some other platforms like Raspberry PI, Odroid and Cubox i. I will choose the version for 64Bit processors (amd64). The direct download link for the current 2.1 version is: _2.1_amd64.iso?r=&ts=1438327317&use_mirror=netcologne2) Prepare the Boot MediaThe ISO image can be used to install OpenMediaVault into a virtual machine like VMWare or Virtualbox directly. To install the software on real hardware, you need a boot media like a CD / DVD or a bootable USB stick.(adsbygoogle=window.adsbygoogle[]).push();Burn the downloaded ISO file on a CD or DVD or load it on a USB stick.2.1) Create a bootable USB Stick on LinuxThe following command can be used to write the ISO file on the USB Stick on Linuxsudo dd if=openmediavault_2.1_amd64.iso of=/dev/sdX bs=4096Replace /dev/sdX with the device name of the USB drive. Please be careful, the dd command can cause severe damage if you select a wrong drive as target.if(typeof ez_ad_units!='undefined')ez_ad_units.push([[580,400],'howtoforge_com-medrectangle-4','ezslot_2',108,'0','0']);__ez_fad_position('div-gpt-ad-howtoforge_com-medrectangle-4-0');2.2) Create a bootable USB Stick on WindowsWhen you downloaded OpenMediaVault onto your Windows Desktop, then you can use e.g. unetbootin to prepare the USB Stick. ) OpenMediaVault InstallationInsert the boot Media that you prepared for the installation into the PC or Server were OpenMediaVault shall be installed and start or reboot the system. It might be necessary to select the correct boot media device in the BIOS.if(typeof ez_ad_units!='undefined')ez_ad_units.push([[580,400],'howtoforge_com-box-4','ezslot_7',110,'0','0']);__ez_fad_position('div-gpt-ad-howtoforge_com-box-4-0');When the System booted successfully you will see the following screen of the OpenMediaVault installer. Select the "Install" option and press enter or wait until the installation starts automatically.Select the language for the installation process.And your location. The location will be used to define the timezone in one of the next steps and to preselect the keyboard layout.Now select the keyboard Layout. In my case, I'll select "German" as layout and press .The installer starts to load some additional packages from installation media.Enter the hostname of your server. The domain name is requested in the next screen, so the hostname here is the first part of the fully qualified domain name. When the server shall have the fqdn "server1.example.com" then the hostname is "server1".Enter the domain name of the server.Enter the root password. This password is used for the shell login, it is not the password of the OpenMediaVault Web interface. Confirm the password by entering it again in the next screen when requested.Select the server time zone and press . The time zone is important for date / time in log files and for the timestamps of saved files.The installer starts to copy the system files to Disk now.Configure the location from where the apt package manager will load the software packages. Choose a location near to you.And then select the mirror server. You can just choose the first one if none of the listed mirrors is from your Internet access provider.When you use a http proxy to access the internet, then enter it's details here. Otherwise press .Apt will now Download the packages.The installation is finished. Press to reboot the server.The Grub boot screen appears. Press or wait until it starts automatically.The System ready. You can now login to OpenMediaVault on the shell as root user or in the Web interface.4) Login detailsWeb interfaceUser: adminPassword: openmediavaultClient (SSH, console)User: rootPassword: The server has been configured by DHCP. Login as root user on the shell and run the command:ifconfigto get the current IP address. In my case, the IP address is 192.168.1.30.Open a web browser and enter http:// followed by your IP address: to go to the web login:Enter the default login details user: admin, password: openmediavault:And the OpenMediaVault Admin interface appears.5) First steps in OpenMediaVaultThis chapter shows the steps to secure the login, enable an FTP and SMB/CIFS share and how to enable access by SSH.5.1) Change the web admin passwordTo change the web administrator password, go to "General Settings" and change to the tab "Web Administrator Password:Enter the new password and press on the "Save" button in the upper left corner of the input form.Services like FTP, SMB and SSH are disabled by default. In the next step, I will enable FTP and SMB (Microsoft Windows Share).5.1) Enable FTPGo to Services > FTP and enable the "Enable" Checkbox.Press the "Save" button in the upper left corner.And click on "Apply" in the yellow bar that appears above the the form.Finally, confirm that the changes shall really be applied.5.2) Enable SMB / CIFSNow go to Services > SMB/CIFS and enable this service like you did with FTP.5.3) Enable SSHSame procedure for the SSH service. Go to Services > SSH and enable the service.5.4) Create a file system as data storage volumeOpenMediaVault needs a separate hard disk or partition to store data (storage volume). In my case, I'll use a second hard disk /dev/sdb. Click on Storage > File Systems > Create to add the second hard disk as a storage volume. The name of tmy storage volume is "data". The final list of storage devices shall look like this. Select the "data" volume in the list and click on the "Mount" button to mount the volume. Only mounted volumes will appear as option in the shared folders volume list.5.5) Add a userNow we can add a user to access your file shares. Click on "Access Rights Management" > "User" > Add:Enter the user details: username, email address, and password. Then confirm the changes.5.5) Add a file shareTo store files on the NAS drive, we need a file share that can be accessed by our user. Click on "Access Rights Management" > "Shared Folders" > "Add".I will add a folder named "Documents" with the path "Documents/" on the data volume.The next step is to grant read/write permissions to the user "till". Click on the "Documents" share in the list and then on the Icon "Priveliges" in the menu above the list. This will open the priveliges Window, enable "Read/Write" for the user and press save.Finally add the share to the services that shall be able to use them. To enable the share for FTP, go to Services > FTP > Shares, Click on "Add", Select the "Documents" share and press save. Confirm the changes.Use the same procedure for SMB/CIFS: go to Services > SMB/CIFS > Shares, Click on "Add", Select the "Documents" share and press save. Confirm the changes.Now you have a NAS device with a Documents folder that can be accessed by your user with FTP and with the SMB/CIFS protocol.6) VMWare / Virtualbox ImageThe resulting setup of this tutorial is available as ready to use virtual machine image in ovf format (compatible with VMWare and Virtualbox) for Howtoforge subscribers.The Login details of the VM are:Root password on the shell: howtoforgeOpenMediaVault Web interfaceUsernam: adminPassword: howtoforgeDont forget to change the passwords!7) LinksOpenMediaVault About Till BrehmOver 20 years of experience as a software developer and Linux system administrator. Till Brehm is the founder and lead developer of the ISPConfig hosting control panel software (since 2000) and he founded HowtoForge in 2005 as a place to share Linux knowledge with other Linux enthusiasts. view as pdf printShare this page:Suggested articles23 Comment(s)Add commentName *Email *tinymce.init( bold italic link",);CommentsBy: thctlo Reply Hai, a nice howto but please stop use-ing .local as domainname in your examples. .local is a reserved domainname for apple's mDNS (zeroconf). and same for these names :.local.localdomain.domain.lan.home.host.corp.privsee also: -chapin-rfc2606bis-00 By: EvilShiloh Reply I don't understand the statement concerning the use of domain name in the instructions. The document refenced specifically stated certain top level domains like .local are reserved so they will not be used on the internet for just this kind of purpose when you are using it on your local network so it would be unlikley to interfere with your communication on your local network to a real internet domain of the same name IF it actually existed. So the example in the instructions is a valid use of .local and most people should know when they see that, if in their case a different domain should be used, change to fit the situation. So if that list of top level names are reservered for no one to use on the internet, how can Apple reserve the name?By: Dhiman Reply Very useful steps. I installed OMV on my laptop. But The files can only be accessible by android apps or windows file explorer. Is there any way to access them using browser interface, like what we can do in case of synology or qnap products? Is there any free os to do so?By: FieldWolf Reply No, there is no way to access your files over the browser interface.By: TheBulgarian Reply -Plugin-Developers/openmediavault-extplorereXtplorer is a web-based File Manager. You can use it to: 2ff7e9595c
Comments