Google Drive Recover Files

I accidentally deleted all files and folders from google drive when I switched from one laptop to another. What to do?

Nothing to worry or even we don’t have to try a one of the great third party software like www.easeus.com

All what you have to do is to restore files by yourself by just doing 3 simple steps:

Login to Google Drive and Restore from your Trash

Steps:

Open google chrome internet browser and go to drive.google.com/drive/trash

Login

Right-click the file you'd like to recover and Click Restore.

Symantec Backup eVault Error: Possible Causes

Error Code: V-79-57344-3844 - The media server was unable to connect to the Remote Agent on machine

Ref. Backup exec verison: Symantec Backup Exec 2010 R3 v13.0Rev.520464bit.

1. Check the version of beremote.exe (C:\Program Files\Symantec\Backup Exec\beremote.exe) on both backup exec server and on enterprise vault server (C:\Program Files\SYMANTEC\BACKUP EXEC\RAWS\beremote.exe).  If differs, must be the SAME version.

2.

Check if there is enough storage space on backup exec server

3. Make sure that the backup exec remote agent services are running on both SQL nodes.

4. DB Permissions needs to be checked. The backup service account needs to have db ownership rights on all the enterprise vault related databases.

Try considering redeployment of BE remote from symantec console to the destination server.

if for any reason the above deployment fails, consider manual re-installation of Symantec Backup exec remote agents:

(agent location)

32bit: C:\Program Files\Symantec\Backup Exec\Agents\RAWS32

64bit: C:\Program Files\Symantec\Backup Exec\Agents\RAWSX64

5. Enable troubleshooting: Click SGMon.exe (C:\Program Files\Symantec\Backup Exec\SGMon.exe) from backup exec server. Capture the following check lists:- JobEngine,RAWS; Backup exec server;Device and Media;Third Party debug output and then click start capturing debug output.

6. Run the backup schedule again. try to expand the enterprise vault backup selections again until the error pops up. 

You might get a tip to find out the error cause from the SGMon capture screen.

NAS

reliable backup storage

Tips for SharePoint 2010 Backup

SharePoint 2010 Backup

.. I will shortly add more steps tested, accomplished and documented in our environment.

Incremental backup of data with .BAT

 DOS command: incremental backup
open notepad and copy the below code in a .bat file and then use windows scheduler to schedule eod backup to your external storage 

@echo off
xcopy C:\mydocuments D:\Backup\Docs /E /H /R /Y /I /D
xcopy "%USERPROFILE%"\Favoris D:\Backup\Favoris /E /H /R /Y /I /D

Script Backup

Backup folders/ files to network share using simple DOS command.

(save money by purchasing softwares which can do the below process)

so here we go:

simple xcopy command needs to be created on a bat file so that the .bat can be automated by windows scheduler.

for eg:

xcopy "D:\GP Backup\SQL Svr Bkp\09" \\qdc-gp\Backup /E /R /Y /D /Q

the above command says to copy everything (files and folders) under 09 directory to a network path under folder Backup. make sure you follow the syntax and the path should be specified within "" so that any spaces in between will be taken care of. 

/E stands for .. Copies directories and subdirectories, including empty ones

/R stands for .. Overwrites read-only files

/Y stands for .. Suppresses prompting to confirm you want to overwrite an existing destination file.

/D stands for .. If no date is given, copies only those files whose source time is newer than the destination time. if you want a specify date, provide in /D:m-d-y format.

/Q stands for .. Does not display file names while copying.

Make sure that the destination share folder has write permission to the account with which the batch file will be executed.

you may apply the above command which are legitimate form your perspective.

xcopy /? will give you the syntax and the relavent usage of switches

Interesting part is scheduling the batch file and alerting the concerned staff with an automated email after the backup completes.