26 March 2014

Get the password used in a SQL Job that launch an SSIS password protected package

On MS SQL Server 2008 R2 (and maybe other versions) :
Simply right-click on the job and select the option Script Job as > CREATE To > New Query Editor Window

The password will be written in the SQL query.

24 March 2014

Resolve the error "Service Temporarily Unavailable" on Belgacom e-services My Bill & Usage

If you get the error message "Service Temporarily Unavailable" when you connect to the e-services administration, you can simply change the email address used as your login and that should do the trick.

18 March 2014

Check the reason why Synology Network Backup failed

If you have encountered errors with the Synology Network Backup and that the log message is as vague as
Network Backup failed to backup task [xxx] to [xxxx.synology.me]. ([23] Some files could not be transferred. Possible reasons: 1) backup user has no permission to access the files, 2) illegal file name. 3) file name too long)
and you want to get more information about the error, simply connect to the console and open the file /var/log/rsync.error 

13 March 2014

Restore Synology network backup after nas migration



If you have changed the source server of a network backup, you may follow these steps in order to recover your backups without the need to transfer again all your files through the network :
  1. Connect to the target (backup) server
  2. Go in the NetBackup folder
  3. Go in the folder you want to recover (you may rename it if you wish)
  4. Delete all files at the root of this folder (not the subfolders)
  5. Go in the @app folder
  6. Delete all files at the root of this folder (not the subfolders)
  7. Create the backup task using the same target folder name as previously.
  8. You may receive an error message: "The operation failed.  Please login to DSM again and retry". Simply ignore it.
  9. Run the backup task

Take care that if you have set a new user to the backup task on your target (backup) server since the last backup has been made. You have to ensure that the access rights for this new user are consistent along the whole folders' tree (use chown -R or check the corresponding checkbox in the folder properties in the File Station)
UPDATE 2014-03-18 : Better use the command line if you want to ensure the owner of hidden files and folders is also changed